-
Notifications
You must be signed in to change notification settings - Fork 152
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
doc: adding admin policy docs #443
Conversation
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.
Added a couple questions and edit suggestions for you, I also have some edits ready to be PR'd into your working branch @joesepi – if you can give me edit permissions to your fork. 🎉
Thanks!
WORKING_GROUPS.md
Outdated
|
||
A Working Group's charter can be revoked either by consent of the Working | ||
Group's members or by a CPC vote. Once revoked, any future work that arises | ||
becomes the responsibility of the CPC. |
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.
On revocation, should Github projects related to the WG's work be archived unless WG members request otherwise and the CPC agrees?
It seems that doing so by default might help keep the organization project list manageable.
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 agree, this should at least enforce that the project list stays manageable. If the CPC is very dependent on the WG's projects, the transfer of responsibility will likely already be well known during the time of revocation anyway. 👍
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 say let's not be prescriptive and see if this needs to be optimized. It has been working in the Node.js space for some time as is. Thanks.
Fyi, I did some link and formatting cleanup to try and fix the CI problems in joesepi#1 |
* Cleanup named links There were a number of named links at the bottom that pointed to Node.js equivalents. Replaced inline URLs with named links, cleaned up the named links to separate them from the document text, and got rid of redundant named links. * Update transfer-repo-into-org.md * Cleanup links in GOVERNANCE.md This seeks to fix the Travis CI warning, and increases consistency among the links to various parts of the CPC charter and project README.
Updating the admin docs for readability and to address concerns raised by CPC members in [CPC openjs-foundation#443](openjs-foundation#443).
* Update admin docs for readability Updating the admin docs for readability and to address concerns raised by CPC members in [CPC openjs-foundation#443](openjs-foundation#443). * update admin docs * paragraph consistency * paragraph consistency
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.
Fix: broken links
Sorry for all the noise. :P I won't do fixes via the web interface next time. 🙏 |
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.
LGTM once my last comment about the foundation npm account is addressed.
@mhdawson thank you for your input! 🙏 Your concern about the foundation npm account has been addressed. 🚀 |
@obensource thanks, looks ready to land 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.
lgtm
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.
LGTM
Some changes from @obensource touch the GOVERNANCE.md file, but they are not meaningful changes, only some link cleanup. |
* adding org mgmt files still need work * gh org mgmt policy update * working groups doc * Cleanup named links (#1) * Cleanup named links There were a number of named links at the bottom that pointed to Node.js equivalents. Replaced inline URLs with named links, cleaned up the named links to separate them from the document text, and got rid of redundant named links. * Update transfer-repo-into-org.md * Cleanup links in GOVERNANCE.md This seeks to fix the Travis CI warning, and increases consistency among the links to various parts of the CPC charter and project README. * Update admin docs for readability (#2) * Update admin docs for readability Updating the admin docs for readability and to address concerns raised by CPC members in [CPC #443](openjs-foundation/cross-project-council#443). * update admin docs * paragraph consistency * paragraph consistency * paragraph consistency * paragraph consistency * paragraph consistency * paragraph consistency * paragraph consistency * Update transfer-repo-into-org.md Co-Authored-By: Michael Dawson <michael_dawson@ca.ibm.com> * Update WORKING_GROUPS.md * appease linter * Update WORKING_GROUPS.md * consensus seeking model link * Fix: broken links * Fix: broken links * Fix: broken links * Fix: broken links * Fix: broken links * Fix: broken links * Fix: broken links * Fix: broken links * Update transfer-repo-into-org.md * Updates from PR review Co-authored-by: Ben Michel <ben@obensource.com> Co-authored-by: Michael Dawson <michael_dawson@ca.ibm.com>
Closes: #185
Adding docs based on Node.js version: