Add an ownership field to cookbooks to clearly define responsibility. This will help clarify who the decision-maker or point of contact is for any potential changes, as well as facilitate ongoing maintenance and updates. Consider how to handle team renames.
This aims to:
- Direct people looking for information on how to use a specific cookbook to the right team.
- Direct people having trouble running a specific cookbook to the right team.
- Help people sending code reviews to an existing cookbook to know who to add as reviewer.
- Clarify ownership and expectations on which team is responsible for each cookbook, in particular to:
- keep the cookbook up to date with code and infrastructure changes
- be a point of contact for questions about cookbook usage, bug reports and feature requests
- be responsive to code reviews for that cookbook
As part of the work to set the ownership of existing cookbooks we'll also check if some of them might no longer be required in T379259.
The choice to be able to mark only one team as owner is intentional, as multiple owners will only risk to create more confusion than help.