[WIP] Reboot of CEP7 development #296
Conversation
|
@gonuke Thank you for putting this together! If I understand correctly, there is now going to be a process to become a Cyclus developer? |
|
@jbae11 - This is not about a process to become a developer - we don't need an more obstacles there. This is about a process to govern a community of those who effectively volunteer their effort to that community. |
Fix typos - thans @jbae11
| governance within this organization. Membership in this organization is | ||
| governed by a process defined below. | ||
|
|
||
| Council of Principal Investigators |
There was a problem hiding this comment.
Some thoughts about the council:
- If a community manager exists, their perspective would be really useful in the council. Maybe it would be helpful to reframe this council as a "leadership" council that is encoded to have a set of PIs on it
- The perspective of a person who is exclusively a user, and not a developer, can be helpful at a top level council making decisions. Would it be helpful to add in a role for this council that fills this representation?
| technical grounds. | ||
| 6. Changes are adopted when at least one member of the Organization has | ||
| approved the changes and no members of the Organization are blocking the | ||
| changes. |
There was a problem hiding this comment.
For more substantive changes (new features maybe?) it might be worth adding in a requirement that a PR is open for a period of time (perhaps two weeks?) before merging is allowed. That way community members have time to weigh in even if they aren't able to attend a development meeting where new features are getting pushed forwards.
|
|
||
| :CEP: 7 | ||
| :Title: Cyclus Community Constitution | ||
| :Last-Modified: 2015-08-18 |
There was a problem hiding this comment.
If this CEP gets updated as a result of this meeting (or the hackathon) then we should update this (or do we have a bot that handles it?)
| :Last-Modified: 2015-08-18 | |
| :Last-Modified: 2024-03-21 |
| :CEP: 7 | ||
| :Title: Cyclus Community Constitution | ||
| :Last-Modified: 2015-08-18 | ||
| :Author: Paul Wilson |
|
It appears I've been ignoring this review request for 5 years. Madicken (@munkm ) seems to have done a recent review. Is my review still needed? |
|
Since CEP7 is about governance, I think your input would still be valuable |
| Best Practices | ||
| --------------- | ||
|
|
||
| (should these be in their own CEP) | ||
|
|
||
| 1. Substantive changes to the work of others should require those others to | ||
| comment during the review process. | ||
| 2. Individual pull requests should be as small as possible to facilitate | ||
| timely review. | ||
| 3. Before embarking on long time-intensive changes, it is wise to collect the | ||
| opinion of the |Cyclus| community on the value of such changes, generally | ||
| through the mailing list. |
There was a problem hiding this comment.
I like the idea of having a development best practices CEP (I think this is what is commented on in l135?). This section isn't specific to governance and broad decision making, but it is something we want to encourage (or require?) community members to practice.
In light of possible expansions and changes to the Cyclus community, I am rebooting the consideration of CEP7.