Developer FAQ - Revision history

Lvessiller: /* Submit a patch, work and help on Dolibarr development */

2025-02-14T11:11:30Z

Submit a patch, work and help on Dolibarr development

← Older revision		Revision as of 11:11, 14 February 2025
Line 69:		Line 69:

	*Because you probably don't have this role (your grade is [[Dolibarr_Project#Developers_roles\|Jedi]] or [[Dolibarr_Project#Developers_roles\|Admiral]] or [[Dolibarr_Project#Developers_roles\|Soldier]]), it is necessary to use the "Fork" feature of GitHub. Then you can make a "Pull Request" from GitHub to ask to have your patch merged into develop branch. More information on [[FAQ_Get,update_GIT_project_sources]] and https://github.com/Dolibarr/dolibarr/blob/develop/.github/CONTRIBUTING.md		*Because you probably don't have this role (your grade is [[Dolibarr_Project#Developers_roles\|Jedi]] or [[Dolibarr_Project#Developers_roles\|Admiral]] or [[Dolibarr_Project#Developers_roles\|Soldier]]), it is necessary to use the "Fork" feature of GitHub. Then you can make a "Pull Request" from GitHub to ask to have your patch merged into develop branch. More information on [[FAQ_Get,update_GIT_project_sources]] and https://github.com/Dolibarr/dolibarr/blob/develop/.github/CONTRIBUTING.md
	*How to decide which branch to merge ?

	=How to package and deploy a module=		=How to package and deploy a module=

Lvessiller at 11:06, 14 February 2025

2025-02-14T11:06:38Z

← Older revision		Revision as of 11:06, 14 February 2025
Line 52:		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">		<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~~>		</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">		<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~~>		</syntaxhighlight>

	=Submit a patch, work and help on Dolibarr development=		=Submit a patch, work and help on Dolibarr development=
Line 69:		Line 69:

	*Because you probably don't have this role (your grade is [[Dolibarr_Project#Developers_roles\|Jedi]] or [[Dolibarr_Project#Developers_roles\|Admiral]] or [[Dolibarr_Project#Developers_roles\|Soldier]]), it is necessary to use the "Fork" feature of GitHub. Then you can make a "Pull Request" from GitHub to ask to have your patch merged into develop branch. More information on [[FAQ_Get,update_GIT_project_sources]] and https://github.com/Dolibarr/dolibarr/blob/develop/.github/CONTRIBUTING.md		*Because you probably don't have this role (your grade is [[Dolibarr_Project#Developers_roles\|Jedi]] or [[Dolibarr_Project#Developers_roles\|Admiral]] or [[Dolibarr_Project#Developers_roles\|Soldier]]), it is necessary to use the "Fork" feature of GitHub. Then you can make a "Pull Request" from GitHub to ask to have your patch merged into develop branch. More information on [[FAQ_Get,update_GIT_project_sources]] and https://github.com/Dolibarr/dolibarr/blob/develop/.github/CONTRIBUTING.md
			*How to decide which branch to merge ?

	=How to package and deploy a module=		=How to package and deploy a module=

Sonikf: Undo revision 60362 by Nexgen (talk)

2024-05-14T22:15:39Z

Undo revision 60362 by Nexgen (talk)

← Older revision		Revision as of 22:15, 14 May 2024
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]].

	=~~Como ser um programador oficial~~=		=How to be an official developer=

	~~No projeto~~ Dolibarr, ~~que se situa numa galáxia própria, existem vários intervenientes com diferentes níveis~~/~~classificações~~. ~~O número de programadores é significativo, pelo que as contribuições e alterações têm de ser controladas e validadas~~ (~~tanto para necessidades funcionais como para codificação~~). ~~Por esse motivo~~, ~~o acesso de escrita ao código fonte~~ (GIT) ~~é limitado e gerido por uma organização descrita em seguida~~. ~~Cada programador possui uma classificação consoante~~ a ~~sua antiguidade e desempenho anterior~~. ~~O nível de autorização de uma pessoa no projeto aumenta à medida que progride na sua classificação~~.		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.

	~~A carreira de um programador~~ Dolibarr ~~segue estes passos~~, ~~classificados por um título~~ familiar ~~aos fãs de ficção científica~~. ~~Aqui estão as etapas~~. ~~É importante compreender que esta organização tem o único propósito de melhorar a qualidade do~~ Dolibarr ~~e a sua utilização rigorosa é necessária~~.		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.

	~~As classificações dos contribuidores para o projeto~~ Dolibarr, ~~e o que fazer para as alcançar~~, ~~estão definidas na página do~~ [[Dolibarr_Project#Developers_roles\|~~Projeto~~ Dolibarr]] ~~no capítulo "Funções dos Desenvolvedores"~~.		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">		<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~~>		</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">		<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~~>		</syntaxHighlight>

	=Submit a patch, work and help on Dolibarr development=		=Submit a patch, work and help on Dolibarr development=

Nexgen: /* Como ser um programador oficial */

2024-05-14T10:01:04Z

Como ser um programador oficial

← Older revision		Revision as of 10:01, 14 May 2024
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~~=		=Como ser um programador oficial=

	~~In the galaxy of the~~ Dolibarr ~~project~~, ~~there are several actors with different levels~~ / ~~grades~~.		No projeto Dolibarr, que se situa numa galáxia própria, existem vários intervenientes com diferentes níveis/classificações. O número de programadores é significativo, pelo que as contribuições e alterações têm de ser controladas e validadas (tanto para necessidades funcionais como para codificação). Por esse motivo, o acesso de escrita ao código fonte (GIT) é limitado e gerido por uma organização descrita em seguida. Cada programador possui uma classificação consoante a sua antiguidade e desempenho anterior. O nível de autorização de uma pessoa no projeto aumenta à medida que progride na sua classificação.
	~~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~~.		A carreira de um programador Dolibarr segue estes passos, classificados por um título familiar aos fãs de ficção científica. Aqui estão as etapas. É importante compreender que esta organização tem o único propósito de melhorar a qualidade do Dolibarr e a sua utilização rigorosa é necessária.
	~~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'''~~.		As classificações dos contribuidores para o projeto Dolibarr, e o que fazer para as alcançar, estão definidas na página do [[Dolibarr_Project#Developers_roles\|Projeto Dolibarr]] no capítulo "Funções dos Desenvolvedores".

	=Current team=		=Current team=
Line 52:		Line 48:
	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">		<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~~>		</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">		<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~~>		</syntaxhighlight>

	=Submit a patch, work and help on Dolibarr development=		=Submit a patch, work and help on Dolibarr development=

ShengGang: Add Chinese

2023-10-12T09:45:35Z

Add Chinese

← Older revision		Revision as of 09:45, 12 October 2023
Line 5:		Line 5:
	[[de:Entwickler_FAQ]]		[[de:Entwickler_FAQ]]
	[[es:FAQ_Desarrolladores]]		[[es:FAQ_Desarrolladores]]
			[[zh:开发者常见问题解答]]
	<!-- END interlang links -->		<!-- END interlang links -->

Hystepik: change deprecated source tag to syntaxHighlight

2022-03-15T12:58:03Z

change deprecated source tag to syntaxHighlight

← Older revision		Revision as of 12:58, 15 March 2022
Line 51:		Line 51:
	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:
	<~~source~~ lang="sql">		<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%';
	</~~source~~>		</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:
	<~~source~~ lang="sql">		<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 '%-%';
	</~~source~~>		</syntaxHighlight>

	=Submit a patch, work and help on Dolibarr development=		=Submit a patch, work and help on Dolibarr development=

Eldy: /* Submit a patch, work and help on Dolibarr development */

2021-09-16T00:47:31Z

Submit a patch, work and help on Dolibarr development

← Older revision		Revision as of 00:47, 16 September 2021
Line 65:		Line 65:
	If you want to know what you can do to start or help Dolibarr development, read instead chapter [[Developer_FAQ#How_to_be_an_official_developer]]. If you already read it and want to distribute a patch, this chapter is for you.		If you want to know what you can do to start or help Dolibarr development, read instead chapter [[Developer_FAQ#How_to_be_an_official_developer]]. If you already read it and want to distribute a patch, this chapter is for you.

	*If you have Yoda grade (See [[~~Developer FAQ~~#~~How to be an official developer~~]] for information on different grade), you have a direct GIT write access. So just use it to commit your changes.		*If you have Yoda grade (See [[Dolibarr_Project#Developers_roles]] for information on different grade), you have a direct GIT write access. So just use it to commit your changes.

	*Because you probably don't have this role (your grade is [[~~Developer FAQ~~#~~Soldier~~\|Jedi]] or [[~~Developer FAQ~~#~~Soldier~~\|Admiral]] or [[~~Developer FAQ~~#~~Soldier~~\|Soldier]]), it is necessary to use the "Fork" feature of GitHub. Then you can make a "Pull Request" from GitHub to ask to have your patch merged into develop branch. More information on [[FAQ_Get,update_GIT_project_sources]] and https://github.com/Dolibarr/dolibarr/blob/develop/.github/CONTRIBUTING.md		*Because you probably don't have this role (your grade is [[Dolibarr_Project#Developers_roles\|Jedi]] or [[Dolibarr_Project#Developers_roles\|Admiral]] or [[Dolibarr_Project#Developers_roles\|Soldier]]), it is necessary to use the "Fork" feature of GitHub. Then you can make a "Pull Request" from GitHub to ask to have your patch merged into develop branch. More information on [[FAQ_Get,update_GIT_project_sources]] and https://github.com/Dolibarr/dolibarr/blob/develop/.github/CONTRIBUTING.md

	=How to package and deploy a module=		=How to package and deploy a module=

Eldy: /* Start a development */

2020-05-15T07:20:20Z

Start a development

← Older revision		Revision as of 07:20, 15 May 2020
Line 28:		Line 28:
	=Start a development=		=Start a development=
	Read first '''completely''' the [[Developer documentation]] to know all rules a developer must respect.		Read first '''completely''' the [[Developer documentation]] to know all rules a developer must respect.
	You can also read following ~~FAQ~~.		You can also read the following FAQs.

	=Get/update project sources=		=Get/update project sources=

Jtraulle at 10:16, 11 March 2020

2020-03-11T10:16:34Z

← Older revision		Revision as of 10:16, 11 March 2020
Line 3:		Line 3:
	Links below will be automatically replicated on translated pages by PolyglotBot -->		Links below will be automatically replicated on translated pages by PolyglotBot -->
	[[fr:FAQ_Développeur]]		[[fr:FAQ_Développeur]]
			[[de:Entwickler_FAQ]]
	[[es:FAQ_Desarrolladores]]		[[es:FAQ_Desarrolladores]]
	<!-- END interlang links -->		<!-- END interlang links -->

Udo.tamm: add to category Development

2020-03-09T17:51:19Z

add to category Development

← Older revision		Revision as of 17:51, 9 March 2020
Line 10:		Line 10:
	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 =		=How to be an official developer=

	In the galaxy of the Dolibarr project, there are several actors with different levels / grades.		In the galaxy of the Dolibarr project, there are several actors with different levels / grades.
Line 22:		Line 22:
	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'''.		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=
	See page [[Dolibarr Project]] to know list of current people that work on Dolibarr, with their current grade.		See page [[Dolibarr Project]] to know list of current people that work on Dolibarr, with their current grade.

	= Start a development =		=Start a development=
	Read first '''completely''' the [[Developer documentation]] to know all rules a developer must respect.		Read first '''completely''' the [[Developer documentation]] to know all rules a developer must respect.
	You can also read following FAQ.		You can also read following FAQ.

	= Get/update project sources =		=Get/update project sources=
	See page [[FAQ Get,update project sources]].		See page [[FAQ Get,update project sources]].

	= How to create a new skin =		=How to create a new skin=
	For this, see page [[Skins]]		For this, see page [[Skins]]

	= How to develop my own module =		=How to develop my own module=
	To develop your own numbering module, see [[Create numeration module]].		To develop your own numbering module, see [[Create numeration module]].

Line 42:		Line 42:
	To develop your own business module (screens, tables), see page [[Module development]].		To develop your own business module (screens, tables), see page [[Module development]].

	= How to add/complete a translation =		=How to add/complete a translation=
	For this, see page [[Translator documentation]]		For this, see page [[Translator documentation]]

	= Change my numbering system after start =		=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 to menu Setup - Modules - Invoice setup and choose the new numbering rule in the list.		If the new numbering system does not conflict with the old one, to change the numbering rule, just go to menu Setup - Modules - Invoice setup and choose the new numbering rule in the list.

Line 61:		Line 61:
	</source>		</source>

	= Submit a patch, work and help on Dolibarr development =		=Submit a patch, work and help on Dolibarr development=
	If you want to know what you can do to start or help Dolibarr development, read instead chapter [[Developer_FAQ#How_to_be_an_official_developer]]. If you already read it and want to distribute a patch, this chapter is for you.		If you want to know what you can do to start or help Dolibarr development, read instead chapter [[Developer_FAQ#How_to_be_an_official_developer]]. If you already read it and want to distribute a patch, this chapter is for you.

	* If you have Yoda grade (See [[Developer FAQ#How to be an official developer]] for information on different grade), you have a direct GIT write access. So just use it to commit your changes.		*If you have Yoda grade (See [[Developer FAQ#How to be an official developer]] for information on different grade), you have a direct GIT write access. So just use it to commit your changes.

	* Because you probably don't have this role (your grade is [[Developer FAQ#Soldier\|Jedi]] or [[Developer FAQ#Soldier\|Admiral]] or [[Developer FAQ#Soldier\|Soldier]]), it is necessary to use the "Fork" feature of GitHub. Then you can make a "Pull Request" from GitHub to ask to have your patch merged into develop branch. More information on [[FAQ_Get,update_GIT_project_sources]] and https://github.com/Dolibarr/dolibarr/blob/develop/.github/CONTRIBUTING.md		*Because you probably don't have this role (your grade is [[Developer FAQ#Soldier\|Jedi]] or [[Developer FAQ#Soldier\|Admiral]] or [[Developer FAQ#Soldier\|Soldier]]), it is necessary to use the "Fork" feature of GitHub. Then you can make a "Pull Request" from GitHub to ask to have your patch merged into develop branch. More information on [[FAQ_Get,update_GIT_project_sources]] and https://github.com/Dolibarr/dolibarr/blob/develop/.github/CONTRIBUTING.md

	= How to package and deploy a module =		=How to package and deploy a module=
	See page [[Module development]].		See page [[Module development]].

	This process works also to generate a package to submit it on the https://www.dolistore.com market place.		This process works also to generate a package to submit it on the https://www.dolistore.com market place.

	= How to be informed on news and what happens on Dolibarr project ? =		=How to be informed on news and what happens on Dolibarr project ?=
	See page [[FAQ How to be informed on news about Dolibarr project ?]]		See page [[FAQ How to be informed on news about Dolibarr project ?]]

	= Migrate my Mysql database to PostgreSQL =		=Migrate my Mysql database to PostgreSQL=
	See page [[FAQ Migrate my Mysql database to PostgreSQL]]		See page [[FAQ Migrate my Mysql database to PostgreSQL]]

	= What and how is the release process =		=What and how is the release process=
	See page [[FAQ Release process]]		See page [[FAQ Release process]]
			[[Category:Development]]