Dolibarr Project

From Dolibarr Wiki

Return to developer
documentation index

File Doc dev.png

Return to user
documentation index
File Doc user.png

This page provides information on Dolibarr project organization, different roles of actors and actions to help.

Contents

Orientation.png Dolibarr history and future (Roadmap)

See page Origin, history and future roadmap of Dolibarr

Who.png Actors and their roles in the Dolibarr galaxy

The current Dolibarr team is a group of people, helped (or sponsored) by miscellaneous physicals or morals contributors (companies, foundations). The following chapters presents roles and functions occupied by everybody in the Dolibarr project management. This make possible to understand the way the project works. Some roles and functions are always waiting for candidates.

Volunteers to apply to a role in the project are invited to send a message on the dev mailing list of Dolibarr.

If you need information to participate as a developer, the page Developer FAQ How to be an official developer may be more helpfull.

The following links show a list of actors that works or have worked on Dolibarr project.


The following chapters shows the different developer roles, then every non-developer roles. All these roles contributes to Dolibarr project's activity.

Developers roles

Developer grade Yoda (GIT project and commit leader, all modules)

Goal/Permissions: Global management of Dolibarr project. Organize beta, create releases and package the standard distribution.

Have this role actualy:

Role need helper: No (by definition, this role is limited to the project leader and backups)

Note: All tasks to build a package for a new Dolibarr release are defined into the file build/makepack-howto.txt available into dolibarr sources.

Developer grade Jedi module X (GIT project and commit leader, for a particular module)

Goal/Permissions: Externalise development of new modules outside the core developer team.

Have this role actualy to work on modules (name - module):

Role need helper for module X: Yes, for all modules/features that does not exists or with no active developer (1 responsible by module). Please ask if you want this role with a new module idea on Dolibarr dev mailing-list.

Developer grade Admiral (GIT Commits for fix only patches)

Goal/Permissions: Develop, add or simply validate and commit, into GIT repository, some fix patches.

Only after a variable time (which can be very long) to the rank of Soldier, and if the quality of all patch that was sent is satisfactory, a Yoda in place will provide you direct GIT access. You become an Admiral of the alliance Dolibarr.

This title can't be requested. It is obtained by a decision or proposal of a Jedi or a Yoda who believes that you have submitted enough patches to be a serious Admiral. The Admiral GIT access, however, must be used only to commit translations or bug fixes reported on Doliforge (https://doliforge.org/tracker/?atid=246&group_id=144&func=browse or the forum (http://www.dolibarr.org/forum/). All GIT commits must necessarily include in its description (commit log field), the issue of bug corrected or the title of the forum message indicating the problem. Only translations escapes this constraint (no restrictions for translations). Failure to observe this constraint may lead to permission removing.

To submit new features, you must still send patch to the Dolibarr-dev Mailing-list (https://savannah.nongnu.org/mail/?group=dolibarr) or use the GIT push request system that does not need GIT write access.

Obtaining the rank of Admiral is as rare as limited. Dolibarr quality can not be achieved by a too large number of Admirals, and this does not means that there is not an important number of soldiers (submitting patches).

Role need helper: Yes (This role, however, is not achieved simply by postulating. See FAQ How to become an official developer for the circuit to follow)

Identified as having this role currently or recently (accounts validated into http://www.github.com, in alphabetical order): Click on name to see "contributor" and check their status (active contributor / withdrawn)

+ All developers with higher level.

Developer grade Z-6PO (GIT commiters to add translation patches)

Goal/Permissions: Integrate and commit into GIT, patches related to translation (or typographic fixes). No other changes.

Have this role actually:

+ All developers with higher level.

Role need helper: Yes (ideally, 1 Z-6PO for each language)

Articles on this topic: Translator documentation

Developer grade Soldier (Submit patch)

Goal/Permissions: Submit enhancements/fixes by sending patch.

Role need helper: Yes (no limit. Patch must be submited on the Dolibarr-dev Mailing-List (https://savannah.nongnu.org/mail/?group=dolibarr) or by GitHub push requests.

Have this role actually:

  • Number too high to be counted. Any Dolibarr users are potential soldiers.

Other roles on Dolibarr project

Role A: Hosting web site (http://www.dolibarr.org or local portal)

Goal: Provide a platform and exploit it to host the Dolibarr web site (based on Joomla).

Have this role actually:

Role need helper: Yes for other languages/countries (See page Create a Dolibarr local community).

Role B: Hosting demo site (http://demo.dolibarr.org/public/demo)

Goal: Provide a platform and exploit it to host the online Dolibarr demo (international version, autodetected language).

Have this role actually:

  • Dolibarr foundation

Role need helper: No

Role C1: Hosting wiki (http://wiki.dolibarr.org)

Goal: Provide a platform and exploit it to host the Dolibarr wiki (based on mediawiki)

Have this role actually:

Role need helper: No

Role C2: Hosting market place (http://wwww.dolistore.com)

Goal: Provide a market place to centralise all external modules (based on prestashop)

Have this role actually:

  • Dolibarr foundation

Role need helper: No

Role D: Hosting doliforge (http://www.doliforge.org)

Goal: Provide a development forge for Dolibarr modules developers (based on tuleap)

Have this role actually:

  • Dolibarr foundation

Role need helper: No

Role E1: Responsible of DoliWamp (Dolibarr installer for Windows)

Have this role actually:

Role need helper: No

Role E2: Responsible of DoliDeb+DoliRpm (Dolibarr installer for Ubuntu/Debian/Redhat/Fedora/Mandriva/OpenSuse)

Have this role actually:

Role need helper: No

Role E3: Responsible of DoliMamp (Dolibarr installer for Mac OS X)

Have this role actually:

  • Nobody

Role need helper: Yes

Role F: Tools to create modules using MDA (UML2Dolibarr)

Have this role actually or recently:

Role need helper: See Auguria company if help is required.

Role G: Management of Dolibarr foundation

Goal: Create and manage a foundation to promote dolibarr and help Dolibarr users.

Have this role actually:

Role H: Promote/Communicate on Dolibarr

Goal: Make communication for Dolibarr, on forums, news sites, press, etc... Write articles on Dolibarr web site.

Have this role actually:

  • The Dolibarr foundation
  • Role need helper. Thanks to volunteer to send a request on Dolibarr mailing-list.

Articles on this topic: Message samples used to announce new beta or release.

Role I: Dolibarr Tester

Goal: Test current development version of Dolibarr (GIT develop branch) and reports problems on mailing-list.

Have this role actually:

  • About 50 regular users have this role actually (number obtained by analysing messages on forum), more if we add temporary testers.

Role J: Administer domain names

Goal: Administer DNS of dolibarr domain names. Some are not used, just reserved to avoid cyber squatting. Ask us if you plan to use one of them to build a local Dolibarr community.

Have this role actually:

  • Laurent Destailleur (project leader) - dolibarr.org
  • Régis Houssin - dolibarr.be, dolibarr.cc, dolibarr.ch, dolibarr.co.uk, dolibarr.de, dolibarr.eu, dolibarr.fr, dolibarr.info, dolibarr.it, dolibarr.me, dolibarr.net, dolibarr.pro, dolibarr.us, dolistore.com, doliforge.com
  • Dolibarr foundation - dolibarr.com, dolibarr.asia, dolibarr.at, dolibarr.se, dolibarr.ru
  • 2Byte.es - dolibarr.es

Workcomputer.png The GIT access

The GIT server is hosted by http://www.github.com

  • Instructions to access GIT in read mode to get current development version are on this page
  • To request a write access, read FAQ How to be an official developer to known how project is organized and steps to do to reach this goal.

Communaute.png The Mailing-lists and groups of information on social networks

See page FAQ How to be inform about Dolibarr project ?

Lug.png Help the project

This is a list of task you can do to help the project.

If you are a developer

  • If you are a developer, join the Dolibarr team. See Developer FAQ for this.

If you speak a non english language

  • Translate Dolibarr in your language. See Translator documentation.
  • Submit articles to promote Dolibarr on informations web sites on your languages or your own web site. At least, a link to web site http://www.dolibarr.org is never a bad idea.

If you are not a developer, nor a translator

If you want to create a Dolibarr users' group or a local community

Lug.png DevCamps Organisation

See DevCamps Organisation for this.

Lug.png Donations

  • If you don't want to be a member of the Dolibarr foundation, you can still make a donation to help development:

Note that a list of public donors of most important donations can be found here.

Retrieved from "http://wiki.dolibarr.org/index.php/Dolibarr_Project"
Personal tools
  • Ask to contact@dolibarr.org to request an account to contribute to this documentation
  • Log in
In other languages
FrenchSpanish