Allow initial install of Konveyor to be seeded with a demo app so a new user can quickly run several workflows about enhancements HOT 3 OPEN

I think this is a great idea.

It would also be good for all the stuff we care about to use this example as a integration test.

from enhancements.

+1. I have always appreciated a few projects where they had a well written demo + documentation around that demo . We can also may be add a little design diagram with the app & how we can use Konveyor to modernize if possible. This was especially helpful when I had to try out multiple tools to solve an issue in a limited time and make a decision on which one to pick.

from enhancements.

I've received feedback about users finding it very hard to figure out where to begin and how things work in an empty Konveyor instance with no data on it. The actual quote was that "it took too much time and effort to get to a point where value could be demonstrated". @dymurray @jwmatthews @savitharaghunathan I believe we should pick this up for 0.4 alongside some documentation that explains what the sample data stands for. My only gripe about the original proposal would be that I don't think we should default to seeding the instance with the sample data, as I believe it should be the other way around.

I think the tackle-testapp application and the petclinic example would be great for sample data, although I guess we would need to figure out if there are any legal implications to that, both upstream and other potential downstream distributions. I imagine the best approach would be to leave this as a configurable parameter or dataset, so vendors can add whatever they want in their downstream distributions.

from enhancements.