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

Fix TBD placeholders in our governance document #25

Open
mbernst opened this issue Dec 21, 2017 · 5 comments
Open

Fix TBD placeholders in our governance document #25

mbernst opened this issue Dec 21, 2017 · 5 comments
Assignees

Comments

@mbernst
Copy link

mbernst commented Dec 21, 2017

The governance document has a few places where we left placeholders for this location. Specifically:

  • "All proposals must be made through our tool (TBA)."
  • "All proposals and their state are maintained on our tool (TBD)."
  • "Each proposal will be documented on our proposal tracker (TBD)"

Proposal

As discussed in this week's hangout (http://youtu.be/UmGGKwuMp0g) and raised by @shirishgoyal, let's fix this. Let's change them to read:


Use comments to share your response or use emoji 👍 to show your support. To officially join in, add yourself as an assignee to the proposal. To break consensus, comment using this template. To find out more about this process, read the how-to.

@shirishgoyal
Copy link

In addition, we need to update the document Governance Groups with engineering quality review team and operational group members for 1) Fix live bugs
and 2) Committing changes to production server, as decided by the community vote. Both of them will be initialized with list of below members and their proper access to the required systems will be reinstated, if not the case.
@aginzberg, @dmorina, @nistala, @neilthemathguy and @shirishgoyal

Voted by the community - 2nd Option below

image

Previous nomination history

image

image

@mbernst
Copy link
Author

mbernst commented Dec 21, 2017

Ah, I have been indicating how the documents should change by doing suggested changes in the Google Doc versions. My assumption is that since #2 doesn't have consensus yet, the Google Drive versions are still the versions of record and the ones we should be editing. I further assume that validating the changes I made with suggestion mode, and accepting them, will be the role of the QR team necessary to close the issue. Please correct me if I screwed anything up here.

https://docs.google.com/document/d/1bkr1zZpYTWY8aERFSXYuNQ7fY5sTzqD24wenUcnRXHE/edit#

https://docs.google.com/document/d/1465PAK2Q1zA-0juttTcbTuQOzABwNMY6yb-JXPSWGps/edit#heading=h.qte9zgui0gkg

@markwhiting
Copy link
Member

I can roll in those other aspects to the revised version of #2 also.

@mbernst mbernst self-assigned this Jan 1, 2018
@mbernst
Copy link
Author

mbernst commented Jan 1, 2018

The proposed changes are now made in suggestion mode on the Governance GDoc. This proposal is now ready for quality review ("an ad-hoc team of at least three people is formed from volunteers").

@markwhiting
Copy link
Member

I reviewed this and it looks good to me.

I did wonder if it might be better to link to the issues page, instead of the repo, i.e. https://github.com/crowdresearch/collective/issues, but I'm ok with either decision there.

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

No branches or pull requests

3 participants