Skip to content

Adds additional responsibilities to the website working group - #727

Closed
snostorm wants to merge 2 commits into
nodejs:v1.xfrom
snostorm:patch-1
Closed

snostorm wants to merge 2 commits into
nodejs:v1.xfrom
snostorm:patch-1

Conversation

@snostorm

@snostorm snostorm commented Feb 5, 2015

Copy link
Copy Markdown

This might be a bit verbose as is, although I think the examples help clarify the intent.

Of course, pending general TC approval of the scope we've said we can take on / help develop.

@mikeal

mikeal commented Feb 5, 2015

Copy link
Copy Markdown
Contributor

+1

Comment thread WORKING_GROUPS.md Outdated

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Forgot a mention this is also potentially a sub-WG, but not sure now if we should pre-emptively say that for either (TMI?)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sub-WG isn't really a thing. this is covered in WORKING_GROUPS but basically once something has a big enough community behind it we spin out a WG and when that work was already handled by a WG then that WG and the TC have to approve the charter, but the WG concept is essentially flat (although we expect a lot of cross-collaboration between groups as they find necessary).

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just simplified the language for now by removing the thought of splitting it out later as the timeline for that is unknown

@Fishrock123

Copy link
Copy Markdown
Contributor

@iojs/tc

@Fishrock123

Copy link
Copy Markdown
Contributor

(.. does that link work?)

@bnoordhuis

Copy link
Copy Markdown
Member

It should but it doesn't... Summoning the @iojs/tc.

LGTM although IMO 'empowering' is a terrible word, on par with 'thought leadership' and 'synergy'.

@mscdex mscdex added the doc Issues and PRs related to Node.js documentation. label Mar 22, 2015
@Fishrock123

Copy link
Copy Markdown
Contributor

Closing. Evangelism is it's own thing and we currently don't have the person-power to actually take on docs.

@Fishrock123 Fishrock123 closed this Apr 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to Node.js documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants