Idea: official community-plans repo

Please reply to propose/discuss any changes and I’ll do my best to re-incorporate

Goals

  • Create a 2nd-tier central place for sharing plans that are generalized and maintained, but don’t belong in core-plans
  • Make it easy for Habitat users to find ready-to-use plans for their own deployments
  • Make it easier for Habitat users developing their own plans to find a variety of quality reference points that go deeper into concrete cases
  • Make it easier for authors of reusable plans to make them available to the community
  • Relieve pressure to complicate core-plans and provide a path to improving plans with usability issues that are too risky to core-plans consumers to change

Proposed Implementation

  • Create a new Chef-owned repository at https://github.com/habitat-sh/community-plans
  • Register a new origin named community and hook up bldr.habitat.sh to build everything in it
  • Require contributed plans be named in the form community/${pkg_name}-${pkg_variant} (e.g. community/php7-laravel, community/nginx-laravel)
  • Require contributed plans to start with a CODEOWNERS file listing at least one reviewer (i.e. the person contributing the plan)
  • Extend review/approve duties beyond Chef staff to include top community contributors
  • Apply same APACHE-2.0 license as core-plans
2 Likes

Heck yeah man. Sounds like a great idea to me.

I like it. This sounds very sensible!

This is a fantastic idea!

:+1: on exploring this idea further!

:heart: @chris I love this idea. This has something that has been back of mind for me for a long while now, thank you for taking the initiative to write this up. I’m going to bubble this up to our DevRel team and will speak to them in the new year about this topic.

1 Like