@@ -76,6 +76,107 @@ Its responsibilities are:
76
76
The current members can be found in their
77
77
[ README] ( https://github.com/iojs/build#people ) .
78
78
79
+ ### Tracing
80
+
81
+ The tracing working group's purpose is to increase the
82
+ transparency of software written in io.js.
83
+
84
+ Its responsibilities are:
85
+ * Collaboration with V8 to integrate with ` trace_event ` .
86
+ * Maintinence and iteration on AsyncWrap.
87
+ * Maintinence and improvements to system tracing support (DTrace, LTTng, etc).
88
+ * Documention of tracing and debugging techniques.
89
+ * Fostering a tracing and debugging ecosystem.
90
+
91
+ The current members can be found in their
92
+ [ README] ( https://github.com/iojs/tracing-wg#people ) .
93
+
94
+ ### i18n
95
+
96
+ The i18n working groups handle more than just translations. They
97
+ are endpoints for community members to collaborate with each
98
+ other in their language of choice.
99
+
100
+ Each team is organized around a common spoken language. Each
101
+ language community might then produce multiple localizations for
102
+ various project resources.
103
+
104
+ Their responsibilities are:
105
+ * Translation of any io.js materials they believe are relevant to their
106
+ community.
107
+ * Review processes for keeping translations up
108
+ to date and of high quality.
109
+ * Social media channels in their language.
110
+ * Promotion of io.js speakers for meetups and conferences in their
111
+ language.
112
+
113
+ Membership is maintained by each language community.
114
+
115
+ * [ iojs-bg] ( http://github.com/iojs/iojs-bg )
116
+ * [ iojs-bn] ( http://github.com/iojs/iojs-bn )
117
+ * [ iojs-cn] ( http://github.com/iojs/iojs-cn )
118
+ * [ iojs-cs] ( http://github.com/iojs/iojs-cs )
119
+ * [ iojs-da] ( http://github.com/iojs/iojs-da )
120
+ * [ iojs-de] ( http://github.com/iojs/iojs-de )
121
+ * [ iojs-el] ( http://github.com/iojs/iojs-el )
122
+ * [ iojs-es] ( http://github.com/iojs/iojs-es )
123
+ * [ iojs-fa] ( http://github.com/iojs/iojs-fa )
124
+ * [ iojs-fi] ( http://github.com/iojs/iojs-fi )
125
+ * [ iojs-fr] ( http://github.com/iojs/iojs-fr )
126
+ * [ iojs-he] ( http://github.com/iojs/iojs-he )
127
+ * [ iojs-hi] ( http://github.com/iojs/iojs-hi )
128
+ * [ iojs-hu] ( http://github.com/iojs/iojs-hu )
129
+ * [ iojs-id] ( http://github.com/iojs/iojs-id )
130
+ * [ iojs-it] ( http://github.com/iojs/iojs-it )
131
+ * [ iojs-ja] ( http://github.com/iojs/iojs-ja )
132
+ * [ iojs-ka] ( http://github.com/iojs/iojs-ka )
133
+ * [ iojs-ko] ( http://github.com/iojs/iojs-ko )
134
+ * [ iojs-mk] ( http://github.com/iojs/iojs-mk )
135
+ * [ iojs-nl] ( http://github.com/iojs/iojs-nl )
136
+ * [ iojs-no] ( http://github.com/iojs/iojs-no )
137
+ * [ iojs-pl] ( http://github.com/iojs/iojs-pl )
138
+ * [ iojs-pt] ( http://github.com/iojs/iojs-pt )
139
+ * [ iojs-ro] ( http://github.com/iojs/iojs-ro )
140
+ * [ iojs-ru] ( http://github.com/iojs/iojs-ru )
141
+ * [ iojs-sv] ( http://github.com/iojs/iojs-sv )
142
+ * [ iojs-ta] ( http://github.com/iojs/iojs-ta )
143
+ * [ iojs-tr] ( http://github.com/iojs/iojs-tr )
144
+ * [ iojs-tw] ( http://github.com/iojs/iojs-tw )
145
+ * [ iojs-uk] ( http://github.com/iojs/iojs-uk )
146
+ * [ iojs-vi] ( http://github.com/iojs/iojs-vi )
147
+
148
+ ### Evangelism
149
+
150
+ The evangelism working group promotes the accomplishments
151
+ of io.js and lets the community know how they can get involved.
152
+
153
+ Their responsibilities are:
154
+ * Project messaging.
155
+ * Official project social media.
156
+ * Promotion of speakers for meetups and conferences.
157
+ * Promotion of community events.
158
+ * Publishing regular update summaries and other promotional
159
+ content.
160
+
161
+ The current members can be found in their
162
+ [ README] ( https://github.com/iojs/evangelism#people ) .
163
+
164
+ ### Roadmap
165
+
166
+ The roadmap working group is responsible for user community outreach
167
+ and the translation of their concerns into a plan of action for io.js.
168
+
169
+ The final [ ROADMAP] ( ./ROADMAP.md ) document is still owned by the TC and requires
170
+ the same approval for changes as any other project asset.
171
+
172
+ Their responsibilities are:
173
+ * Attract and summarize user community needs and feedback.
174
+ * Find or potentially create tools that allow for broader participation.
175
+ * Create Pull Requests for relevant changes to [ Roadmap.md] ( ./ROADMAP.md )
176
+
177
+ The current members can be found in their
178
+ [ README] ( https://github.com/iojs/roadmap#people ) .
179
+
79
180
## Starting a WG
80
181
81
182
A Working Group is established by first defining a charter that can be
0 commit comments