Changes

Jump to navigation Jump to search

Developer FAQ

38 bytes added, 8 years ago
m
Minor English Grammatical Corrections (Up to Numbering System Changes)
<span id="Soldier">'''* Soldier'''</span>
The first thing that a person willing to help needs is to be familiar with the rules and standards developments.By reading the [[Developer documentation]], you have shown sufficient willingness to automatically become automatically '''Soldier''' (grade level '''Soldier'''). Most people that are interesting interested in Dolibarr development are in this cateogrycategory.
This grade is obtained without higher validation higher. It is a grade of principle, to start.
Due to the nature of this level, it is not possible to establish a list of all Dolibarr actors with this grade (list always changing and too long).
{{TemplateURLTasks}}
Easy to start tasks are task with have the property "Task opened to external developers" that is set to "yes". If the value is "no", forget it, this means the task will be processed by a Jedi-grade developer with grade Jedi.
At your first accepted patch (included in GIT by an Admiral, Jedi or Yoda), you automatically enter into the family of '''Fighters''' of the Dolibarr alliance.
The number of hunters is not limited. The more we are, the more stronger we will be strong.The hunters are the main force of the Dolibarr alliance Dolibarr.
A list of Dolibarr contributors with this grade is available on page [[:Category:Chasseur]]
<span id="Z-6PO">'''* Z-6PO'''</span>
If you are fluent in a language not present or poorly translated into Dolibarr, a '''Jedi''' or '''Yoda''' will grant GIT write access, so you can make changes and commits directly into the GIT sources of the project.
Create your git account then ask for write access on Dolibarr dev mailing-list ({{TemplateURLMLDev}}) to claim to be part of project as a Z-6PO for your language.
You can also read page [[Developer_FAQ#Get/update project sources |Get/update project sources ]] to know how to use the GIT server to commit your changes on language files. But commits must be limited to changes for translations purposes.
This grade can be obtained quickly enough. Just ask for it on mailing list.
A list of Dolibarr contributors with this grade is available on page [[:Category:Z-6PO]]
<span id="Admiral">'''* Admiral'''</span>
Only after you've held the rank of Fighter for a variable time (which can be very long) to the rank of a Fighter, and you've submitted many patches of suitable quality had been sent, a Yoda in place allows you to make GIT commits extended for cause of any patch.
You have become an '''Admiral''' of the Dolibarr alliance.
This title can't be asked, it requested. It is obtained by a decision or proposal of a '''Jedi''' or '''Yoda''' who believes that you have submitted enough patch patches to be a serious '''Admiral'''.
An '''Admiral''' GIT access, however, must be used to commit translations or bug fixes that are reported on bug tracker ({{TemplateURLBugs}}) or forum (such as personal fixes or fixes submitted by a '''Fighter''').
So all GIT commits you do must necessarily include in the description (the commit log field), the issue of bug corrected or the title of the forum message indicating the problem. Only a translation escapes this constraint (no restrictions for translations). Failure to observe this constraint may lead to downgrade to the rank of '''Fighter'''.
<span id="Jedi">'''* Jedi'''</span>
This is even Only after holding the rank of Adminral for a variable time (probably the longest of all) to the rank of Admiral, and the quality of GIT bug fixes or patches sent is satisfactory, that a Yoda will tell you that you are authorized to perform commits without restrictions, included including new features, however . However you will still have to explain to all Yoda what you want to do to give back a "go".
You will then become a '''Jedi'''.
There may be temporary restrictions on commits, defined by a Yoda, for example due to a close release.
<span id="Yoda">'''* Yoda'''</span>
There is are about 1 to 5 '''Yoda'''. It's the overall management of project development. This ranking is obtained by inheritance or vote. For example, for example it can be achieved after a vote organized by a Yoda making retirement.
A list of Dolibarr contributors with this grade is available on page [[:Category:Yoda]]
'''* And Darth Vader?'''
There is are some parasites parasitic people that pollute the forum or mailing-list with aggressive messages, which slows the development of Dolibarr rather than offering constructive criticism to help improve. Some are very strong bad liver and bad tone. Such people are Darth Vaders.Fortunately, statistically, there is only one or two Dark Vador Darth Vader per year ...
= Current team =
= Change my numbering system after start =
If the new numbering system does not conflict with the old one, to change the numbering rule, just go on to menu Setup - Modules - Invoice setup and choose the new numbering rule in the list.If the new rule can crete create conflicts with old one, it will be necessary to rename old existing references. This can be do done by a SQL request.For example, to go from numbering module Jupiter (FYYYYMM99) to Terre (FAYYMM-999), you can run the folloing following request:
<source lang="sql">
update llx_facture set facnumber=concat('FA',substr(facnumber,4,4),'-',substr(facnumber,8))
</source>
For example, to rename references from modele model FAYYMM999 to Terre (FAYYMM-999), you can ru run the following request:
<source lang="sql">
update llx_facture set facnumber=concat('FA',substr(facnumber,3,4),'-',substr(CONCAT('0000',substr(facnumber,7)),-4))
3

edits

Navigation menu