We're trying not to impose rules. However we do require the following for acceptable submissions:
- All blueprints should use the
debian-stretchcontainer base template for containers. If custom containers are required they should ultimately derive from the
debian-stretchbase template. Submissions using other containers that do not ultimately derive from the debian-stretch container base template will not be accepted.
- You should have a Readme.md file at a minimum that documents your blueprint. It should explain the application, applications or components in the stack as well as any user variables effecting the behavior of template.
- Do not copy or use other people's work without proper attributions in your Readme.md file. Depending on the ratio of original work produced the blueprint may or may not be accepted.
- Make sure to use the Branding Features of blueprints so the author, product version, and product icon is available to users of your blueprint in the bazaar.
- The more features of blueprints you use, the higher your chances of a successful submission.
- The more you document your blueprint, the higher your chances of a successful submission.
- The more "sophisticated" the blueprint with the options offered to users of the blueprint increases the chances of accepting submissions.
- Have fun and join us on Slack, ask questions, and report bugs. That naturally increases your changes by improving your ability to produce better blueprints.