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

@miketheman miketheman Oct 2, 2014

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

Copy link
Contributor

@coderanger coderanger Oct 2, 2014

Badass?

Copy link
Contributor

@jonlives jonlives Oct 2, 2014

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

Copy link
Contributor

@jjasghar jjasghar Oct 2, 2014

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

Copy link
Contributor

@coderanger coderanger Oct 2, 2014

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

Copy link
Contributor

@btm btm Oct 2, 2014

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

Copy link
Contributor Author

@adamhjk adamhjk Oct 15, 2014

lets use "advise on" the roadmap

juliandunn
Copy link
Contributor

juliandunn commented on 018cf48 Oct 2, 2014

Can you clarify what (c) means? Do we just mean a company that has committed to using Chef software in the conduct of its business?

juliandunn
Copy link
Contributor

juliandunn commented on 018cf48 Oct 2, 2014

Maybe also need some information in here about how any of these people can resign from their duties in a way that ensures the long-term viability of their component. i.e. wouldn't just want someone to just tableflip & bail.

juliandunn
Copy link
Contributor

juliandunn commented on 018cf48 Oct 2, 2014

Assume you meant "Company Leadership" here, otherwise it's self-referential since "Leadership" is defined as CBGB + Company Leadership


The CBGB is not:

* Intended to serve as a decision-making governance board. The CBGB advises, but does not manage, the Leadership.
Copy link
Contributor

@coderanger coderanger Oct 2, 2014

As above, should say Company Leadership probably.

Copy link
Contributor

@btm btm Oct 2, 2014

The "Leadership" is defined above as "the CBGB and Company Leadership (Chef Software CEO)." Do we mean instead "Project Lead and Lieutenants" ?

juliandunn
Copy link
Contributor

juliandunn commented on 018cf48 Oct 2, 2014

Can you clarify what (c) means? Do we just mean a company that has committed to using Chef software in the conduct of its business?

juliandunn
Copy link
Contributor

juliandunn commented on 018cf48 Oct 2, 2014

Maybe also need some information in here about how any of these people can resign from their duties in a way that ensures the long-term viability of their component. i.e. wouldn't just want someone to just tableflip & bail.

juliandunn
Copy link
Contributor

juliandunn commented on 018cf48 Oct 2, 2014

Assume you meant "Company Leadership" here, otherwise it's self-referential since "Leadership" is defined as CBGB + Company Leadership


Handle contributions on GitHub - first response to a PR within 48 hours
Be available on IRC
Attend the developers meeting (do not miss more than 3 in a row)
Copy link
Contributor

@jonlives jonlives Oct 2, 2014

Note to @adamhjk to clarify what happens when maintainers etc are in an inconvenient timezone for dev meetings

Copy link
Contributor Author

@adamhjk adamhjk Oct 15, 2014

We need to just make it part of the deal - lets figure out something that works. The reality is, going to be hard to be a maintainer without being in the meetings

@coderanger
Copy link
Contributor

@coderanger coderanger commented Oct 2, 2014


<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

@jonlives jonlives Oct 3, 2014

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

Copy link
Contributor Author

@adamhjk adamhjk Oct 17, 2014

All.

@ranjib
Copy link
Contributor

@ranjib 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 sersut commented Oct 8, 2014

Ditto @ranjib. +1

@coderanger
Copy link
Contributor

@coderanger coderanger commented Oct 8, 2014

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 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

@danielsdeleo danielsdeleo Oct 31, 2014

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

@coderanger coderanger Nov 9, 2014

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

Jon Cowie and others added 2 commits Nov 11, 2014
@adamhjk
Copy link
Contributor Author

@adamhjk 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 issue Nov 13, 2014
Proposed governance and maintenance policy
@coderanger coderanger merged commit b7bb7c6 into master Nov 13, 2014
@danielsdeleo
Copy link
Contributor

@danielsdeleo danielsdeleo commented Nov 13, 2014

🎉

@jtimberman jtimberman deleted the gov_maint branch Nov 14, 2014
@jtimberman
Copy link
Contributor

@jtimberman jtimberman commented Nov 14, 2014

🍨

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