Adds additional responsibilities to the website working group #727
Conversation
|
+1 |
| @@ -27,6 +27,10 @@ Its responsibilities are: | |||
| * Develop and maintain a build and automation system for `iojs.org`. | |||
| * Ensure the site is regularly updated with changes made to `io.js` like | |||
| releases and features. | |||
| * Documentation: maintain the docs build process and publish to `iojs.org`. See https://github.com/iojs/doc-tool (the source API docs are maintained and managed in core, not through this WG.) | |||
| * General marketing and social media initiatives (proposed sub-WG) | |||
| * Fostering io.js evangelism efforts (empowering speakers with materials, maintaining a list of interested speakers/interviewees, education, etc.) | |||
There was a problem hiding this comment.
Forgot a mention this is also potentially a sub-WG, but not sure now if we should pre-emptively say that for either (TMI?)
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
I just simplified the language for now by removing the thought of splitting it out later as the timeline for that is unknown
|
@iojs/tc |
|
(.. does that link work?) |
|
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'. |
|
Closing. Evangelism is it's own thing and we currently don't have the person-power to actually take on docs. |
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.