2
.. i18n: .. _openerp-team:
4
.. i18n: Working in teams
5
.. i18n: ----------------
14
.. i18n: single: teams
29
.. i18n: Who are the different actors in the community of OpenERP.
32
Who are the different actors in the community of OpenERP.
42
.. i18n: single: contributors (teams)
43
.. i18n: single: teams; contributors
48
single: contributors (teams)
49
single: teams; contributors
52
.. i18n: Contributors are people who wants to help the project getting better, add
53
.. i18n: functionnality and improve stability. Everyone can contribute on the project
54
.. i18n: with his own knowledge by reporting bugs, purposing smart improvment and
55
.. i18n: posting patch.
58
Contributors are people who wants to help the project getting better, add
59
functionnality and improve stability. Everyone can contribute on the project
60
with his own knowledge by reporting bugs, purposing smart improvment and
63
.. i18n: The community team is available on launchpad: https://launchpad.net/~openerp-community
66
The community team is available on launchpad: https://launchpad.net/~openerp-community
68
.. i18n: Member of the quality and commiter team are automatically members of the community.
71
Member of the quality and commiter team are automatically members of the community.
73
.. i18n: Official Commiters
74
.. i18n: """"""""""""""""""
81
.. i18n: single: official commiters (teams)
82
.. i18n: single: teams; official commiters
87
single: official commiters (teams)
88
single: teams; official commiters
91
.. i18n: Official commiters are people allowed to commit in the community repository.
92
.. i18n: Those people are approved as commiters by the community once they've done
93
.. i18n: enought good patch and/or contributions in the project.
96
Official commiters are people allowed to commit in the community repository.
97
Those people are approved as commiters by the community once they've done
98
enought good patch and/or contributions in the project.
100
.. i18n: Their allow to :
105
.. i18n: * Purpose and post their own patch on bugs report.
106
.. i18n: * Review patches from contributors, comments and / or improve them.
107
.. i18n: * Commit well done patch or contribution in the community repository.
108
.. i18n: * Write a news on the Planet OpenERP RSS
111
* Purpose and post their own patch on bugs report.
112
* Review patches from contributors, comments and / or improve them.
113
* Commit well done patch or contribution in the community repository.
114
* Write a news on the Planet OpenERP RSS
116
.. i18n: The commiter team is available on launchpad: https://launchpad.net/~openerp-commiter
119
The commiter team is available on launchpad: https://launchpad.net/~openerp-commiter
121
.. i18n: Quality Team
122
.. i18n: """"""""""""
129
.. i18n: single: quality team (teams)
130
.. i18n: single: teams; quality team
135
single: quality team (teams)
136
single: teams; quality team
139
.. i18n: Quality team are people from Tiny sprl responsible for the quality of the
140
.. i18n: Official repository. They assume the stability and coherence of the Official
141
.. i18n: version by review the community patch and commit.
144
Quality team are people from Tiny sprl responsible for the quality of the
145
Official repository. They assume the stability and coherence of the Official
146
version by review the community patch and commit.
148
.. i18n: They're in charge to merge the commit from Community repository to Official
149
.. i18n: repository. "Extra_addons" and "Others" repository are not part of their
150
.. i18n: responsability.
153
They're in charge to merge the commit from Community repository to Official
154
repository. "Extra_addons" and "Others" repository are not part of their
157
.. i18n: If a commit isn't good enough, they must remove it from Community repository
158
.. i18n: and report it in the :ref:`bug tracker <bug-tracker-link>`. In other case, they
159
.. i18n: will apply the purposed commit in the Official version. Like this, everyone
160
.. i18n: will stay aware about what is or isn't accepted.
163
If a commit isn't good enough, they must remove it from Community repository
164
and report it in the :ref:`bug tracker <bug-tracker-link>`. In other case, they
165
will apply the purposed commit in the Official version. Like this, everyone
166
will stay aware about what is or isn't accepted.
168
.. i18n: The quality team is available on launchpad: https://launchpad.net/~openerp
171
The quality team is available on launchpad: https://launchpad.net/~openerp
180
.. i18n: Introduction
181
.. i18n: """"""""""""
187
.. i18n: As to help developers and contributors to take the right decision when
188
.. i18n: improving OpenERP, we set up experts teams for different management domains.
189
.. i18n: Only people that have a strong experience in OpenERP and the related domain can
190
.. i18n: apply as an expert. We have teams of accountants, manufacturing experts,
191
.. i18n: technical experts, services management experts, ...
194
As to help developers and contributors to take the right decision when
195
improving OpenERP, we set up experts teams for different management domains.
196
Only people that have a strong experience in OpenERP and the related domain can
197
apply as an expert. We have teams of accountants, manufacturing experts,
198
technical experts, services management experts, ...
200
.. i18n: Developers can contact our experts mailing list when they need feedback on
201
.. i18n: particular features to be developed. Please contact our experts only for new
202
.. i18n: developments related questions. They don't provide help on current features of
203
.. i18n: OpenERP. Most of our experts have very high positions in the company they work
204
.. i18n: for, so they don't have time to spent providing help or support.
207
Developers can contact our experts mailing list when they need feedback on
208
particular features to be developed. Please contact our experts only for new
209
developments related questions. They don't provide help on current features of
210
OpenERP. Most of our experts have very high positions in the company they work
211
for, so they don't have time to spent providing help or support.
213
.. i18n: Expert Teams
214
.. i18n: """"""""""""
221
.. i18n: single: expert team (teams)
222
.. i18n: single: teams; expert team
225
.. i18n: * Accounting: https://launchpad.net/~openerp-expert-accounting/+members
226
.. i18n: * Services Management: https://launchpad.net/~openerp-expert-service/+members
227
.. i18n: * Manufacturing Industries: https://launchpad.net/~openerp-expert-production/+members
231
single: expert team (teams)
232
single: teams; expert team
235
* Accounting: https://launchpad.net/~openerp-expert-accounting/+members
236
* Services Management: https://launchpad.net/~openerp-expert-service/+members
237
* Manufacturing Industries: https://launchpad.net/~openerp-expert-production/+members
239
.. i18n: Requesting Advices to A Team
240
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
243
Requesting Advices to A Team
244
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
246
.. i18n: When you `create a specification <https://blueprints.launchpad.net/openobject/+addspec>`_
247
.. i18n: of a new feature on launchpad (called a blueprint), you can
248
.. i18n: assign an expert team as a drafter of the specifications. Then, you can click
249
.. i18n: on request feedback on your blueprint and assign this to an expert team.
252
When you `create a specification <https://blueprints.launchpad.net/openobject/+addspec>`_
253
of a new feature on launchpad (called a blueprint), you can
254
assign an expert team as a drafter of the specifications. Then, you can click
255
on request feedback on your blueprint and assign this to an expert team.
257
.. i18n: They will receive a notification email and will discuss about the requested
258
.. i18n: feature. The team will improve your specifications directly in your blueprint.
261
They will receive a notification email and will discuss about the requested
262
feature. The team will improve your specifications directly in your blueprint.
264
.. i18n: Translators team
265
.. i18n: """"""""""""""""
272
.. i18n: single: translators team (teams)
273
.. i18n: single: teams; translators team
278
single: translators team (teams)
279
single: teams; translators team
282
.. i18n: .. todo:: extend the 'Translators team' section
285
.. todo:: extend the 'Translators team' section
287
.. i18n: Community Team
288
.. i18n: """"""""""""""
295
.. i18n: single: community team (teams)
296
.. i18n: single: teams; community team
301
single: community team (teams)
302
single: teams; community team
305
.. i18n: .. todo:: extend the 'Community Team' section
308
.. todo:: extend the 'Community Team' section