14
Who are the different actors in the community of OpenERP.
20
single: contributors (teams)
21
single: teams; contributors
24
Contributors are people who wants to help the project getting better, add
25
functionnality and improve stability. Everyone can contribute on the project
26
with his own knowledge by reporting bugs, purposing smart improvment and
29
The community team is available on launchpad: https://launchpad.net/~openerp-community
31
Member of the quality and commiter team are automatically members of the community.
37
single: official commiters (teams)
38
single: teams; official commiters
41
Official commiters are people allowed to commit in the community repository.
42
Those people are approved as commiters by the community once they've done
43
enought good patch and/or contributions in the project.
47
* Purpose and post their own patch on bugs report.
48
* Review patches from contributors, comments and / or improve them.
49
* Commit well done patch or contribution in the community repository.
50
* Write a news on the Planet OpenERP RSS
52
The commiter team is available on launchpad: https://launchpad.net/~openerp-commiter
58
single: quality team (teams)
59
single: teams; quality team
62
Quality team are people from Tiny sprl responsible for the quality of the
63
Official repository. They assume the stability and coherence of the Official
64
version by review the community patch and commit.
66
They're in charge to merge the commit from Community repository to Official
67
repository. "Extra_addons" and "Others" repository are not part of their
70
If a commit isn't good enough, they must remove it from Community repository
71
and report it in the :ref:`bug tracker <bug-tracker-link>`. In other case, they
72
will apply the purposed commit in the Official version. Like this, everyone
73
will stay aware about what is or isn't accepted.
75
The quality team is available on launchpad: https://launchpad.net/~openerp
83
As to help developers and contributors to take the right decision when
84
improving OpenERP, we set up experts teams for different management domains.
85
Only people that have a strong experience in OpenERP and the related domain can
86
apply as an expert. We have teams of accountants, manufacturing experts,
87
technical experts, services management experts, ...
89
Developers can contact our experts mailing list when they need feedback on
90
particular features to be developed. Please contact our experts only for new
91
developments related questions. They don't provide help on current features of
92
OpenERP. Most of our experts have very high positions in the company they work
93
for, so they don't have time to spent providing help or support.
99
single: expert team (teams)
100
single: teams; expert team
103
* Accounting: https://launchpad.net/~openerp-expert-accounting/+members
104
* Services Management: https://launchpad.net/~openerp-expert-service/+members
105
* Manufacturing Industries: https://launchpad.net/~openerp-expert-production/+members
107
Requesting Advices to A Team
108
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
110
When you `create a specification <https://blueprints.launchpad.net/openobject/+addspec>`_
111
of a new feature on launchpad (called a blueprint), you can
112
assign an expert team as a drafter of the specifications. Then, you can click
113
on request feedback on your blueprint and assign this to an expert team.
115
They will receive a notification email and will discuss about the requested
116
feature. The team will improve your specifications directly in your blueprint.
122
single: translators team (teams)
123
single: teams; translators team
126
.. todo:: extend the 'Translators team' section
132
single: community team (teams)
133
single: teams; community team
136
.. todo:: extend the 'Community Team' section