Make an official gitlab partner cookbook
Chef Inc. is starting a "partner" cookbook program. The tl:dr; is that this will allow Chef to introduce a quality assurance and it will allow partners to get greater visibility for their official cookbooks.
- There are multiple cookbooks available if you search for gitlab on chef supermarket
- The first hit and the one holding the namespace was previously owned by atomic-penguin (Eric G. Wolfe) but is now in the hands of @jjasghar
- GitLab Inc is using https://supermarket.chef.io/cookbooks/omnibus-gitlab to deploy GitLab.com and dev.gitlab.org
- As a user it is unclear which way to go
- GitLab should have the gitlab namespace and the stewards of the project should have control over it
- The cookbook should have a "partner" stamp of quality assurance
How to get there:
- On the Chef Inc. side (@jjasghar, @russellseymour) send the joint marketing agreement to @ashleys, can reuse the email thread we already have running.
- On the GitLab side (@marin, @dblessing, @twk3, @pcarranza) will reassess the situation of the current gitlab and current omnibus-gitlab cookbook. We need to make sure that GitLab Inc. can use the cookbook but also that the cookbook is flexible enough to be used by majority of the community
- On the GitLab side, make sure that the cookbook has tests, proper README.
- On The Chef Inc. side (once GitLab finishes its part of updating the cookbook), verify if the cookbook fulfills the criteria. If no, Chef Inc. will create issues noting all the shortcomings
- Once the cookbook is in the ready state, Chef Inc. will start the procedure for the cookbook to receive the appropriate badge.
- On the GitLab side, make sure that the cookbook is tested by GitLab CI so we can make sure that the build is green.