Dolibarr Project

From Dolibarr Wiki

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

Contents

File:orientation.png Dolibarr history and future

See page Origin, history and future roadmap of Dolibarr

File: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 are have worked on Dolibarr project.


The following chapters shows the different developer roles in a first time and every non-developer roles. All these roles contributes to enhance Dolibarr.

Developers roles

Developer grade Yoda (CVS 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 backup)

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 (CVS project and commit leader, for a particular module)

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

Have this role actualy on work for special spanish VAT:

Have this role actualy on Module OSCommerceWS:

Have this role actualy on module Ciel compta:

Have this role actualy on Module Thelia:

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 (CVS Commits for fix only patches)

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

Only after a variable time (which can be very long) to the rank of Fighter, and if the quality of all patch that was sent is satisfactory, a Yoda in place will provide you direct CVS 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 CVS access, however, must be used to commit translations or bug fixes reported on Savannah or the forum (that is personal or corrections from a patch submitted by a Fighter). All CVS commits must necessarily include in its description (commit log field), the issue of Savannah 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, patches must still by send to the Dolibarr-dev Mailing-list.

Obtaining the rank of Admiral is as rare as limited. Dolibarr quality can not be achieved by a too large number of Admirals, but this does not means that there is not an important number of fighters (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 in savannah, 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 (CVS commiters to add translation patches)

Goal/Permissions: Integrate and commit into CVS, 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 Fighter (Submit patch by files)

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

Role need helper: Yes (no limit. Patch must be submited on the Dolibarr-dev Mailing-List. Click here to subscribe).

Have this role actually:

  • Number to high to be counted.

Developer grade Soldier (Users wich never send patches)

Goal/Permissions: Submit your first patch by mail to be upgraded to the Fighter level.

Role need helper: Yes (no limit. Patch must be submitted on the Dolibarr-dev Mailing-List. Click here to subscribe).

Have this role actually:

  • All Dolibarr users with a "developer feeling". Number to high to be counted.

Other roles on Dolibarr project

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

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

Have this role actually:

Role need helper: No

Role B: Hébergement site démo (http://demo.dolibarr.org/public/demo)

Goal: Provide a platform and exploit it to host the online Dolibarr demo.

Have this role actually:

Role need helper: No

Role C: Hébergement wiki (http://wiki.dolibarr.org/public/demo)

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

Have this role actually:

Role need helper: No

Role D: Responsible of DoliWamp distribution (Dolibarr installer for Windows)

Have this role actually:

Role need helper: No

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

Have this role actually:

Role need helper: No

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: Animation of Dolibarr web site

Goal: add news and articles in French and English on Dolibarr web site

Have this role actually:

  • Role need helper: Thanks to people who want to help to send a request on Dolibarr mailing-list.

Role I: Promote/Communicate on Dolibarr

Goal:

  • Make communication for Dolibarr, on forums, news sites, press, etc...
  • Update the wiki page Press reviews (Paper press and Online press).
  • Write articles on Dolibarr web site.

Have this role actually:

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

Role J: Dolibarr Tester

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

Have this role actually:

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

File:workcomputer.png The CVS access

The CVS server is hosted by Savannah.

  • Instructions to access CVS 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.

A graphical report of CVS commits on main branch is also available on following page.

File:communaute.png The Mailing-lists and groups of information on social networks

See page FAQ How to be inform about Dolibarr project ?

File: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

If you are not a developer, nor a translator

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

File:orientation.png Actions to do by project team

  • Install a cross backup between joomla / demo-wiki (to do)
  • Call for new developers (to do)
  • Release 2.8
Retrieved from "http://wiki.dolibarr.org/index.php/Dolibarr_Project"
Personal tools
In other languages
FrenchSpanish