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

Add i18n, tracing, roadmap and evangelism working groups #911

Closed
wants to merge 3 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
102 changes: 102 additions & 0 deletions WORKING_GROUPS.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,108 @@ Its responsibilities are:
The current members can be found in their
[README](https://github.com/iojs/build#people).

### Tracing

The tracing working group's purpose is to increase the
transparency of software written in io.js.

Its responsibilities are:
* Collaboration with V8 to integrate with `trace_event`.
* Maintinence and iteration on AsyncWrap.
Copy link
Contributor

Choose a reason for hiding this comment

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

maintenance?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is the third document i've misspelled this word in this week. sigh

Copy link
Contributor

Choose a reason for hiding this comment

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

Whoops, missed this one :P

* Maintinence and improvements to system tracing support (DTrace, LTTng, etc).
* Documention of tracing and debugging techniques.
* Fostering a tracing and debugging ecosystem.

The current members can be found in their
[README](https://github.com/iojs/tracing-wg#people).

### i18n

The i18n working groups handle more than just translations. They
are endpoints for community members to collaborate with each
other in their language of choice.

Each team is organized around a common spoken language. Each
language community might then produce multiple localizations for
various project resources.

Their responsibilities are:
* Translationg of any io.js materials they believe are relevant to their
Copy link
Contributor

Choose a reason for hiding this comment

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

Translating - or translation?

Copy link
Contributor

Choose a reason for hiding this comment

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

Fixed in merge.

community.
* Review processes for keeping translations up
to date and of high quality.
* Social media channels in their language.
* Promotion of io.js speakers for meetups and conferences in their
language.

Membership is maintained by each language community.

* [iojs-bg](http://github.com/iojs/iojs-bg)
* [iojs-bn](http://github.com/iojs/iojs-bn)
Copy link
Contributor

Choose a reason for hiding this comment

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

is there any alternative way to show this list? maybe a github-flavored table? already with the number of languages we have (+more later), this list is really long and might grow out of proportion

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we have 2 or 3 more already, but it will slow down naturally soon enough. i don't see how a table would work

Copy link
Contributor

Choose a reason for hiding this comment

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

okay. i know a list is more, i guess, functional, but it just seemed to take up my entire page when i scrolled by it.

* [iojs-cn](http://github.com/iojs/iojs-cn)
* [iojs-cs](http://github.com/iojs/iojs-cs)
* [iojs-da](http://github.com/iojs/iojs-da)
* [iojs-de](http://github.com/iojs/iojs-de)
* [iojs-el](http://github.com/iojs/iojs-el)
* [iojs-es](http://github.com/iojs/iojs-es)
* [iojs-fa](http://github.com/iojs/iojs-fa)
* [iojs-fi](http://github.com/iojs/iojs-fi)
* [iojs-fr](http://github.com/iojs/iojs-fr)
* [iojs-he](http://github.com/iojs/iojs-he)
* [iojs-hi](http://github.com/iojs/iojs-hi)
* [iojs-hu](http://github.com/iojs/iojs-hu)
* [iojs-id](http://github.com/iojs/iojs-id)
* [iojs-it](http://github.com/iojs/iojs-it)
* [iojs-ja](http://github.com/iojs/iojs-ja)
* [iojs-ka](http://github.com/iojs/iojs-ka)
* [iojs-ko](http://github.com/iojs/iojs-ko)
* [iojs-mk](http://github.com/iojs/iojs-mk)
* [iojs-nl](http://github.com/iojs/iojs-nl)
* [iojs-no](http://github.com/iojs/iojs-no)
* [iojs-pl](http://github.com/iojs/iojs-pl)
* [iojs-pt](http://github.com/iojs/iojs-pt)
* [iojs-ro](http://github.com/iojs/iojs-ro)
* [iojs-ru](http://github.com/iojs/iojs-ru)
* [iojs-sv](http://github.com/iojs/iojs-sv)
* [iojs-ta](http://github.com/iojs/iojs-ta)
* [iojs-tr](http://github.com/iojs/iojs-tr)
* [iojs-tw](http://github.com/iojs/iojs-tw)
* [iojs-uk](http://github.com/iojs/iojs-uk)
* [iojs-vi](http://github.com/iojs/iojs-vi)

### Evangelism

The evangelism working group promotes the accomplishments
of io.js and let's the community know how they can get involved.
Copy link
Contributor

Choose a reason for hiding this comment

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

i don't think "let's" gets an apostrophe here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

you're right, i'll work on better copy.

Copy link
Contributor

Choose a reason for hiding this comment

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

Fixed in merge.


Their responsibilities are:
* Project messaging.
* Official project social media.
* Promotion of speakers for meetups and conferences.
* Promotion of community events.
* Publishing regular update summaries and other promotional
content.

The current members can be found in their
[README](https://github.com/iojs/evangelism#people).

### Roadmap

The roadmap working group is responsible for user community outreach
and the translation of their concerns in to a plan
Copy link
Contributor

Choose a reason for hiding this comment

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

in to -> into

Copy link
Contributor

Choose a reason for hiding this comment

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

Fixed in merge.

of action for io.js.

The final [ROADMAP](./ROADMAP.md) document is still owned by the TC and requires
the same approval for changes as any other project asset.

Their responsibilities are:
* Attract and summarize user community needs and feedback.
* Find or potentially create tools that allow for broader participation.
* Create Pull Requests for relevant changes to [Roadmap.md](./ROADMAP.md)

The current members can be found in their
[README](https://github.com/iojs/roadmap#people).

## Starting a WG

A Working Group is established by first defining a charter that can be
Expand Down