83
edits
Developer FAQ: Difference between revisions
Jump to navigation
Jump to search
Undo revision 60362 by Nexgen (talk)
Tag: Undo |
|||
| Line 12: | Line 12: | ||
This page contains some frequently asked questions related to Dolibarr development. For frequently asked questions on other topics, read page [[User FAQ]]. | This page contains some frequently asked questions related to Dolibarr development. For frequently asked questions on other topics, read page [[User FAQ]]. | ||
= | =How to be an official developer= | ||
In the galaxy of the Dolibarr project, there are several actors with different levels / grades. | |||
The number of developers is important so contributions and changes must be controlled and validated (both for functional needs and for coding). | |||
For this reason, the write access on the source (GIT) is limited and governed by an organization that is described in the following. | |||
Each developer has a ''grade'' depending on seniority and the past. The level of authorization of a person on the project increases with the stages of promotion in grade. | |||
The course of a Dolibarr developer passes through these steps, which are classified by a title familiar to fans of science fiction. Here are the steps. | |||
It is important to understand that this organization has the sole purpose of improving the quality of Dolibarr and it is necessary that it is rigorously used. | |||
The ranks of contributors to the Dolibarr project, and what to do to reach this rank, are defined into page [[Dolibarr_Project#Developers_roles|Dolibarr Project]] in chapter '''Developers roles'''. | |||
=Current team= | =Current team= | ||
| Line 48: | Line 52: | ||
If the new rule can create conflicts with old one, it will be necessary to rename old existing references. This can be done by a SQL request. | If the new rule can create conflicts with old one, it will be necessary to rename old existing references. This can be done by a SQL request. | ||
For example, to go from numbering module Jupiter (FYYYYMM99) to Terre (FAYYMM-999), you can run the following request: | For example, to go from numbering module Jupiter (FYYYYMM99) to Terre (FAYYMM-999), you can run the following request: | ||
< | <syntaxHighlight lang="sql"> | ||
update llx_facture set facnumber=concat('FA',substr(facnumber,4,4),'-',substr(facnumber,8)) | update llx_facture set facnumber=concat('FA',substr(facnumber,4,4),'-',substr(facnumber,8)) | ||
where facnumber like 'F%' and facnumber not like 'FA%'; | where facnumber like 'F%' and facnumber not like 'FA%'; | ||
</ | </syntaxHighlight> | ||
For example, to rename references from model FAYYMM999 to Terre (FAYYMM-999), you can run the following request: | For example, to rename references from model FAYYMM999 to Terre (FAYYMM-999), you can run the following request: | ||
< | <syntaxHighlight lang="sql"> | ||
update llx_facture set facnumber=concat('FA',substr(facnumber,3,4),'-',substr(CONCAT('0000',substr(facnumber,7)),-4)) | update llx_facture set facnumber=concat('FA',substr(facnumber,3,4),'-',substr(CONCAT('0000',substr(facnumber,7)),-4)) | ||
where facnumber like 'FA%' and facnumber not like '%-%'; | where facnumber like 'FA%' and facnumber not like '%-%'; | ||
</ | </syntaxHighlight> | ||
=Submit a patch, work and help on Dolibarr development= | =Submit a patch, work and help on Dolibarr development= | ||