-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Adds GOVERNANCE.md #4
Conversation
Can you name the Working Group that's responsible for those repos? Specifying a name seems important to me. I would say Website WG is the appropriate name. |
Yeah, I think specifying the group and/or the group members would be a smart idea, give readers somewhere to go if they need to contact us. |
Possible formatting: ### Website WG Members + Contact
Full Name: @gh-name, [@twitter-name](), `email``@``provider.tld` Website WG Members + ContactFull Name: @gh-name, @twitter-name, The markdown-formatted email provides an easy-to-copy email that hides the address from spiders in different tags. I'd be happy to go through and fill in this information if I can get a list of people to include. |
Trent Oswald: @therebelrobot, @therebelrobot, Though I'm pretty sure all of the spiders have my email :P @nodejs/website, I would suggest commenting on this thread with the info you want for yourself in this file. |
I tried to sneak in 'naming' the group by using Re: these or any other changes proposed, this branch is living on our repo. I'd encourage collaborators to make any small additions or changes as they see fit directly (versus just commenting: takes almost as much time if you use the built-in editor.) |
Previously our README maintained the list of WG members/collaborators and this document just linked to that part of the README. Do we want to just move that section here instead? (I'd rather it just live in one place, regardless of which option.) |
@snostorm I think it should stay in the README.md file. There's a wall of text in this file that is on par with legalese - I think it's best to keep it where it can be found very fast, without needing to worry about the rest of the content in this file. |
Agreed, et al. |
Ok, so perhaps we can open a separate PR for us to all get our names in the README and work out how to organize WG Members/Collaborators? That way we won't dilute the evaluation of this PR. (I assume we still want to be more clear about the "Website Working Group" name, for example.) |
@nodejs/website Any objections about merging this? |
Modifications of the contents of the `nodejs/new.nodejs.org` repository are made on | ||
a collaborative basis. Anybody with a GitHub account may propose a | ||
modification via pull request and it will be considered by the project | ||
Collaborators. All pull requests must be reviewed and accepted by a |
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.
This may not be worthwhile, especially if we are redeveloping parts of the site.
There are some modifications from nodejs/iojs.org’s existing version (in retrospect, perhaps I should have imported - committed - then committed the revisions.)
The most notable change is to the introduction section: