Dolibarr Project: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 24: Line 24:
== Developers roles ==
== Developers roles ==


=== Developer grade [[Developer_FAQ#Yoda|Yoda]] (CVS project and commit leader, all modules) ===
=== Developer grade [[Developer_FAQ#Yoda|Yoda]] (GIT project and commit leader, all modules) ===


Goal/Permissions: Global management of Dolibarr project. Organize beta, create releases and package the standard distribution.
Goal/Permissions: Global management of Dolibarr project. Organize beta, create releases and package the standard distribution.
Line 37: Line 37:
All tasks to build a package for a new Dolibarr release are defined into the file '''build/makepack-howto.txt''' available into dolibarr sources.
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 [[Developer_FAQ#Jedi|Jedi]] module X (CVS project and commit leader, for a particular module) ===
=== Developer grade [[Developer_FAQ#Jedi|Jedi]] module X (GIT project and commit leader, for a particular module) ===


Goal/Permissions: Externalise development of new modules outside the core developer team.
Goal/Permissions: Externalise development of new modules outside the core developer team.
Line 47: Line 47:
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.
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 [[Developer_FAQ#Admiral|Admiral]] (CVS Commits for fix only patches) ===
=== Developer grade [[Developer_FAQ#Admiral|Admiral]] (GIT Commits for fix only patches) ===


Goal/Permissions: Develop, add or simply validate and commit, into CVS repository, some '''fix 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 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.
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 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 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.
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 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 GIT 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).
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).
Line 66: Line 66:
+ All developers with higher level.
+ All developers with higher level.


=== Developer grade [[Developer_FAQ#Z-6PO|Z-6PO]] (CVS commiters to add translation patches) ===
=== Developer grade [[Developer_FAQ#Z-6PO|Z-6PO]] (GIT commiters to add translation patches) ===


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


Have this role actually:
Have this role actually:
Line 198: Line 198:
=== Role J: Dolibarr Tester ===
=== Role J: Dolibarr Tester ===


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


Have this role actually:
Have this role actually:
Line 212: Line 212:
* [http://2byte.es 2Byte.es] for dolibarr.es
* [http://2byte.es 2Byte.es] for dolibarr.es


= [[File:workcomputer.png]] The CVS access =
= [[File:workcomputer.png]] The GIT access =


The CVS server is hosted by Savannah.
{{ToComplete}}
* Instructions to access CVS in read mode to get current development version are on [https://savannah.nongnu.org/cvs/?group=dolibarr this page]
* To request a write access, read [[Developer_FAQ#How_to_be_an_official_developer|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 [http://www.nltechno.com/stats/dolibarr/cvschangelogbuilder_dolibarr.html following page].


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

Navigation menu