2
.. i18n: .. _openerp-team:
4
.. i18n: Working in teams
5
.. i18n: ----------------
13
.. i18n: single: teams
26
.. i18n: Who are the different actors in the community of OpenERP.
28
Who are the different actors in the community of OpenERP.
37
.. i18n: single: contributors (teams)
38
.. i18n: single: teams; contributors
42
single: contributors (teams)
43
single: teams; contributors
46
.. i18n: Contributors are people who wants to help the project getting better, add
47
.. i18n: functionnality and improve stability. Everyone can contribute on the project
48
.. i18n: with his own knowledge by reporting bugs, purposing smart improvment and
49
.. i18n: posting patch.
51
Contributors are people who wants to help the project getting better, add
52
functionnality and improve stability. Everyone can contribute on the project
53
with his own knowledge by reporting bugs, purposing smart improvment and
56
.. i18n: The community team is available on launchpad: https://launchpad.net/~openerp-community
58
The community team is available on launchpad: https://launchpad.net/~openerp-community
60
.. i18n: Member of the quality and commiter team are automatically members of the community.
62
Member of the quality and commiter team are automatically members of the community.
64
.. i18n: Official Commiters
65
.. i18n: """"""""""""""""""
71
.. i18n: single: official commiters (teams)
72
.. i18n: single: teams; official commiters
76
single: official commiters (teams)
77
single: teams; official commiters
80
.. i18n: Official commiters are people allowed to commit in the community repository.
81
.. i18n: Those people are approved as commiters by the community once they've done
82
.. i18n: enought good patch and/or contributions in the project.
84
Official commiters are people allowed to commit in the community repository.
85
Those people are approved as commiters by the community once they've done
86
enought good patch and/or contributions in the project.
88
.. i18n: Their allow to :
92
.. i18n: * Purpose and post their own patch on bugs report.
93
.. i18n: * Review patches from contributors, comments and / or improve them.
94
.. i18n: * Commit well done patch or contribution in the community repository.
95
.. i18n: * Write a news on the Planet OpenERP RSS
97
* Purpose and post their own patch on bugs report.
98
* Review patches from contributors, comments and / or improve them.
99
* Commit well done patch or contribution in the community repository.
100
* Write a news on the Planet OpenERP RSS
102
.. i18n: The commiter team is available on launchpad: https://launchpad.net/~openerp-commiter
104
The commiter team is available on launchpad: https://launchpad.net/~openerp-commiter
106
.. i18n: Quality Team
107
.. i18n: """"""""""""
113
.. i18n: single: quality team (teams)
114
.. i18n: single: teams; quality team
118
single: quality team (teams)
119
single: teams; quality team
122
.. i18n: Quality team are people from Tiny sprl responsible for the quality of the
123
.. i18n: Official repository. They assume the stability and coherence of the Official
124
.. i18n: version by review the community patch and commit.
126
Quality team are people from Tiny sprl responsible for the quality of the
127
Official repository. They assume the stability and coherence of the Official
128
version by review the community patch and commit.
130
.. i18n: They're in charge to merge the commit from Community repository to Official
131
.. i18n: repository. "Extra_addons" and "Others" repository are not part of their
132
.. i18n: responsability.
134
They're in charge to merge the commit from Community repository to Official
135
repository. "Extra_addons" and "Others" repository are not part of their
138
.. i18n: If a commit isn't good enough, they must remove it from Community repository
139
.. i18n: and report it in the :ref:`bug tracker <bug-tracker-link>`. In other case, they
140
.. i18n: will apply the purposed commit in the Official version. Like this, everyone
141
.. i18n: will stay aware about what is or isn't accepted.
143
If a commit isn't good enough, they must remove it from Community repository
144
and report it in the :ref:`bug tracker <bug-tracker-link>`. In other case, they
145
will apply the purposed commit in the Official version. Like this, everyone
146
will stay aware about what is or isn't accepted.
148
.. i18n: The quality team is available on launchpad: https://launchpad.net/~openerp
150
The quality team is available on launchpad: https://launchpad.net/~openerp
158
.. i18n: Introduction
159
.. i18n: """"""""""""
164
.. i18n: As to help developers and contributors to take the right decision when
165
.. i18n: improving OpenERP, we set up experts teams for different management domains.
166
.. i18n: Only people that have a strong experience in OpenERP and the related domain can
167
.. i18n: apply as an expert. We have teams of accountants, manufacturing experts,
168
.. i18n: technical experts, services management experts, ...
170
As to help developers and contributors to take the right decision when
171
improving OpenERP, we set up experts teams for different management domains.
172
Only people that have a strong experience in OpenERP and the related domain can
173
apply as an expert. We have teams of accountants, manufacturing experts,
174
technical experts, services management experts, ...
176
.. i18n: Developers can contact our experts mailing list when they need feedback on
177
.. i18n: particular features to be developed. Please contact our experts only for new
178
.. i18n: developments related questions. They don't provide help on current features of
179
.. i18n: OpenERP. Most of our experts have very high positions in the company they work
180
.. i18n: for, so they don't have time to spent providing help or support.
182
Developers can contact our experts mailing list when they need feedback on
183
particular features to be developed. Please contact our experts only for new
184
developments related questions. They don't provide help on current features of
185
OpenERP. Most of our experts have very high positions in the company they work
186
for, so they don't have time to spent providing help or support.
188
.. i18n: Expert Teams
189
.. i18n: """"""""""""
195
.. i18n: single: expert team (teams)
196
.. i18n: single: teams; expert team
199
.. i18n: * Accounting: https://launchpad.net/~openerp-expert-accounting/+members
200
.. i18n: * Services Management: https://launchpad.net/~openerp-expert-service/+members
201
.. i18n: * Manufacturing Industries: https://launchpad.net/~openerp-expert-production/+members
204
single: expert team (teams)
205
single: teams; expert team
208
* Accounting: https://launchpad.net/~openerp-expert-accounting/+members
209
* Services Management: https://launchpad.net/~openerp-expert-service/+members
210
* Manufacturing Industries: https://launchpad.net/~openerp-expert-production/+members
212
.. i18n: Requesting Advices to A Team
213
.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
215
Requesting Advices to A Team
216
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
218
.. i18n: When you `create a specification <https://blueprints.launchpad.net/openobject/+addspec>`_
219
.. i18n: of a new feature on launchpad (called a blueprint), you can
220
.. i18n: assign an expert team as a drafter of the specifications. Then, you can click
221
.. i18n: on request feedback on your blueprint and assign this to an expert team.
223
When you `create a specification <https://blueprints.launchpad.net/openobject/+addspec>`_
224
of a new feature on launchpad (called a blueprint), you can
225
assign an expert team as a drafter of the specifications. Then, you can click
226
on request feedback on your blueprint and assign this to an expert team.
228
.. i18n: They will receive a notification email and will discuss about the requested
229
.. i18n: feature. The team will improve your specifications directly in your blueprint.
231
They will receive a notification email and will discuss about the requested
232
feature. The team will improve your specifications directly in your blueprint.
234
.. i18n: Translators team
235
.. i18n: """"""""""""""""
241
.. i18n: single: translators team (teams)
242
.. i18n: single: teams; translators team
246
single: translators team (teams)
247
single: teams; translators team
250
.. i18n: .. todo:: extend the 'Translators team' section
252
.. todo:: extend the 'Translators team' section
254
.. i18n: Community Team
255
.. i18n: """"""""""""""
261
.. i18n: single: community team (teams)
262
.. i18n: single: teams; community team
266
single: community team (teams)
267
single: teams; community team
270
.. i18n: .. todo:: extend the 'Community Team' section
272
.. todo:: extend the 'Community Team' section