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

Adds GOVERNANCE.md #4

Merged
merged 1 commit into from
Aug 25, 2015
Merged

Adds GOVERNANCE.md #4

merged 1 commit into from
Aug 25, 2015

Conversation

snostorm
Copy link
Contributor

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:

All of the Node.js Foundation websites, including this repo, are jointly governed
by a Working Group (WG). The WG is responsible for high-level guidance of this and
related projects which include:

- [nodejs/iojs.org](https://github.com/nodejs/iojs.org) published to https://iojs.org
- [nodejs/new.nodejs.org](https://github.com/nodejs/iojs.org) published to https://new.nodejs.org
- [joyent/node-website](https://github.com/joyent/node-website) published to https://nodejs.org

@bnb
Copy link
Contributor

bnb commented Jun 19, 2015

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.

@therebelrobot
Copy link
Contributor

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.

@bnb
Copy link
Contributor

bnb commented Jun 19, 2015

Possible formatting:

### Website WG Members + Contact
Full Name: @gh-name, [@twitter-name](), `email``@``provider.tld`

Website WG Members + Contact

Full Name: @gh-name, @twitter-name, email``@``provider.tld

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.

@therebelrobot
Copy link
Contributor

Trent Oswald: @therebelrobot, @therebelrobot, trentoswald``@``therebelrobot.com

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.

@snostorm
Copy link
Contributor Author

I tried to sneak in 'naming' the group by using Website Working Group in context, shortly after it is more generically defined. Granted, I almost made the addition myself a few times earlier in the document, but I was trying to keep consistent with the older structure.

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.)

@snostorm
Copy link
Contributor Author

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.)

@bnb
Copy link
Contributor

bnb commented Jun 19, 2015

@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.

@therebelrobot
Copy link
Contributor

Agreed, et al.

@snostorm
Copy link
Contributor Author

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.)

@fhemberger
Copy link
Contributor

@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
Copy link
Contributor

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.

mikeal added a commit that referenced this pull request Aug 25, 2015
@mikeal mikeal merged commit 9356b6e into master Aug 25, 2015
@ghost ghost deleted the adds-governance branch November 30, 2015 20:19
unstoo added a commit to unstoo/nodejs.org that referenced this pull request Jul 11, 2019
unstoo added a commit to unstoo/nodejs.org that referenced this pull request Jul 14, 2019
alexandrtovmach pushed a commit that referenced this pull request Jul 15, 2019
* Getting started RU translation

A human translation of 'Getting started' article to Russian.

* Patch of ru translation

* ru translation patch #2

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

Successfully merging this pull request may close these issues.

6 participants