|
|
9.
|
|
|
With about 200 full time developers, OpenERP is evolving every day. The usability team continuously looks for ideas to simplify OpenERP for new users.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:27
|
|
|
10.
|
|
|
These ideas are discussed between OpenERP SA, the official partners and members of the community. In order to discuss about ideas, we have setup an open `usability team on Launchpad`_ to discuss every proposition.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:29
|
|
|
11.
|
|
|
You can also subscribe to the `usability mailing list`_ to be part of the main discussions about how to improve OpenERP's usability.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:31
|
|
|
12.
|
|
|
Once an improvement is approved by the usability managers, the community of OpenERP SA develops the software according to the proposed improvements. You can check the `developer guide`_ and `documentation process`_ for more information on how to contribute to OpenERP.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:33
|
|
|
13.
|
|
|
Main usability improvements are reported in this book as a set of guidelines. The usability team is responsible for synchronizing the book content with the best practices on OpenERP. If you want to contribute to this book, you can work on the `Launchpad documentation branch`_.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:36
|
|
|
14.
|
|
|
All changes done, regarding important improvements, will be posted on the `OpenERP blog`_ where you can also leave your comments, advice or ideas.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:38
|
|
|
15.
|
|
|
In order to benefit from the feedback from any visitor on this web site, everyone can leave a comment on any page of this book. The usability team will review all comments every month and update the book accordingly if required.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:42
|
|
|
16.
|
|
|
The book is written only in English, then `translated by community members`_ into several languages.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:44
|
|
|
17.
|
|
|
In order to check that all OpenERP modules respect the usability guidelines, the check of these guidelines is part of the quality certification process of new modules by OpenERP SA. So, we check that all official modules respect the above guidelines in order to make them become official.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:46
|
|
|
18.
|
|
|
The usability team is also in charge of educating the developer teams. So, when the usability team detects developments which do not conform to these guidelines, they must contact the authors and ask the author of the module to improve his code according to specific guidelines. In this feedback email, the usability team links to each guideline that was infringed.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:48
|
