|
|
66.
|
|
|
Developers can contact our experts mailing list when they need feedback on particular features to be developed. Please contact our experts only for new development related questions. They don't provide help on current features of OpenERP. Most of our experts have very senior positions in the company they work for, so they don't have time to spend providing help or support.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/02_working_in_teams.rst:116
|
|
|
75.
|
|
|
When you `create a specification <https://blueprints.launchpad.net/openobject/+addspec>`_ for a new feature on launchpad (called a blueprint), you can assign an expert team as a drafter of the specification. Then, you can click on request feedback on your blueprint and assign this to an expert team.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/02_working_in_teams.rst:134
|
|
|
78.
|
|
|
The translation teams are in charge of the translation of OpenERP in a specific language. The list of current translation teams can be found here: https://translations.launchpad.net/+groups/openobject-translators
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/02_working_in_teams.rst:150
|
|
|
79.
|
|
|
For more information regarding OpenERP translations and the corresponding process, please see the :ref:`translating_software` section.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/02_working_in_teams.rst:153
|
|
|
81.
|
|
|
Making a merge proposal of your own code is the way to integrate your work in the OpenERP project. You can request a merge proposal either on OpenERP's branch or OpenERP community's branch. In every project the process is the same and you can get the basic documentation here: https://help.launchpad.net/Code/Review
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/02_working_in_teams.rst:159
|
|
|
95.
|
|
|
The planets are places where partners, developers and contributors express their thoughts about the Open Object project. It's an aggregate of the personal blogs of partners and contributors. We use them to announce new developments, features and events on OpenERP and Open Object.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/03_planet.rst:12
|
|
|
100.
|
|
|
Our marketing and editorial team will review the Open Object planet frequently. When they notice good announcements, they will write an announcement and publish on the OpenERP planet. If the new feature is very good, we may also write a press release based on our article.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/03_planet.rst:25
|
|
|
114.
|
|
|
The new development process uses Bazaar via launchpad.net instead of Subversion. Bazaar offers flexibility with this distributed model. You can see our branches on https://code.launchpad.net/~openerp.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/04_using_bazaar.rst:12
|
|
|
134.
|
|
|
To become a committer a contributor must show interest on working for openerp project and ability to do it properly as selection is based on merit. It can be by proposing bug fixes, features requested on our :ref:`bug tracker <bug-tracker-link>` system. You can even suggest additional modules and/or functionality on our :ref:`bug tracker <bug-tracker-link>` system.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/04_using_bazaar.rst:49
|
|
|
137.
|
|
|
report and suggest your work via your new branch to our :ref:`bug tracker <bug-tracker-link>` system (there are two ways: bugs report for bug and blueprint for idea / functionality)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/contribute/04_using_bazaar.rst:62
|
