~openerp-community/openobject-doc/ksa-openobject-doc-6.0

.. i18n: OpenERP is a full-featured business application suite, with more than 700 modules. Despite the complexity of technical work and the importance of the community members in the development of such a huge project, our goal is to make software that is easy to use, user friendly, and consistent while remaining fully open.

OpenERP is a full-featured business application suite, with more than 700 modules. Despite the complexity of technical work and the importance of the community members in the development of such a huge project, our goal is to make software that is easy to use, user friendly, and consistent while remaining fully open.

.. i18n: That's one of our main challenges: provide tons of features while remaining easy to use.

That's one of our main challenges: provide tons of features while remaining easy to use.

.. i18n: OpenERP SA has setup a usability team whose role is to continuously simplify the software, its installation and its configuration. This team is responsible for maintaining this document that covers all usability guidelines for OpenERP developers.

OpenERP SA has setup a usability team whose role is to continuously simplify the software, its installation and its configuration. This team is responsible for maintaining this document that covers all usability guidelines for OpenERP developers.

.. i18n: The guide is in two parts: one description of every concept of OpenERP and their impacts on usability and a set of guidelines at the end of the book.

The guide is in two parts: one description of every concept of OpenERP and their impacts on usability and a set of guidelines at the end of the book.

.. i18n: A goal for this manual is to include the opinions, advice and help of the community. Indeed, everyone can contribute to the writing of the usability manual thanks to the tools used to write it. The notes of the Usability team will be inserted on the web site and in the manual. The community can also add notes or send its ideas.

A goal for this manual is to include the opinions, advice and help of the community. Indeed, everyone can contribute to the writing of the usability manual thanks to the tools used to write it. The notes of the Usability team will be inserted on the web site and in the manual. The community can also add notes or send its ideas.

.. i18n: Continuous improvement process

.. i18n: ------------------------------

Continuous improvement process

------------------------------

.. i18n: With about 200 full time developers, OpenERP is evolving every day. The usability team continuously looks for ideas to simplify OpenERP for new users.

With about 200 full time developers, OpenERP is evolving every day. The usability team continuously looks for ideas to simplify OpenERP for new users.

.. i18n: 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.

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.

.. i18n: You can also subscribe to the `usability mailing list`_ to be part of the main discussions about how to improve OpenERP's usability.

You can also subscribe to the `usability mailing list`_ to be part of the main discussions about how to improve OpenERP's usability.

.. i18n: 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.

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.

.. i18n: 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`_.

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`_.

.. i18n: All changes done, regarding important improvements, will be posted on the `OpenERP blog`_ where you can also leave your comments, advice or ideas.

All changes done, regarding important improvements, will be posted on the `OpenERP blog`_ where you can also leave your comments, advice or ideas.

.. i18n: 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.

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.

.. i18n: The book is written only in English, then `translated by community members`_ into several languages.

The book is written only in English, then `translated by community members`_ into several languages.

.. i18n: 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.

100

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.

101

102

.. i18n: 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.

103

104

105

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.

106

107

.. i18n: Having set this process, a full-time team of several developers and functional experts, we expect OpenERP's usability to improve very quickly over time. If you want to propose a new improvement, the easiest way is to `write to the usability mailing list`_ with your suggestion.

108

109

110

Having set this process, a full-time team of several developers and functional experts, we expect OpenERP's usability to improve very quickly over time. If you want to propose a new improvement, the easiest way is to `write to the usability mailing list`_ with your suggestion.

111

112

.. i18n: If your improvement is validated by the usability team, we will assign a developer and a member of the usability team will improve the guidelines.

113

114

115

If your improvement is validated by the usability team, we will assign a developer and a member of the usability team will improve the guidelines.

116

117

.. i18n: .. _usability mailing list:

118

.. i18n: .. _usability team on Launchpad: https://launchpad.net/~openerp-expert-ergonomy

119

.. i18n: .. _developer guide: ../../developer/index.html

120

.. i18n: .. _documentation process:

121

.. i18n: ../../contribute/08_documentation_process.html

122

.. i18n: .. _Launchpad documentation branch:

123

.. i18n: https://code.launchpad.net/~openerp-community/openobject-doc/trunk

124

.. i18n: .. _OpenERP blog: http://usability-openerp.blogspot.com/

125

.. i18n: .. _translated by community members:

126

.. i18n: ../../contribute/09_documentation_translation.html

127

.. i18n: .. _write to the usability mailing list:

128

.. i18n: mailto:openerp-expert-ergonomy@lists.launchpad.net

129

130

131

.. _usability mailing list:

132

.. _usability team on Launchpad: https://launchpad.net/~openerp-expert-ergonomy

133

.. _developer guide: ../../developer/index.html

134

.. _documentation process:

135

../../contribute/08_documentation_process.html

136

.. _Launchpad documentation branch:

137

https://code.launchpad.net/~openerp-community/openobject-doc/trunk

138

.. _OpenERP blog: http://usability-openerp.blogspot.com/

139

.. _translated by community members:

140

../../contribute/09_documentation_translation.html

141

.. _write to the usability mailing list:

142

mailto:openerp-expert-ergonomy@lists.launchpad.net

Older »