The goal is to start a discussion on how to structure Chef as an open
source project - and ultimately decide, document, and live by that
structure. That starts with a lot of Chef Software employees, because we
are the maintainers currently. As we build the rules for maintainers, ever
more people will have increased authority (and responsibilities) for
various parts of the project. For sure that involves roadmap.
Unless we just can’t function without it, the rooms will be open and no
restrictions placed. Feel free to send a clarifying PR.
On Jul 7, 2014 4:07 PM, “Mike” email@example.com wrote:
This is great, thanks for opening this up.
Is the goal of this to have Chef Inc developers join in on the “where is
Chef (the product) going” discussion, and open it to interested,
You reference moderators, voicers and de-voicing. Will the IRC room turn
into Voice-only for the duration of the meeting? Who will be given voice
Thanks for taking the time!
On Mon, Jul 7, 2014 at 5:59 PM, Adam Jacob firstname.lastname@example.org wrote:
Hi guys! As I mentioned in the blog post I wrote a few days back, we
should start having regular developer meetings in IRC. The following pull
request is my stab at how we should hold those meetings, and a proposed
standing agenda (that I expect will change dramatically as we evolve.)
Note that I do not expect the first meeting to follow the standard agenda.
When I get 3 thumbsups, I’m going to merge it.
Feedback super welcomed.
Adam Jacob, Chief Dev Officer
T: (206) 619-7151 E: email@example.com