This repository has been archived by the owner on Mar 25, 2018. It is now read-only.
Update membership section of GOVERNANCE #54
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
||
| Membership in the Node.js Documentation WG entails the following access: | ||
|
|
||
| * Membership in the [Node.js Documentation Slack][nodejs-doc-slack]. |
There was a problem hiding this comment.
I started a Slack team because:
- A real-time channel of communications has proven useful to other WGs,
- The existing Gitter channel was a bit of a ghost town,
- Slack is a bit more user-friendly for non-technical folks than IRC or Gitter,
- The integrations for Slack making keeping track of changes to the docs easier.
|
If we've moved to Slack, which I definitely think we should, then can we remove the gitter badge from the readme and officially close down the gitter channel if there's anyone left in it? |
…in nodejs.org repo"
|
Everything looks like it was addressed to LGTM. |
|
Merging this now. Thanks all! |
chrisdickinson
added a commit
that referenced
this pull request
Jan 22, 2016
Update membership section of GOVERNANCE
|
apologies for not finding the time to review this after being pulled in, it sounds like it's going well though so +1! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While running through the responses to the call for membership, I realized that the existing GOVERNANCE document was a bit lax on details for membership. Specifically, it did not answer:
In addition, the CONTRIBUTING doc was a bit off from where we're at right now: it's expected, at least in the near term future, that we'll be operating primarily in the nodejs/node repo.
This PR attempts to address the questions above and is meant as jumping off point for discussion! I'm going to cc the folks who have publicly raised their hand to help out on this issue too, to make sure they're OK with all of this. In addition, I will reach out privately to all Node collaborators who have touched the docs in the last 6 months who are not part of the Docs WG.
This does not address process, goal-setting, or tooling, but that should follow in subsequent PRs to be discussed by the WG and CTC.
/cc @nodejs/documentation
/cc @mikeal — could you make sure this looks okay w/r/t WG setup?
/cc @rvagg — You've expressed interest in the operation of the Docs WG in other issues, and I'd love your thoughts on this.
/cc @kosamari, @a0viedo — you've both raised your hands to help out (thank you!), are there any questions you have that the membership section doesn't answer? Are the responsibilities and access outlined here in line with what you'd expect, or is it too much?