Blueprint reoganization and support

[mlavi]

Kanister blueprints exist in the /examples directory of the project; they are the key artifacts that Kanister works on.

As the project has grown over time, blueprints have been added for different use cases and proof of concepts, they exist in various states of maintenance, and some have atrophied. In order to improve blueprint organization, community participation, and clarify the support model, a blueprint reorganization is needed!

Proposed Solution:

• Move blueprints that are not used by Kanister developers for testing into a sub-directory: /examples/community
  • This will make explicit what blueprints the project depends on (and must maintain) versus community supported blueprints
  • Stabilize any dependencies, hopefully not needed!
• Create an /examples/community/README.md to describe directory organization and community support model, link back to Kanister project supported blueprints if appropriate
• Create kanisterio/blueprints repository, migrate kanister/examples/community blueprints to new repo
  • Remove kanister/examples/community/ blueprints, update the /examples/community/README.md to point to the new repo

[github-actions[bot]]

Thanks for opening this issue :+1:. The team will review it shortly.

If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md.

If you haven't already, please take a moment to review our project's Code of Conduct document.

[shuguet]

Why would we go through step 2? Why not move directly to a separate repo? That's what Kyverno does for example with they "policies" repo (https://github.com/kyverno/policies/), and make it much cleaner in my opinion.

[github-actions[bot]]

This issue is marked as stale due to inactivity. Add a new comment to reactivate it.

[mlavi]

At our most recent engineering offsite, Thomas agreed to a separate repo.