-
Notifications
You must be signed in to change notification settings - Fork 13
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
Adding information about structure and governance. #38
Conversation
Another ping for the @2i2c-org/founders on this issue. I'll leave it open until mid-next week. Unless anybody suggests that we need to have a vote on it, I'll plan to merge unless anybody suggests changes or has comments to discuss. |
This looks good to me. 👍🏽 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing the hard work of thinking this through!
Overall LGTM!
about/structure.md
Outdated
|
||
* Open an issue in the `meta/` GitHub repository using [the {guilabel}`decision` template](https://github.com/2i2c-org/meta/issues/new?assignees=&labels=decision&template=decision.md&title=%7B%7B+Decision+Summary+%7D%7D). | ||
* Have conversation around the decision in that issue. This may happen in the issue directly, or in ancillary issues, meetings, etc that are relevant. The decision issue should link to these relevant spaces. | ||
* Once everybody has voted, note the decision in the issue and close it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To my understanding, the notions of "voting" and "consensus" (above) are incompatible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah - I was interpreting consensus to mean "every vote must be in favor in order to proceed". Is that not clear here? Or does it differ from your understanding of consensus?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was not clear to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll make that language more explicit 👍
Updated the proposal per @rabernat's suggestions above 👍 Will leave it open another day or two in case others have thoughts. |
Thanks for pushing this forward @choldgraf! This looks good to me |
OK, I'm gonna merge this! Wohoo explicit instead of implicit! |
This PR defines our current governance and general structure of 2i2c, as well as our relationship to ICSI. It closes https://github.com/2i2c-org/meta/issues/133.
To re-iterate, the point here is not to create new governance, but to put names and labels to our current governing structures. For suggestions about improvements to our governance, see https://github.com/2i2c-org/meta/issues/158. But let's focus this PR around "describing" rather than changing.
I am not sure whether this PR requires a formal vote from the @2i2c-org/founders. On the one hand, it is a change related to governance, which in general I think requires votes. On the other hand, it is not trying to change the substance of our governance, only describe it explicitly.
If anybody believes that we need to have a founding team vote for this, please do not hesitate to suggest one. Otherwise, I'll plan to leave this open for several days to give people a chance to provide input.
You can find a preview of the page here: https://2i2c-team-compass--38.org.readthedocs.build/en/38/about/structure.html
closes https://github.com/2i2c-org/meta/issues/150
closes https://github.com/2i2c-org/meta/issues/133