Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed governance and maintenance policy #58

Merged
merged 7 commits into from Nov 13, 2014
Merged

Proposed governance and maintenance policy #58

merged 7 commits into from Nov 13, 2014

Conversation

adamhjk
Copy link
Contributor

@adamhjk adamhjk commented Oct 2, 2014

Below are the proposed governance and maintenance policy for Chef. :)

Before talking about certain roles and ideals, we want to make sure we’re clear about what we mean:

<dl>
<dt>CBGB</dt><dd>Means the Chef Board for Governance – the group of up to 12 representatives who will direct the roadmap and core criteria of the Project.</dd>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does the second "B" in the acronym stand for?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Badass?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If that's not what it stands for, I move that it should become so :p

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@adamhjk shouldn't it be an odd number not 12? Couldn't in theory something polarizing cause a deadlock?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also I would say this should read something more like who will [oversee | advise on | influence | assist with] the roadmap.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

steer, e.g. a steering committee, means the right thing to me.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets use "advise on" the roadmap

@coderanger
Copy link
Contributor

Google doc for everyone to self-organize on subsystems: https://docs.google.com/document/d/1I1GeXy0BHfy2grP2P46Ob1HAATmH9Xr8v46bSvElFSA/edit?usp=sharing


<dt>Company Leadership</dt><dd>Means the CEO of Chef Software Inc.</dd>

<dt>Corporate Contributor</dt><dd>Means a company that (a) is one of the top eight companies in terms of non-trivial pull requests in the past six months as measured by contributions by all employees; (b) a company that has employees as Maintainers who make significant contributions to the Project; and (c) has committed to integrate Chef software into its products.</dd>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this one a) AND b) AND c) or is it a) OR b) AND c)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All.

@ranjib
Copy link
Contributor

ranjib commented Oct 8, 2014

👍 the proposed format in its current shape is good enough for us to begin. We can revisit this as and when its needed, whats more important is to get this going and start working on these structures, as it will give us some early feedback (after which we might have to accommodate some changes in the proposed structure anyway ... like the respond within 2 days of raising a PR etc)

@sersut
Copy link

sersut commented Oct 8, 2014

Ditto @ranjib. +1

@coderanger
Copy link
Contributor

I don't want to put words in @adamhjk's mouth, but I know sub-delegation has been discussed. I think the plan was to start with these somewhat broad categories and look in to additional delegation if we think this overall structure is working well. Minimum viable culture :)

@adamhjk
Copy link
Contributor Author

adamhjk commented Oct 17, 2014

Updated to reflect the changes I commented on this thread.

Be available on IRC
Attend the developers meeting (do not miss more than 3 in a row - special dispensation can be made for difficult time zones)
Be available to answer mailing list questions within 48 hours
Weekends and local holidays in the maintainer’s jurisdiction are not counted for timeliness requirements. Absences for reasonable causes such as vacations, illness, etc. are also acceptable; Maintainers should notice of absences via the development mailing list whenever possible.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing the verb in "Maintainers should notice of absences." "provide" works.


* Project Lead: Initial Project Lead will be Adam Jacob. Any new Project Lead candidate will be selected by a majority vote of the Lieutenants, and approved by Company Leadership. This selection will happen according to the Maintenance Policy.

* All Other Seats: Candidates who meet the criteria for each group identified above will be elected by at least a majority vote of all qualified voters: +1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What defines "qualified voters"? I think maybe this was a thought that got cut off.

Jon Cowie and others added 2 commits November 11, 2014 10:16
@adamhjk
Copy link
Contributor Author

adamhjk commented Nov 13, 2014

This has my 👍 to merge. We have one more change we are going to make, which is a clarification that anyone with a supermarket account is a registered voter.

@opscode/rfc-editors can merge when that is done. Long live Chef!

I want to publicly thank @coderanger for carrying this policy forward so strongly.

coderanger added a commit that referenced this pull request Nov 13, 2014
Proposed governance and maintenance policy
@coderanger coderanger merged commit b7bb7c6 into master Nov 13, 2014
@danielsdeleo
Copy link
Contributor

🎉

@jtimberman jtimberman deleted the gov_maint branch November 14, 2014 04:16
@jtimberman
Copy link
Contributor

🍨

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet