Dolibarr ERP CRM Wiki - User contributions [en]

Dolibarr suppliers France

2019-06-26T13:06:16Z

Rdoursenaud: Suppression GPC.solutions qui a arrêté cette activité

{{Dolibarr_suppliers}}

{{TemplateCompany|
name=1fonet Services|
profid=|
desc=Integrations and open source development
Specialist software open source.Dolibarr, Joomla! Prestashop, Cahiers des charges ERP/CRM, Ecommerce, site web, gratuits. Complementary development of the module, component or application needs. Based in the PACA region work throughout France.|
web=http://www.1fonet.fr|
email=mailto:contact@1fonet.fr|
zip=13530|
town=Trets|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=2A2C Conseil|
profid=|
desc=CRM et Solutions e-commerce opensource pour TPM et PME, VoIP et Hosting en marque blanche, maintenance informatique, WordPress, Dolibarr, Prestashop, Formation utilisateur|
web=|
email=mailto:info@2a2c-conseil.fr|
zip=75012|
town=PARIS|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=A3SYS : MON-DOLIBARR|
profid=52456658500021 (SIRET)|
desc=Intégration, assistance et développement.
Notre société forte de plus de 20 ans d'expérience dans l'intégration de divers ERP propose ses services aux entreprises souhaitant mettre en place l'ERP Dolibarr. Une plateforme dédiée est mise en place pour proposer des services de qualité à moindre coût.|
web=http://www.mon-dolibarr.fr|
email=http://www.mon-dolibarr.fr/contact/|
zip=59310|
town=Orchies (Nord - France)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=logo_mon-dolibarr.jpg
}}

{{TemplateCompany|
name=A6TM - SOLUTIONS|
profid=|
desc=A6TM SOLUTIONS, est une entreprise maîtrisant les technologies de l'informatique, et spécialisée dans les solutions informatiques et notamment les services tels que l'infogérance, installations et déploiements, dépannages, maintenance et réseaux informatique. Installation et maintenance CMS(Joomla, Wordpress...), Progiciel ERP/CRM (Dolibarr...)|
web=http://www.a6tm-solutions.fr|
email=mailto:contact@a6tm-solutions.fr|
zip=44|
town=Nantes et son département|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ACN - Atelier de Création Numérique|
profid=808 725 212 00019|
desc=ACN (Atelier de Création Numérique), Maîtres d’œuvres en Informatique, Nous sommes spécialisés dans le conseil, la création et l’intégration de solutions professionnelles pour les bureaux d'études. Nos solutions vont de l’intégration d’outils Open Source et de logiciels libres à la mise en place des meilleurs produits de grands éditeurs du marché.|
web=http://ateliercreationnumerique.com/|
email=mailto:contact@atlcreanum.com|
zip=44|
town=Nantes et Grand Ouest|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=acn.png|
}}

{{TemplateCompany|
name=Aplose|
partner=yes|
profid=534906698|
desc=
Aplose c'est l'Agence pour la Promotion du Libre et de l'Open Source en Entreprise, société de service et organisme de formation spécialisé dans les logiciels libres de création de site internet et boutique en ligne (wordpress, prestashop), les erp, logiciels de gestion et logiciels de caisse et point de vente (Odoo, Dolibarr), les langages de programmation (java, html5, Javascript, php), les bases de données (mysql, postgresql), les systèmes d'exploitation (linux), les méthodes des gestion de projet agiles (Scrum). Bordeaux - Montpellier|
web=http://www.aplose.fr|
email=[mailto:oandrade@aplose.fr?subject=Contact%20from%20Dolibarr%20Suppliers%20France20page oandrade@aplose.fr]|
zip=33610|
town=Cestas|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=Logo_Aplose.png
}}

{{TemplateCompany|
name=Artaban Communication|
partner=no|
profid=400 396 388 00037|
desc=Artaban Communication est une SSLL. Spécialistes du CMS SPIP, nous concevons et réalisons des sites web à forte composante éditoriale. Nous prenons également en charge le webmastering et la création de contenu. Notre expertise s'étend à un certain nombre de logiciels, choisis pour leur qualité et leur intérêt, et avec lesquels nous aimons travailler et notamment Dolibarr. Artaban Communication est membre de l'April.|
web=http://www.artaban.fr|
email=mailto:contact@artaban.fr|
zip=94340|
town=Joinville-le-Pont|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Artaban_logo.png‎|
}}

{{TemplateCompany|
name=ATM Consulting|
partner=yes|
profid=753 447 481 00015|
desc=Consulting company dedicated to small and medium enterprises information system optimization, we provide to our customers open-source based solutions to improve their information system efficiency. We offer hosting and support solutions and we are Dolibarr contributor, developer and integrator. "Open-source. Custom. Freedom"|
web=http://www.atm-consulting.fr|
email=mailto:contact@atm-consulting.fr|
zip=26000|
town=Valence|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=AB2L|
profid=|
desc=Un Alsacien à votre service. Installation et configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur notre serveur. Nous vous accompagnons pour un démarrage rapide et serein. Nous sommes une société de service en logiciel libre fournissant un équivalent open source au logiciel propriétaire de tout type. |
web=http://www.ab2l.eu|
email=mailto:contact@ab2l.eu|
zip=67000|
town=Strasbourg|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Axopen IT Services|
profid=|
desc=L'entreprise Axopen propose toute une gamme de produits et services informatiques allant du conseil en système d'informations, développement de solutions sur mesure et intégration de solutions Open Source ou propriétaires. Nous sommes spécialisé en particulier dans l'intégration de solutions de gestion de la relation client Open Source telles que Dolibarr, SugarCRM ou VTiger... |
web=http://www.axopen.com|
email=mailto:contact@axopen.com|
zip=69001|
town=Lyon|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=AKILIS|
profid=|
desc=AKILIS est une société éditrice de logiciels de gestion qui a fait le pari d’utiliser les nouvelles méthodes de travail pour développer des solutions clairs et efficaces. Notre mission est de vous proposer des solutions simples d'utilisation, ne demandant aucun entretien de votre part, ni aucune connaissance technique particulière. Notre outil est celui que VOUS utilisez quotidiennement : le Web.
AKILIS, c’est une équipe toujours disponible pour vous guider et vous écouter. Nous développons et améliorons sans cesse nos logiciels afin que ceux-ci répondent au mieux à votre activité et vos besoins.
AKILIS peut également, dans le cadre de besoin partculier, étudier avec vous un développement sur mesure. |
web=http://www.akilis.fr|
email=mailto:contact@akilis.fr|
zip=69200|
town=Vénissieux|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Altairis|
profid=|
partner=yes|
desc=Développements spécifiques, Installation, Formation, Accompagnement à la mise en oeuvre, Support, Intégration.|
web=http://www.altairis.fr|
email=contact@altairis.fr|
zip=38570|
town=Goncelin|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Auguria Conseil|
partner=yes|
profid=|
desc=You are a Small Business, a very small firm, you need tools to increase profitability, and reliability facing competition. Auguria aims to help you develop the tools of information vectors of progress.|
web=http://www.auguria.net/|
email=contact@auguria.net|
zip=44300|
town=Nantes|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Atoo.Net|
partner=yes|
profid=|
desc=Installation et configuration de l'ERP/CRM Dolibarr soit sur nos serveurs, soit en local dans votre entreprise. Aide à la prise en main et formation.|
web=http://www.atoo-net.com/|
email=contact@atoo-net.com|
zip=45160|
town=Olivet|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Blue-Click Informatique|
profid=|
desc=Nous proposons l'installation et la configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur votre hébergement Internet. De plus nous assurons la formation pour la prise en main de cet outil adapté aux TPE et PME.|
web=http://www.blue-click.fr|
email=|
zip=92,78|
town=Nanterre,Plaisir|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=CAP-REL|
profid=|
desc=Après avoir contribué au code de dolibarr dans les années 2004-2005 et l'avoir utilisé en interne pour de nombreux projets depuis cette époque je propose maintenant un service autour de Dolibarr (adaptation, accompagnement, utilisation etc.).|
web=https://www.cap-rel.fr|
email=eric.doli@cap-rel.fr|
zip=30|
town=Département du Gard|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_cap-rel.png‎|
}}

{{TemplateCompany|
name=Caribbean Consult CCC|
partner=yes|
profid=|
desc=Installation, configuration de l'ERP/CRM Dolibarr en ligne, ou en local pour votre entreprise ou association. Migration de données vers Dolibarr. Prise en main, support et formation.|
web=https://dolibarr.ccc.gp|
email=support@caribbeanconsult.com|
zip=97180|
town=Sainte Anne (Guadeloupe et Martinique) Antilles Guyane|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_CCC.png‎|
}}

{{TemplateCompany|
name=Cergy Internet|
profid=|
desc=Cergy Internet est spécialisé dans l’informatique et plus spécifiquement dans l’internet pour les PMI/PME. Nous maitrisons les technologies digitales du simple site web jusqu’au portail complète de pilotage d’entreprise. Grâce à Dolibarr nous pouvons vous donner une vision unique sur vos clients, vos produits et même votre trésorerie. Nous lions Dolibarr avec Wordpress et sur Smartphones pour créer des portails pour vos clients. Notre directeur, Thomas Carter, a fait son MBA à MIT aux USA et a géré des entreprises de plus de 100 personnes. Il met cette expérience à votre disposition. Chez Cergy Internet nous maitrisons la technologie de boute en boute. Nous avons notre propre équipe de jeunes codeurs qui baignent dans tous qui est réseaux sociaux, applications iPhone etc. ainsi qu’une plateforme de 30 serveurs pour héberger vos sites. |
web=www.cergy-internet.fr|
email=mailto:thomas.carter@cergy-internet.fr|
zip=95300|
town=Cergy-Pontoise|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=D-BOG|
profid=|
desc=IT services company located in Beaune (21), moved around Dolibarr:
Installation, setup, configuration on the internal server or hosted;
Training agreement;
Outsourcing, on-site maintenance and remote.|
web=http://www.d-bog.com/|
email=|
zip=|
town=Beaune|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=DiVA-Cloud|
profid=|
desc=DiVA-Cloud propose des applications OpenSource de gestion de la communication et de l'information pour les entreprises. Notre logithèque contient des applications de WebConference, ERP, CRM, CMS, GED, et bien d'autres... Toutes ces applications pré-configurés sont mises à disposition sur un environnement privé. |
web=www.diva-cloud.com |
email=mailto:contact@diva-cloud.com |
zip=81100|
town=Castres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Elonet|
partner=yes|
profid=SIRET:52511620800022|
desc=Elonet a créé dolimail.fr , un outil qui permet de savoir quand, par qui, et quelles pages de vos fichiers PDF (devis, commande, facture) sont parcourus par vos prospects, clients ou fournisseur. Elonet est également intégrateur et développeur de solutions pour Dolibarr.|
web=https://elonet.fr|
email=mailto:contact@elonet.fr|
zip=59000|
town=LILLE|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Elonet.png
}}

{{TemplateCompany|
name=FUTUR TECH|
profid=|
desc=Prestataire de services pour artisans, TPE, PME :
Solutions open source, Internet, Sécurité, Sauvegarde, Antivirus, Gestion d'entreprise, Conseil, Formation, Installation et Paramétrage
Intervention sur site client. Situé entre Bordeaux et Libourne|
web=http://www.futur-tech.com|
email=mailto:info@futur-tech.com|
zip=33450|
town=IZON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Groupe KM|
profid=790 885 388 00013|
desc=Intégrateur,développeur et hébergeur de solutions Open Source: Progiciel ERP/CRM (Dolibarr),CMS(Joomla)et e-commerce(Prestashop). Nous déployons aussi des solutions Téléphonie (VOIP, PABX...) et Accés Internet (ADSL/VDSL, SDSL...). 
Secteur Cannes, Antibes, Sophia-Antipolis, Carros, Nice et plus généralement toutes les Alpes-Maritimes. 
Notre objectif : Vous satisfaire!|
web=https://www.groupe-km.com|
email=mailto:contact@groupe-km.com|
zip=06220|
town=Vallauris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=GWARED|
profid=804 659 027 00036|
desc=La société GWARED, est une équipe diplômée dans le domaine de l’informatique, de plus de 10 ans d’expériences dans diverses structures telles que de grandes administrations, sociétés privées mais aussi au service des particuliers. Nous sommes à l’écoute pour vous accompagner dans vos projets.

Professionnel ou particulier, nous vous proposons de nombreux services informatiques et domotiques adaptés à votre configuration et vos besoins. Nos prestations concernent la réparation et la maintenance de votre ordinateur ou de votre parc informatique, l'installation réseau (Local informatique, Internet, intranet, Wifi, CPL, etc.), l'installation d’alarmes et vidéo-surveillance, sur site, à distance ou à domicile.

Notre société se distingue en trois branches :

- L’informatique (GWARED)
- La sécurité (alarme, vidéosurveillance et protection numérique) (GWARDSECURITY)
- Les jeux vidéo (concepteur de console de jeux) (GWARDBOX)

Nous pourrons répondre à tous vos besoins dans le domaine de l’informatique.|
web=http://www.gwared.fr|
email=[mailto:support@gwared.fr?subject=Contact%20de%20Dolibarr%20Suppliers%20France support@gwared.fr]|
zip=77500|
town=Chelles et Île de France|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=Logo_Gwared.png|
}}

{{TemplateCompany|
name=HELIUM TECHNOLOGIES|
profid=494 895 360 00027|
partner=yes|
desc=
Mise en place de solutions ERP Dolibarr sur nos serveurs ou dans votre entreprise avec assistance téléphonique, support technique, développement de modules spécifiques et formation.
 '''SSII basée en Guadeloupe, Martinique et Guyane''', nous proposons également des solutions libres comme GLPI, Prestashop, Joomla, Odoo, Zimbra, BlueMind, Centreon, ...|
web=http://|
email=[mailto:contact@helium-technologies.com?subject=Contact%20from%20Dolibarr%20Suppliers%20France20page contact@helium-technologies.com]|
zip=97122|
town=BAIE-MAHAULT (GUADELOUPE)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_HeliumTechnologies.jpg
}}

{{TemplateCompany|
name=Infonel.net|
profid=|
desc=administrateur système open source indépendant:
Installation, paramétrage, configuration et sécurisation de dolibarr sur site client|
web=http://www.infonel.net|
email=|
zip=11100|
town=Narbonne|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=iNodbox|
partner=yes|
profid=|
desc=Développeur indépendant d'application web, paramétrage et installation de Dolibarr, développement de modules spécifique. Basé dans l'Ain à Bourg en Bresse (30min de Mâcon, 1h de Chalon sur Saône, 1h de Lyon), je contribue depuis de nombreuses années au développement de Dolibarr.|
web=https://www.inodbox.com/|
email=regis.houssin@inodbox.com|
zip=01000|
town=Bourg en Bresse|
country=fr|
service_hosting=(https://www.inodbox.com)|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Inovea Conseil|
partner=yes|
profid=797 613 072 00017|
desc=Développeur, Intégrateur, Hébergeur et Formateur de Dolibarr pour TPE - PME |
web=https://www.inovea-conseil.com/ |
email=https://www.inovea-conseil.com/contact/ |
zip=88,54,75|
town=Nancy|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Inoveaconseil.png
}}

{{TemplateCompany|
name=i.d & l|
profid=521 749 994 00013|
desc=Conseil et intégration de solutions logicielles libres, dont Dolibarr, pour artisans, TPE, indépendants, commerçants, PME, associations...|
web=http://idl-mp.com|
email=http://idl-mp.com/contact/|
zip=31,32,09,82,81|
town=Toulouse et région toulousaine|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=iouston informatique|
profid=792 263 683 00015|
desc=iouston informatique, située à proximité de Nancy, Metz, Lunéville, est une société spécialisée auprès des associations, des TPE et des artisans commerçants. Nous installons et configurons dolibarr pour vous et nous formons vos équipes à son utilisation quotidienne.
Nous proposons de nombreux autres services, associés ou non à dolibarr.|
web=http://www.iouston.com|
email=mailto:allo@iouston.com|
zip=54370|
town=Bauzemont|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ISYNUX|
profid=|
desc=Société de services en réseaux et sytèmes. ISYNUX vous propose un suivi complet pour DOLIBARR : installation, hébergement, personnalisation de vos modèles de document, formation à la carte. |
web=http://www.isynux.fr|
email=mailto:formation@isynux.fr|
zip=626100|
town=Ardres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Jeffinfo (ZenDSI)|
profid=429 625 973|
partner=yes|
desc=Jeffinfo est une société de services en informatique qui vous sert depuis plus de 15 ans dont 10 ans dans le domaine de Dolibarr. Implanté dans le nord à Ennetières en Weppes. Nous sommes à vos services pour vous proposer tous les services autour de votre ERP préféré.
web=https://shop.zendsi.com|
email=mailto:contact@zendsi.com|
zip=59320|
town=Ennetières en Weppes|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no
}}

{{TemplateCompany|
name=Kreiz IT|
partner=yes|
profid= 752 505 131 00017|
desc={{Flag_fr}}Conseils en organisation et sécurité informatique pour les TPE / PME. Dolibarr fait partie des outils informatiques structurants pour les TPE/PME proposé par Kreiz IT.

{{Flag_en}}IT management and security consultant for small to medium business. Dolibarr is part of IT's structuring tools for business used by Kreiz IT. |
web=http://www.kreiz-it.fr |
email=mailto:contact@kreiz-it.fr |
zip=56600|
town=Lanester|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=LogoKIT.jpg
}}

{{TemplateCompany|
name=LIBRE EXPERT|
partner=no|
profid=48879200300045|
desc={{Flag_fr}}Intégrateur et développeur Dolibarr, auteur de plusieurs modules complémentaires, spécialiste également de l'administration Linux.

{{Flag_en}}
Integrator and Dolibarr developer, author of several complementary modules, also specialist in Linux administration. |
web=http://www.libre-expert.com|
email=mailto:contact@libre-expert.com |
zip=63100|
town=Clermont-Ferrand|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Librethic|
partner=yes|
profid=83334801400014|
desc={{Flag_fr}}Librethic est une Société de Services en Informatique et Technologies Libres, tournée vers les entreprises et les associations. Créée en 2017, elle est portée par des professionnels aguerris aux technologies libres et open source.
L'environnement Dolibarr fait partie du cœur de compétences de Librethic (développement de modules complémentaires, hébergement SaaS, hébergement sur site, passerelle e-commerce).
{{Flag_en}}
Librethic is an IT Provider aiming at businesses and organizations, offering services in free/libre and open source software (FLOSS) and open design technologies.
Founded in 2017, Librethic is driven by libre and open source technologies seasoned professionals. Dolibarr's environment is one of Librethic's core skills (Addons and plugins development, SaaS hosting, on-premise hosting, e-commerce gateway).
web=https:/librethic.io/|
email=mailto:hello+dolibarr@librethic.io|
zip=34070|
town=Montpellier|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=logo-librethic.png
}}

{{TemplateCompany|
name=LVS Informatique|
profid=|
desc=Development Specialist php, mysql. Creation, enhancement, customization of modules and components ...
Nos modifs/nos modules :
-cashdesk : prix en ttc, possibilité de modification du prix, du libellé...
-interfaçage avec GoogleAgenda (toutes les actions apparaissent dans GoogleAgenda)
-Mails/Télécopies reçus : apparaissent dans un onglet spécifique sur le tiers en question
-qualification Tiers
-Adresse Tiers vu dans GoogleMap
-creation de nbreux template excel/pdf
|
web=http://www.lvsinformatique.com|
email=|
zip=83860|
town=NANS LES PINS|
country=fr|
service_dev=yes|
service_local=yes|
}}

{{TemplateCompany|
name=MEDIALTA|
profid=|
desc=Installation, configuration de Dolibarr sur nos serveurs, ou dans l'entreprise (Nancy, Metz, Lorraine, Grand Est). Formation, prise en main. Développement de modules sur mesure.|
web=www.medialta.com|
email=|
zip=54340|
town=Pompey|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Mephivio|
profid=|
desc=Services company with a computer located in Montpellier agglo, specializing in computer graphics, secretariat, Joomla web sites, client, opensource (Dolibarr, glpi, voip Elastix / Trixbox / PIAF etc ...)|
web=http://www.mephivio.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=MEZIANT|
profid=|
desc=MEZIANT propose aux PME, TPE, artisans, commerçants et associations de l'Ouest son expertise en informatique issue d'une expérience de plus de 15 ans en Audit de Système d'Informations, Site internet, Formation et Choix de logiciel de gestion (ERP) comme '''DOLIBARR''' dont elle peut assurer l’installation, la formation ou encore le développement de modules spécifiques sur site client.
web=http://www.meziant.fr |
email=mailto:contact@meziant.fr |
zip=22940|
town=PLAINTEL (Bretagne - France)|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Modulaweb : Technologies modulables orientées web.|
profid=|
desc=Développement d'applicatifs web, hébergement d'applications web, serveurs de fichiers et de sauvegarde, sites internet/intranet et intégration web, espaces clients, communication via internet (VoIP, messagerie instantanée), travail collaboratif. Spécialiste solutions libres pour l'entreprise (Zimbra, Dolibarr, Thaïs...) Région Languedoc-Rouissillon et voisines |
web=http://www.modulaweb.fr|
email=http://www.modulaweb.fr/portail/contact/|
zip=34000|
town=Montpellier|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Net Logic|
partner=yes|
profid=SIRET: 477 583 264 00023|
desc=Installation et configuration de l'ERP/CRM Dolibarr sur nos serveurs, ou en local dans votre entreprise. Paramétrage, personnalisation, reporting spécifique, assistance.|
web=http://www.netlogic.fr/|
email=info@netlogic.fr|
zip=93160|
town=Noisy-le-Grand|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=NLTechno|
partner=yes|
desc=NLTechno is one of the most important contributor on Dolibarr and can host for you a Dolibarr database in a SaaS (Software As A Service) mode.|
profid=493 861 496 00021|
web=http://www.nltechno.com|
email=|
zip=92500|
town=Boulogne Billancourt|
country=fr|
service_hosting=yes (https://www.dolicloud.com)|
service_onlinesupport=yes|
service_emailsupport=only for DoliCloud.com customers|
service_dev=no|
service_local=no|
service_formation=no|
logo=logo_nltechno.png}}

{{TemplateCompany|
name=NORD ERP CRM|
partner=no|
profid=83184221600010 (SIRET)|
desc=Intégration, assistance, formation et hébergement de solutions Dolibarr. Nous intervenons auprès des artisans, indépendants, TPE et associations dans le Nord Pas-de-Calais. Développement possible selon les spécificités métier. NORD ERP CRM accompagne également les commerçants pour leur système d'encaissement.|
web=https://www.nord-erp-crm.fr/|
email=mailto:contact@nord-erp-crm.fr|
zip=59100|
town=Roubaix|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=logonewcouleur.jpg|
}}

{{TemplateCompany|
name=OAS-SERVICES|
profid=829767904|
partner=no|
desc=
OAS-SERVICES est une société de service spécialisés dans la mise en place de logiciels libres sous forme de services cloud, notamment de Ma Gestion Cloud (Dolibarr, viger), la mise en place de site internet et boutique en lignes, le développement d'application et de modules en PHP (Dolibarr, Wordpress, Prestashop), mais aussi en Java (JEE, Webservices, JPA), la mise en place de systèmes d'exploitation (linux), la gestion de projet en agilité - Montpellier, Sète|
web=https://www.ma-gestion-cloud.fr|
email=[mailto:contact@oas-services.fr?subject=Contact%20from%20Dolibarr%20Suppliers%20France20page contact@oas-services.fr]|
zip=34200|
town=SETE|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
logo=logo-oas-services.png
}}

{{TemplateCompany|
name=OPEN-DSI|
partner=yes|
profid=SIRET:75130522800015|
desc=Depuis 2012, nous accompagnons les petites et moyennes structures (1 à 50 salariés) dans la mise en place de solutions basées sur les logiciels libres. Nous proposons Dolibarr pour tous les besoins de gestion.|
web=https://www.open-dsi.fr|
email=mailto:infos@open-dsi.fr|
zip=69,38,01,42|
town=LYON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=opendsi.png
}}

{{TemplateCompany|
name=OIS - Open IT Store|
profid=822 430 419 00017|
desc=OIS (Open IT Store), We provide opensource instances located in Europe or North America.|
web=https://openitstore.com/dolibarr|
email=mailto:contact@openitstore.com|
zip=|
town=|
country=|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=no|
service_formation=yes|
logo=|
}}

{{TemplateCompany|
name=Oscss Shop|
partner=yes|
profid=SIRET:810 421 339 00013|
desc=Développement de modules sur mesure, interconnexions et hébergements.|
web=http://oscss-shop.fr|
email=mailto:support@oscss-shop.fr|
zip=28,45,41,72,61,27,75,69,38,01,73,74|
town=LA LOUPE|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Pascal Sené|
profid=|
desc=Logiciels libres et photographie.|
web=http://www.pascalsene.com|
email=contact@pascalsene.com|
zip=22,29,35,56|
town=Lannion|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Patas-Monkey|
profid=|
desc=Conseil, formation, développement et modules|
web=http://www.patas-monkey.com|
email=r.deschamps@patas-monkey.com|
zip=69,42,38,01,83|
town=Lyon|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Patasmonkey.jpg
}}

{{TemplateCompany|
name=ProbeSys|
profid=|
desc=Créée en 2003 par des passionnés du logiciel libre, [http://probesys.com ProbeSys] est une entreprise coopérative à l'image du secteur des nouvelles technologies : dynamique, réactive et participative. |
web=http://www.probesys.com|
email=mailto:contact@probesys.com|
zip=38600|
town=Fontaine|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Pro IP|
profid=|
desc=Mise en place de solutions ERP comme Dolibarr sur nos serveurs ou dans votre entreprise, assistance et formation|
web=http://wwww.proip.fr|
email=mailto:contact@proip.fr|
zip=62129|
town=Clarques|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=PTMSoft SARL|
profid=520 618 646 00019|
desc=Société de services et de développement logiciel. Installation Dolibarr sur nos serveurs ou dans votre entreprise, assistance et configuration.|
web=http://www.ptmsoft.fr|
email=[mailto:contact@ptmsoft.fr?subject=Contact%20de%20la%20page%20Dolibarr%20Suppliers%20France contact@ptmsoft.fr]|
zip=68890|
town=Mulhouse, Colmar|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
logo=Logo PTMSoft.png
}}

{{TemplateCompany|
name=Syllene|
profid=|
desc=We install and configure the software Dolibarr to suit your needs and train your users. We can also provide hosting and maintenance of your application.|
web=http://www.syllene.net/|
email=|
zip=|
town=|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Teclib'|
profid=513893503|
partner=yes|
desc=
Teclib est une société de services en informatique au capital de 400 000€. Implantés à Paris, Colmar (Alsace), Caen, Chartres (Région Centre) et Bordeaux (Aquitaine). L'équipe Teclib' rassemble une quarantaine de personnes spécialisées dans l'intégration, hébergement et développements de logiciels libres tels que Dolibarr, Odoo, GLPI, Zimbra, BlueMind, Nagios, Centreon, ... |
web=http://www.teclib.com|
email=[mailto:contact@teclib.com?subject=Contact%20from%20Dolibarr%20Preferred%20Partners%20page contact@teclib.com]|
zip=75001|
town=Paris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_Teclib.png
}}

{{TemplateCompany|
name=Tiaris|
partner=yes|
profid=|
desc=Solutions and services for small businesses and merchants: e-commerce, maintenance, ERP/CRM Dolibarr, development telecommuting. ecommerce - dolibarr webservice based interface. Saas Offer Dolibarr + ecommerce connection for open source caddies (OsCommerce, Zencart, Crelaoded, Prestashop and others...)|
web=http://www.tiaris.fr/|
email=http://www.tiaris.fr/spip.php?page=contact|
zip=57870|
town=WALSCHEID|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=UTOPSYS - L'Informatique, Professionnelle.|
profid=|
desc=Maintenance, dépannage, conseil, audits, Green IT, solutions open-source de travail collaboratif, installation et maintenance Dolibarr. Bordeaux, CUB, Libourne.|
web=http://www.utopsys.fr|
email=|
zip=|
town=Libourne|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=YON - Your Own Net|
profid=822 430 419 00017|
desc=YON (Your Own Net), Fournisseur de solution numérique, Nous sommes spécialisés dans la fourniture de solutions informatiques pour les professionnelles et les particuliers. Nos solutions vont de l’intégration d’outils Open Source et de logiciels libres à l'hébergement de logiciels.|
web=http://yourownnet.net/|
email=mailto:contact@yourownnet.net|
zip=79|
town=Niort et Grand Ouest|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
logo=|
}}

{{TemplateCompany|
name=WEBINFOPRO|
profid=|
desc=Society Computers and Internet service for small businesses located in the suburbs west of Paris. One of the main activities is the integration of open source software.|
web=http://www.webinfopro.fr/|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Z-Application|
profid=|
desc=Développement personnalisé et assistance à la installation-migration. Support sur site possible dans le département Manche (50).|
web=https://www.z-application.com/|
email=|
zip=50250|
town=Coutances - Cherbourg - Saint-Lô|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

ReleaseProcess

2016-10-19T14:20:58Z

Rdoursenaud: Add nice to have releases

= Dolibarr release process =

This document is a '''draft'''.

The intention is to document what needs to be done to release Dolibarr.

RD: ''I intend to use it as a base to revamp the whole releasing process.''

== Officialy maintained ==

=== Descriptor ===

* [http://pad.asp-software.org Portable Application Description]

=== Archives ===

* Gziped tar archive

''Actually uses the .tgz extension, I'd prefer the more common .tar.gz''

''SO: In my opinion it would be even better if we could use .tar.xz''

* Zipped archive

RD: ''I'd build it from the tarball''

=== Distribution packages ===

RD: ''I'd make these from the release tarball.''

==== RPM ====

RD: ''Can't all of these be unified?''

LD: ''This is what Generic below is for but specific versions are needed for distro integration''

RD: ''I think that Debian integration is ongoing, what about other distros?''

''Isn't this the distribution package maintainer responsibility, not the release managers?''

* Generic
* Fedora

RD: ''RedHat?''

* Mandriva

RD: ''Is this really needed? I mean who still uses mandriva these days?''

* OpenSuse

==== DEB ====

* Debian

RD: ''Ubuntu?''

=== Installers ===

* Windows (DoliWamp, exe)

RD: ''This one is the most involved. We need a better spec of the process.''

== '''Not''' officially maintained ==

RD: ''Need volunteers?''

These packages are not officially maintained but are in the source tree. Maybe we'd want to have them work one day or another.

* [http://www.apsstandard.org APS]
* MacOS X installer (DoliMamp, dmg)
* [https://github.com/edumbill/doap/wiki DOAP]

RD: ''Is this even a package format?''

* Doxygen (Developer documentation)

RD: ''Again, not a package format, but this should certainly be published somewhere for each released version''

* Launchpad (https://launchpad.net/dolibarr)

RD: ''Ubuntu packages and build system?''

* Live CD

RD: ''Really? What for? Demos? Looks overkill''

* [https://build.opensuse.org/project/show/Application:ERP:Dolibarr OpenSuse build system]

RD: ''This one is pretty cool. Looks like we could leverage its capabilities to automate the builds of our Linux distribution packages.'' ''Credentials needed''

* Virtualmin installer
* Proxmox Appliance

== Nice to have ==

RD: ''Releases that don't exist just yet but would help reaching farther IMHO''

* GitHub releases

* Packagist.org (Compser)

== Tentative process ==

=== Early announcement ===

# Post to dolibarr-dev intention to package. Ask testers to test. Ask translators to update their translations. Fix release date allowing at least ''one'' week for people to do their tasks.

=== Building ===

# Update version numbers in source code, ChangeLog and PAD files
# Commit and Tag version

RD: ''Better be a [http://git-scm.com/book/en/Git-Basics-Tagging#Signed-Tags signed tag]''

<ol start="3" style="list-style-type: decimal;">
<li>Checkout tag to a test directory</li>
<li>Play unit tests</li>
<li>Play UI tests</li></ol>

If all is OK

<ol start="6" style="list-style-type: decimal;">
<li>Checkout tag to a build directory</li>
<li>Clean build directory (i.e. remove stuff that won't go into release. Includes devolopment tools, samples, test results, git repo itself, etc.)</li>
<li>Fix rights</li>
<li>TAR reference release</li></ol>

RD: ''We should also generate checksums''

RD: ''Add a GPG signature?''

<ol start="10" style="list-style-type: decimal;">
<li>ZIP release</li>
<li>RPM releases</li>
<li>DEB realease</li>
<li>Windows installer release</li></ol>

=== Testing ===

* ?

=== Pushing ===

# Tag to central repository

RD: ''Credentials needed. This won't get along with a pull request!''

<ol start="2" style="list-style-type: decimal;">
<li>Packages, Artifacts (Checksum(s), signature(s)…), ChangeLog and PAD files to dolibarr.org (/home/dolibarr/wwwroot/files)</li></ol>

RD: ''Credentials needed''

<ol start="3" style="list-style-type: decimal;">
<li>Packages to [http://sourceforge.net/projects/dolibarr/ Sourceforge.net]</li></ol>

RD: ''Credentials needed''

RD: ''Can be automated: [https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download doc]''

=== Verifiing ===

* ?

RD: ''This is where checksums comes in handy''

=== Releasing ===

# Craft announcement message

RD: ''The message template should be in the repo''

<ol start="2" style="list-style-type: decimal;">
<li>Post announcement as a news on dolibarr.org</li></ol>

RD: ''Credentials needed''

<ol start="2" style="list-style-type: decimal;">
<li>Send announcement on Social Networks</li></ol>

* [https://plus.google.com/+DolibarrOrg Google+]
* [http://www.twitter.com/dolibarr Twitter]
* [http://www.facebook.com/dolibarr Facebook]

RD: ''Credentials needed''

RD: ''Should all be automated through their respective APIs''

<ol start="3" style="list-style-type: decimal;">
<li>Send announcement on Mailing lists</li></ol>

dolibarr-user, dolibarr-dev, dolibarr-foundation

<ol start="4" style="list-style-type: decimal;">
<li>Send announcement on Forum</li></ol>

RD: ''This should be a sticky in the appropriate category (which?)''

RD: ''Credentials needed''

<ol start="5" style="list-style-type: decimal;">
<li>Create version on this wiki</li></ol>

RD: ''Credentials needed''

<ol start="5" style="list-style-type: decimal;">
<li>Create version in [http://doliforge.org Doliforge]</li></ol>

RD: ''Credentials needed''

== Misc. Questions ==

===RD===
* More projects are moving to tar.xz releases, shan't we join the boat?
* Shouldn't we use native environments to build distribution packages and windows installer? Vagrant maintained virtual build and test machines would be neet.
LD: More then 80% of users prefer to use installer, and 60% of dowload are for wamp installer, so we must keep native distribution packages.
* [https://aur.archlinux.org/packages/dolibarr Arch Linux package] could be adopted and made up to par with other distro's
* Shouldn't we publish also on GitHub since it's one of our homes now? This can be fully automated with the [http://developer.github.com/v3/repos/releases/ API]
* Is there other announcements to be made?
* Release script is in Perl now, I'd like to rewrite it with [http://www.phing.info Phing]. Any objections ?
LD: No, it would be better to have only php tools.

== Misc. Notes ==

* Directory structure for resulting binaries should be:
<pre>.
├── generic
├── package_aps
├── package_debian-ubuntu
├── package_mac
├── package_rpm_generic
├── package_rpm_mandriva
├── package_rpm_opensuse
├── package_rpm_redhat-fedora
└── package_windows
</pre>
* We need to define the versionning and naming conventions as well as the branching system

Modules - Packaging rules and Dolistore validation rules

2016-10-03T10:49:47Z

Rdoursenaud: Update template URL

= [[File:Art.png]] Enabling/activation condition of external module on DoliStore =
Here are the rules that will be apply by Dolibarr team on validation/activation of external module on [www.dolistore.com www.dolistore.com]

=== Structure ===
All module files have to be inside module directory, check this template [https://github.com/Dolibarr/dolibarr-module-template GitHub Dolibarr Module Template]

=== Inclusion ===
* To include a core file, use
<source lang="php">
include_once/require_once/include/require DOL_DOCUMENT_ROOT.'/pathtofile';
</source>

* To include a file of module into a file of same module, use
<source lang="php">
include_once/require_once/include/require './mymoduledir/...';
</source>

* To include a file of another external module into a module file, use
<source lang="php">
dol_include_once('/otherextmoduledir/...');
</source>

=== Link ===
All link to a page of a standard dolibarr object (an invoice, an order, a bank account, ...) should be included into your module page using the '''getNomUrl''' method of the class of the object.

=== Custom directory management ===
An external module called '''mymodule''' can be installed into '''htdocs/custom/mymodule''' as well as in '''htdocs/mymodule'''. It must works in both cases

=== Core file modifications ===
Your module MUST NOT change or overwrite any files provided by standard Dolibarr distribution. If some Dolibarr core files need to me modified to have your module working, you must submit this change to core team. They will be accepted :
* If they are pushed to dolibarr '''develop''' branch on GitHub
* If what you push is adding hooks or triggers, or optionnal parameter to existing functions, it should be accepted with no condition. For other change, it may depends if change keeps old code compatible and is interesting for everybody.

=== Support ===
If your module is not free you have to give a email adress for support (or a website that allow customers to contact you)

Product description is mandatory in English, French, Spanish (and support email as well)

Developer FAQ

2016-06-21T13:03:52Z

Rdoursenaud: New CONTRIBUTING.md path

[[Category:FAQ EN]]
{{TemplateDocDevEn}}
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. So do not be offended if, as a developer, you can not have a GIT write access for some time.

The ranks of contributors to the Dolibarr project are:

'''* Soldier'''

The first thing that a person willing to help needs to be familiar with the rules and standards developments.
By reading the [[Developer documentation]], you have shown sufficient willingness to automatically become '''Soldier''' (grade level '''Soldier'''). Most people that are interested in Dolibarr development are in this category.

This grade is obtained without higher validation. It is a grade of principle, to start.

The next step is to submit your first patch, starting with simple ones, on the dev Mailing List (see chapter [[Developer FAQ#Submit a patch, work and help on Dolibarr development|Submit a patch, work and help on Dolibarr development]] for the procedure) or on the forum (Preferred Mailing List).

You can find easy to do patches (easy hacks) on the TODO tracker:
{{TemplateURLTasks}}

Easy to start tasks have the property "Task opened to external developers" set to "yes". If the value is "no", forget it, this means the task will be processed by a Jedi-grade developer.

The number of soldiers is not limited. The more we are, the stronger we will be.
The soldiers are the main force of the Dolibarr alliance.

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).

'''* Z-6PO'''

If you are fluent in a language not present or poorly translated into Dolibarr, and know how to use GIT, you can use GIT to fork project locally and use push system tp publish your changes/adds.
If you don't know, send your changes done on last version of language files on '''dolibarr-dev''' mailing-list (Subscribe from page {{TemplateURLMLDev}}). However, first solution using GIT push is preferred.

The Dolibarr core team may add you, after several push, as official Z-6PO on page [[:Category:Z-6PO]].

'''* Admiral'''

Only after you've held the rank of Soldier for a variable time (which can be very long), you've submitted many patches of suitable quality, 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 requested. It is obtained by a decision or proposal of a '''Jedi''' or '''Yoda''' who believes that you have submitted enough 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 '''Soldier''').
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 '''Soldier'''.

Obtaining the rank of Admiral is as rare as limited. Dolibarr quality can not be achieved without a limited number of Admirals, but this is still compatible with having a very high number of developers ('''Soldiers'''), contributing through patches.

A list of Dolibarr contributors with this grade is available on page [[:Category:Admiral]]

'''* Jedi'''

Only after holding the rank of Adminral for a variable time (probably the longest of all), and the quality of GIT bug fixes or patches sent is satisfactory, a Yoda will tell you that you are authorized to perform commits without restrictions, including new features. 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.

This title can't be asked, it is obtained by a proposal of another Jedi or by a Yoda.

This privilege is exceptional. Dolibarr quality can not be achieved
without a limited number of '''Jedi''', but this is not compatible with a high number developers ('''Soldiers''') contributing with patches.

A list of Dolibarr contributors with this grade is available on page [[:Category:Jedi]]

'''* Yoda'''

There are about 1 to 5 '''Yoda'''. It's the overall management of project development. This ranking is obtained by inheritance or vote. 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 are some 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 Darth Vader per year ...

= Current team =
See page [[Dolibarr Project]] to know list of current people that work on Dolibarr, with their current grade.

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

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

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

= How to develop my own menu system =
For this, see page [[Menus system]]

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

To develop your own document model, PDF or other, see [[Create a PDF document template]] or [[Create an ODT document template]].

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

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

= 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 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:
<source lang="sql">
update llx_facture set facnumber=concat('FA',substr(facnumber,4,4),'-',substr(facnumber,8))
where facnumber like 'F%' and facnumber not like 'FA%';
</source>

For example, to rename references from model FAYYMM999 to Terre (FAYYMM-999), you can 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))
where facnumber like 'FA%' and facnumber not like '%-%';
</source>

= 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 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 page: https://github.com/Dolibarr/dolibarr/blob/develop/.github/CONTRIBUTING.md

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

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

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

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

Dolibarr suppliers France

2016-04-06T13:03:46Z

Rdoursenaud: Removed on-site services for GPC.solutions

{{Dolibarr_suppliers}}

{{TemplateCompany|
name=Pro IP|
profid=|
desc=Mise en place de solutions ERP comme Dolibarr sur nos serveurs ou dans votre entreprise, assistance et formation|
web=http://wwww.proip.fr|
email=mailto:contact@proip.fr|
zip=62129|
town=Clarques|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=1fonet Services|
profid=|
desc=Integrations and open source development
Specialist software open source.Dolibarr, Joomla! Prestashop, Cahiers des charges ERP/CRM, Ecommerce, site web, gratuits. Complementary development of the module, component or application needs. Based in the PACA region work throughout France.|
web=http://www.1fonet.fr|
email=mailto:contact@1fonet.fr|
zip=13530|
town=Trets|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=2A2C Conseil|
profid=|
desc=CRM et Solutions e-commerce opensource pour TPM et PME, VoIP et Hosting en marque blanche, maintenance informatique, WordPress, Dolibarr, Prestashop, Formation utilisateur|
web=|
email=mailto:info@2a2c-conseil.fr|
zip=75012|
town=PARIS|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=A3SYS : MON-DOLIBARR|
profid=52456658500021 (SIRET)|
desc=Intégration, assistance et développement.
Notre société forte de plus de 20 ans d'expérience dans l'intégration de divers ERP propose ses services aux entreprises souhaitant mettre en place l'ERP Dolibarr. Une plateforme dédiée est mise en place pour proposer des services de qualité à moindre coût.|
web=http://www.mon-dolibarr.fr|
email=http://www.mon-dolibarr.fr/contact/|
zip=59310|
town=Orchies (Nord - France)|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=A6TM - SOLUTIONS|
profid=|
desc=A6TM SOLUTIONS, est une entreprise maîtrisant les technologies de l'informatique, et spécialisée dans les solutions informatiques et notamment les services tels que l'infogérance, installations et déploiements, dépannages, maintenance et réseaux informatique. Installation et maintenance CMS(Joomla, Wordpress...), Progiciel ERP/CRM (Dolibarr...)|
web=http://www.a6tm-solutions.fr|
email=mailto:contact@a6tm-solutions.fr|
zip=44|
town=Nantes et son département|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ACN - Atelier de Création Numérique|
profid=808 725 212 00019|
desc=ACN (Atelier de Création Numérique), Maîtres d’œuvres en Informatique, Nous sommes spécialisés dans le conseil, la création et l’intégration de solutions professionnelles pour les bureaux d'études. Nos solutions vont de l’intégration d’outils Open Source et de logiciels libres à la mise en place des meilleurs produits de grands éditeurs du marché.|
web=http://ateliercreationnumerique.com/|
email=mailto:contact@atlcreanum.com|
zip=44|
town=Nantes et Grand Ouest|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=acn.png|
}}

{{TemplateCompany|
name=Artaban Communication|
partner=no|
profid=400 396 388 00037|
desc=Artaban Communication est une SSLL. Spécialistes du CMS SPIP, nous concevons et réalisons des sites web à forte composante éditoriale. Nous prenons également en charge le webmastering et la création de contenu. Notre expertise s'étend à un certain nombre de logiciels, choisis pour leur qualité et leur intérêt, et avec lesquels nous aimons travailler et notamment Dolibarr. Artaban Communication est membre de l'April.|
web=http://www.artaban.fr|
email=mailto:contact@artaban.fr|
zip=94340|
town=Joinville-le-Pont|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Artaban_logo.png‎|
}}

{{TemplateCompany|
name=ATM Consulting|
partner=yes|
profid=753 447 481 00015|
desc=Consulting company dedicated to small and medium enterprises information system optimization, we provide to our customers open-source based solutions to improve their information system efficiency. We offer hosting and support solutions and we are Dolibarr contributor, developer and integrator. "Open-source. Custom. Freedom"|
web=http://www.atm-consulting.fr|
email=mailto:contact@atm-consulting.fr|
zip=26000|
town=Valence|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=
}}

{{TemplateCompany|
name=AB2L|
profid=|
desc=Un Alsacien à votre service. Installation et configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur notre serveur. Nous vous accompagnons pour un démarrage rapide et serein. Nous sommes une société de service en logiciel libre fournissant un équivalent open source au logiciel propriétaire de tout type. |
web=http://www.ab2l.eu|
email=mailto:contact@ab2l.eu|
zip=67000|
town=Strasbourg|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Axopen IT Services|
profid=|
desc=L'entreprise Axopen propose toute une gamme de produits et services informatiques allant du conseil en système d'informations, développement de solutions sur mesure et intégration de solutions Open Source ou propriétaires. Nous sommes spécialisé en particulier dans l'intégration de solutions de gestion de la relation client Open Source telles que Dolibarr, SugarCRM ou VTiger... |
web=http://www.axopen.com|
email=mailto:contact@axopen.com|
zip=69001|
town=Lyon|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=AKILIS|
profid=|
desc=AKILIS est une société éditrice de logiciels de gestion qui a fait le pari d’utiliser les nouvelles méthodes de travail pour développer des solutions clairs et efficaces. Notre mission est de vous proposer des solutions simples d'utilisation, ne demandant aucun entretien de votre part, ni aucune connaissance technique particulière. Notre outil est celui que VOUS utilisez quotidiennement : le Web.
AKILIS, c’est une équipe toujours disponible pour vous guider et vous écouter. Nous développons et améliorons sans cesse nos logiciels afin que ceux-ci répondent au mieux à votre activité et vos besoins.
AKILIS peut également, dans le cadre de besoin partculier, étudier avec vous un développement sur mesure. |
web=http://www.akilis.fr|
email=mailto:contact@akilis.fr|
zip=69200|
town=Vénissieux|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Altairis|
profid=|
partner=yes|
desc=Développements spécifiques, Installation, Formation, Accompagnement à la mise en oeuvre, Support, Intégration.|
web=http://www.altairis.fr|
email=contact@altairis.fr|
zip=38570|
town=Goncelin|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Auguria Conseil|
partner=yes|
profid=|
desc=You are a Small Business, a very small firm, you need tools to increase profitability, and reliability facing competition. Auguria aims to help you develop the tools of information vectors of progress.|
web=http://www.auguria.net/|
email=contact@auguria.net|
zip=44300|
town=Nantes|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Atoo.Net|
partner=yes|
profid=|
desc=Installation et configuration de l'ERP/CRM Dolibarr soit sur nos serveurs, soit en local dans votre entreprise. Aide à la prise en main et formation.|
web=http://www.atoo-net.com/|
email=contact@atoo-net.com|
zip=45160|
town=Olivet|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Blue-Click Informatique|
profid=|
desc=Nous proposons l'installation et la configuration de l'ERP/CRM Dolibarr dans votre entreprise ou sur votre hébergement Internet. De plus nous assurons la formation pour la prise en main de cet outil adapté aux TPE et PME.|
web=http://www.blue-click.fr|
email=|
zip=92,78|
town=Nanterre,Plaisir|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Cap-Networks|
partner=yes|
profid=|
desc=Développeur indépendant d'application web, paramétrage et installation de Dolibarr, développement de modules spécifique. Basé dans la Saône et loire à Tournus (40min de Bourg en Bresse, 20min de Mâcon, 30min de Chalon sur Saône, 1h de Lyon), je contribue depuis de nombreuses années au développement de Dolibarr.|
web=http://www.inodbox.com/|
email=regis.houssin@cap-networks.com|
zip=71700|
town=Tournus|
country=fr|
service_hosting=(http://www.inodbox.com)|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=D-BOG|
profid=|
desc=IT services company located in Beaune (21), moved around Dolibarr:
Installation, setup, configuration on the internal server or hosted;
Training agreement;
Outsourcing, on-site maintenance and remote.|
web=http://www.d-bog.com/|
email=|
zip=|
town=Beaune|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=DiVA-Cloud|
profid=|
desc=DiVA-Cloud propose des applications OpenSource de gestion de la communication et de l'information pour les entreprises. Notre logithèque contient des applications de WebConference, ERP, CRM, CMS, GED, et bien d'autres... Toutes ces applications pré-configurés sont mises à disposition sur un environnement privé. |
web=www.diva-cloud.com |
email=mailto:contact@diva-cloud.com |
zip=81100|
town=Castres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=FUTUR TECH|
profid=|
desc=Prestataire de services pour artisans, TPE, PME :
Solutions open source, Internet, Sécurité, Sauvegarde, Antivirus, Gestion d'entreprise, Conseil, Formation, Installation et Paramétrage
Intervention sur site client. Situé entre Bordeaux et Libourne|
web=http://www.futur-tech.com|
email=mailto:info@futur-tech.com|
zip=33450|
town=IZON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=GPC.solutions|
partner=yes|
profid=RCS de Pau 528 995 921|
desc={{Flag_fr}}Spécialiste Open Source et Logicel Libre et revendeur Agréé PME Google Apps for Business.

Nous proposons un gamme complète de services autour de Dolibarr parmi lesquels l'hébergement cloud, le développement sur mesure, l'assistance et la formation.

Nous travaillons aussi à une intégration forte dans l'écosystème Google Apps.

{{Flag_en}}Open Source and Libre Software specialist and Authorized Google Apps for Business™ SMB reseller.

We offer a full range of services around Dolibarr including cloud hosting, custom development, support and training.

We're also working on a tight integration into the Google Apps ecosystem.|
web=http://gpcsolutions.fr|
email=mailto:contact@gpcsolutions.fr|
zip=64000|
town=Pau|
country=fr|
service_hosting=http://gpcsolutions.fr/dolibarr|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=no|
service_formation=yes|
logo=gpcsolutions.png|
}}

{{TemplateCompany|
name=Infonel.net|
profid=|
desc=administrateur système open source indépendant:
Installation, paramétrage, configuration et sécurisation de dolibarr sur site client|
web=http://www.infonel.net|
email=|
zip=11100|
town=Narbonne|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=i.d & l|
profid=521 749 994 00013|
desc=Conseil et intégration de solutions logicielles libres, dont Dolibarr, pour artisans, TPE, indépendants, commerçants, PME, associations...|
web=http://idl-mp.com|
email=http://idl-mp.com/contact/|
zip=31,32,09,82,81|
town=Toulouse et région toulousaine|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=iouston informatique|
profid=792 263 683 00015|
desc=iouston informatique, située à proximité de Nancy, Metz, Lunéville, est une société spécialisée auprès des assoiations, des TPE et des artisans commerçants. Nous installons et configurons dolibarr pour vous et nous formons vos équipes à son utilisation quotidienne.
Nous proposons de nombreux autres services, associés ou non à dolibarr.|
web=http://www.iouston.com|
email=mailto:allo@iouston.com|
zip=54370|
town=Bauzemont|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=ISYNUX|
profid=|
desc=Société de services en réseaux et sytèmes. ISYNUX vous propose un suivi complet pour DOLIBARR : installation, hébergement, personnalisation de vos modèles de document, formation à la carte. |
web=http://www.isynux.fr|
email=mailto:formation@isynux.fr|
zip=626100|
town=Ardres|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Koncept Management|
profid=790 885 388 00013|
desc=Société de conseil, intégration, développement de solutions pour Artisan, entrepreneur, commerçant et TPE.
Nous intervenons sur CMS(Joomla, Wordpress...), Progiciel ERP/CRM (Dolibarr...), Téléphonie (VOIP, PABX...), Accés Internet (ADSL/VDSL, SDSL...),Site Internet et Hébergement.
Nous rayonnons sur Cannes, Antibes, Sophia-Antipolis, Carros, Nice et plus généralement toutes les Alpes-Maritimes.
Notre objectif : Vous satisfaire!|
web=http://www.koncept-management.com|
email=mailto:contact@koncept-management.com|
zip=06220|
town=Vallauris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Kreiz IT|
partner=yes|
profid= 752 505 131 00017|
desc={{Flag_fr}}Conseils en organisation et sécurité informatique pour les TPE / PME. Dolibarr fait partie des outils informatiques structurants pour les TPE/PME proposé par Kreiz IT.

{{Flag_en}}IT management and security consultant for small to medium business. Dolibarr is part of IT's structuring tools for business used by Kreiz IT. |
web=http://www.kreiz-it.fr |
email=mailto:contact@kreiz-it.fr |
zip=56600|
town=Lanester|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=LogoKIT.jpg
}}

{{TemplateCompany|
name=LVS Informatique|
profid=|
desc=Development Specialist php, mysql. Creation, enhancement, customization of modules and components ...
Nos modifs/nos modules :
-cashdesk : prix en ttc, possibilité de modification du prix, du libellé...
-interfaçage avec GoogleAgenda (toutes les actions apparaissent dans GoogleAgenda)
-Mails/Télécopies reçus : apparaissent dans un onglet spécifique sur le tiers en question
-qualification Tiers
-Adresse Tiers vu dans GoogleMap
-creation de nbreux template excel/pdf
|
web=http://www.lvsinformatique.com|
email=|
zip=83860|
town=NANS LES PINS|
country=fr|
service_dev=yes|
service_local=yes|
}}

{{TemplateCompany|
name=MEDIALTA|
profid=|
desc=Installation, configuration de Dolibarr sur nos serveurs, ou dans l'entreprise (Nancy, Metz, Lorraine, Grand Est). Formation, prise en main. Développement de modules sur mesure.|
web=www.medialta.com|
email=|
zip=54340|
town=Pompey|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Mephivio|
profid=|
desc=Services company with a computer located in Montpellier agglo, specializing in computer graphics, secretariat, Joomla web sites, client, opensource (Dolibarr, glpi, voip Elastix / Trixbox / PIAF etc ...)|
web=http://www.mephivio.fr/|
email=|
zip=|
town=|
country=fr|
}}

{{TemplateCompany|
name=MEZIANT|
profid=|
desc=MEZIANT propose aux PME, TPE, artisans, commerçants et associations de l'Ouest son expertise en informatique issue d'une expérience de plus de 15 ans en Audit de Système d'Informations, Site internet, Formation et Choix de logiciel de gestion (ERP) comme '''DOLIBARR''' dont elle peut assurer l’installation, la formation ou encore le développement de modules spécifiques sur site client.
web=http://www.meziant.fr |
email=mailto:contact@meziant.fr |
zip=22940|
town=PLAINTEL (Bretagne - France)|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Modulaweb : Technologies modulables orientées web.|
profid=|
desc=Développement d'applicatifs web, hébergement d'applications web, serveurs de fichiers et de sauvegarde, sites internet/intranet et intégration web, espaces clients, communication via internet (VoIP, messagerie instantanée), travail collaboratif. Spécialiste solutions libres pour l'entreprise (Zimbra, Dolibarr, Thaïs...) Région Languedoc-Rouissillon et voisines |
web=http://www.modulaweb.fr|
email=http://www.modulaweb.fr/portail/contact/|
zip=34000|
town=Montpellier|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Net Logic|
partner=no|
profid=SIRET: 477 583 264 00023|
desc=Installation et configuration de l'ERP/CRM Dolibarr sur nos serveurs, ou en local dans votre entreprise. Paramétrage, personnalisation, reporting spécifique, assistance.|
web=http://www.netlogic.fr/|
email=info@netlogic.fr|
zip=93160|
town=Noisy-le-Grand|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=no|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=NLTechno|
partner=yes|
desc=NLTechno is one of the most important contributor on Dolibarr and can host for you a Dolibarr database in a SaaS (Software As A Service) mode.|
profid=493 861 496 00021|
web=http://www.nltechno.com|
email=|
zip=92500|
town=Boulogne Billancourt|
country=fr|
service_hosting=yes (http://www.dolicloud.com)|
service_onlinesupport=yes|
service_emailsupport=only for DoliCloud.com customers|
service_dev=no|
service_local=no|
service_formation=no|
logo=logo_nltechno.png}}

{{TemplateCompany|
name=Open-Concept.pro|
partner=yes|
profid=537 828 717 00026|
desc=Open-concept.pro ([[Florian Henry]]) is dedicated to Open-Source ERP/CRM solition. Open-concept.pro ([[Florian Henry]]) is a contributor of Dolibarr sine 2010, and modules builder also|
web=http://www.open-concept.pro|
email=mailto:florian.henry@open-concept.pro|
zip=30129|
town=MANDUEL|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_openconcept.png}}

{{TemplateCompany|
name=OPEN-DSI|
profid=SIRET:75130522800015|
desc=Depuis 2012, nous accompagnons les petites et moyennes structures (1 à 50 salariés) dans la mise en place de solutions basées sur les logiciels libres. Nous proposons Dolibarr pour tous les besoins de gestion.|
web=https://www.open-dsi.fr|
email=mailto:infos@open-dsi.fr|
zip=69,38,01,42|
town=LYON|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=opendsi.png
}}

{{TemplateCompany|
name=Pascal Sené|
profid=|
desc=Logiciels libres et photographie.|
web=http://www.pascalsene.com|
email=contact@pascalsene.com|
zip=22,29,35,56|
town=Lannion|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=Patas-Monkey|
profid=|
desc=Conseil, formation, développement et modules|
web=http://www.patas-monkey.com|
email=r.deschamps@patas-monkey.com|
zip=69,42,38,01,83|
town=Lyon|
country=fr|
service_hosting=no|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Patasmonkey.jpg
}}

{{TemplateCompany|
name=ProbeSys|
profid=|
desc=Créée en 2003 par des passionnés du logiciel libre, [http://probesys.com ProbeSys] est une entreprise coopérative à l'image du secteur des nouvelles technologies : dynamique, réactive et participative. |
web=http://www.probesys.com|
email=mailto:contact@probesys.com|
zip=38600|
town=Fontaine|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes
}}

{{TemplateCompany|
name=Syllene|
profid=|
desc=We install and configure the software Dolibarr to suit your needs and train your users. We can also provide hosting and maintenance of your application.|
web=http://www.syllene.net/|
email=|
zip=|
town=|
country=fr|
service_hosting=yes|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=Teclib'|
profid=513893503|
partner=yes|
desc=
Teclib est une société de services en informatique au capital de 400 000€. Implantés à Paris, Colmar (Alsace), Caen, Chartres (Région Centre) et Bordeaux (Aquitaine). L'équipe Teclib' rassemble une quarantaine de personnes spécialisées dans l'intégration, hébergement et développements de logiciels libres tels que Dolibarr, Odoo, GLPI, Zimbra, BlueMind, Nagios, Centreon, ... |
web=http://www.teclib.com|
email=[mailto:contact@teclib.com?subject=Contact%20from%20Dolibarr%20Preferred%20Partners%20page contact@teclib.com]|
zip=75001|
town=Paris|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
logo=Logo_Teclib.png
}}

{{TemplateCompany|
name=Tiaris|
partner=yes|
profid=|
desc=Solutions and services for small businesses and merchants: e-commerce, maintenance, ERP/CRM Dolibarr, development telecommuting. ecommerce - dolibarr webservice based interface. Saas Offer Dolibarr + ecommerce connection for open source caddies (OsCommerce, Zencart, Crelaoded, Prestashop and others...)|
web=http://www.tiaris.fr/|
email=http://www.tiaris.fr/spip.php?page=contact|
zip=57870|
town=WALSCHEID|
country=fr|
service_hosting=yes|
service_onlinesupport=yes|
service_emailsupport=yes|
service_dev=yes|
service_local=yes|
service_formation=yes|
}}

{{TemplateCompany|
name=UTOPSYS - L'Informatique, Professionnelle.|
profid=|
desc=Maintenance, dépannage, conseil, audits, Green IT, solutions open-source de travail collaboratif, installation et maintenance Dolibarr. Bordeaux, CUB, Libourne.|
web=http://www.utopsys.fr|
email=|
zip=|
town=Libourne|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

{{TemplateCompany|
name=WEBINFOPRO|
profid=|
desc=Society Computers and Internet service for small businesses located in the suburbs west of Paris. One of the main activities is the integration of open source software.|
web=http://www.webinfopro.fr/|
email=|
zip=|
town=|
country=fr|
service_hosting=no|
service_onlinesupport=no|
service_emailsupport=no|
service_dev=yes|
service_local=yes|
service_formation=no|
}}

Translator documentation

2015-09-30T18:22:09Z

Rdoursenaud: Added web editor tutorial

<keywords content="translation, documentation, translator, localize, localization, i18n, internationalization, language" />

= [[File:Language.png]] Translate Dolibarr Application into your language =

Dolibarr language files are already translated in several languages.
English is the default and always complete. Other languages depend on contributions. This tutorial can help you complete a translation for a language not yet available or somehow incorrect.
Dolibarr can be translated by three different means:

# Manually using Transifex (Official and recommended method).
# Manually editing language files
# Completely automatic: autotranslator

== Manual Translation using Transifex online service (recommended) ==

Transifex is a web application that provides an online platform for translation projects. It includes teams and discussion tools, translation memory, glossary, proofreading and a lot of other features.
It is quite easy to use and all translations can be uploaded and downloaded through the web interface or using their TX client from a terminal.
Transifex is an open source project and the "community edition" can be freely downloaded and installed, but we will use the online hosted service.

===Using the web interface (for translators)===
If you want to help translating Dolibarr in your own language, check the project's page at https://www.transifex.com/dolibarr-association/dolibarr/

You can then register an account and request joining the project team for language(s) you're targeting. A manager will have to accept your request, so please be patient.

Once accepted, you can start translating right away.

For more informations, please check Transifex "Getting Started" introduction http://docs.transifex.com/introduction/translators/ and the web editor tutorial http://docs.transifex.com/tutorials/txeditor/

====Note about en_US====
The web interface can not be used to translate the en_US language which is source.
Any change must be done in Dolibarr source code and submitted using a Pull Request on our GitHub repository.

=== Using TX command line client (for Dolibarr [[:Category:Yoda]] team) ===
This describe how to use Transifex from command line. However, this is reserved to Dolibarr admin users to synchronize Transifex with Dolibarr main sources.

[http://docs.transifex.com/developer/client/ Official documentation]

====TX Client configuration====
First install TX Client.
With Debian/Ubuntu/Mint:
<source lang="bash">
apt-get install python-pip
pip install transifex-client
</source>
Then you have to initialize your TX environment. This is done by running '''tx init''' into dolibarr project root directory.
<source lang="bash">
cd git/dolibarr
tx init
</source>
Accept to overwrite config file. Keep default value for Transifex instance, then enter your Transifex login and password.

After this, a .transifexrc has been created into your HOME dir and a generic config file has been created as '''.tx/config''' in project's root.
So your directory's contents will look like that:
<code><pre>
.
|-- build
|-- build.xml
|-- ChangeLog
|-- COPYING
|-- COPYRIGHT
|-- dev
|-- doc
|-- .gitignore
|-- htdocs
|-- INSTALL
|-- pom.xml
|-- quickbuild.xml
|-- README
|-- README-FR
|-- README.md
|-- robots.txt
|-- scripts
|-- test
`-- .tx
</pre></code>

The current config file can be downloaded from https://github.com/Dolibarr/dolibarr/tree/develop/.tx , put it into .tx directory, overwriting the one created by '''tx init'''

This project configuration file is used to store the project’s details and the file-to-resource mappings.

That is a sample of what the config file contains:

<source lang="ini">
[main]
host = https://www.transifex.com
lang_map = uz: uz_UZ

[dolibarr.admin]
file_filter = htdocs/langs/<lang>/admin.lang
source_file = htdocs/langs/en_US/admin.lang
source_lang = en_US
type = MOZILLAPROPERTIES
</source>

Here is an explanation of the sections and options used in the config file:

<nowiki>[main] section</nowiki>

In this section we have project-wide options, such as the default transifex host for all projects. These can be overridden by each resource, in case it is needed.

<nowiki>[dolibarr.resource]</nowiki>

source_lang: this is the source language of the resource. 
source_file: this points to the source file directly. 
file_filter: here we hold the expression used to identify translation files under the specific project. ''not mandatory'' 
trans.<lang>: this is used for translation files that don’t follow a common naming schema and the file expression cannot be used to track them. ''not mandatory'' 
host: in case the project doesn’t use the default Transifex server as specified in the [main] section, it can override it using this option. ''not mandatory'' 

====TX Client use====
Some useful information on '''tx''' commands.

'''tx status'''

Show status of translations

'''tx push'''

Used to push changes from your computer to Transifex server 
Additional options for the tx push command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to push (defaults to all)
-r <resource> - Specify the resource for which you want to push the translations (defaults to all)
-f - Push source files without checking modification times
--skip - Don't stop on errors. Useful when pushing many files concurrently.
-s - Push the source file to the server
-t - Push the translation files to the server
--no-interactive - Don't require user input when forcing a push</pre></code>

'''tx pull'''

Used to pull changes from Transifex server to your computer 
Additional options for the tx pull command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to pull (defaults to all)
-r <resource> - Specify the resource for which you want to pull the translations (defaults to all)
-a - Fetch all translation files from server (even new ones)
-s - Force the fetching of the source file (default: False)
-f - Force download of translations files
--skip - Don't stop on errors. Useful when pushing many files concurrently.
--disable-overwrite - By default Transifex will fetch new translations files and replace existing ones. Use this flag if you want to disable this feature.
--minimum_perc=VALUE - Specify the minimum acceptable percentage of a translation in order to download it.</pre></code>

'''Examples'''

To pull translation files, you can use:

<source lang="bash">
tx -d pull -l it_IT # Get italian language only
tx -d pull -a # Get all languages
</source>

To push source files, just type:

<source lang="bash">
tx -d push -t -l it_IT [-r dolibarr.file] # To push only a specific translation file
tx -d push -s # To push source file
</source>

=== Other questions on transifex process ===
This is short questions and answer you may also ask about transifex translation process:

1) Is the sync on a regular time interval ?

No. It is done where there is enough translation submitted. It is also done on a beta branch just before creating the final release package.

2) Are all the translations synced to git, or only the reviewed translations. Do I need to review before sync is done ?

When a Sync is done, transifex files overwrites files into git, but only if there is at least on record modified for the file.
You don't have to make review before sync is done. Making review is above all to know which lines were manually reviewed and which one were initially translated using a robot.

3) In which Dolibarr releases will translations be available ? Are transifex translations also synced to maintenance releases ?

Sync is always done on develop and/or beta.
So transifex changes appear in all version whose branch is created after the transifex change (a sync is always done before creating a new branch). Once a branch is created, then new changes into transifex will be available only for next branch. Reason of this is that transifex is not able to manage branch/versions (not yet).

== Manual Translation (not recommended) ==

To translate Dolibarr into another language, go to the langs directory and create a folder/directory named with the code language to translate (follow the existing format, for example en_US, en_GB, es_ES, de_DE, etc...). Then copy the files from an existing language directory (for example en_US/main.lang, en_GB/bills.lang), into the new language directory that you have just created.

These files have the format of key/value pairs in each line like the followings:

<source lang="ini">
Code1 = translate phrase 1
Code2 = translate phrase 2
...
Coden = translate phrase n
</source>

Translate the phrases (the value portion of the key/value pairs) on right side of the "=" as seen above, the code (the key portion) on left side of "=" should remain unchanged. It is possible to translate the files one by one, without bringing them all at once. If a file has not been translated into the new language, Dolibarr uses English.

To have a localised (translated) string into the PHP code, all you have to do is load the language file and use the method to get the translated value, like this:

<source lang="php">
$langs->load("myfile"); // or use $langs->load("myfile@mymodule") if myfile.lang is inside directory htdocs/mymodule/langs/xx_XX

print $langs->trans("CodeX")
</source>

An entry type;

<source lang="ini">
CodeX = phrase X
</source>

must be present or added to the myfile.lang file.

== Automatic Translation with autotranslator.php tool ==

* Translator OS: All
* Tool: '''autotranslator.php''' provided with Dolibarr in directory '''dev/translation'''.
This method is recommended when starting translation for a language not already initialized. If there is already a translation available but you need to add missing key or correct errors, try to use method using Transifex (see later).

To make or update all files of a language code, just run the script:
<source lang="bash">
php autotranslator.php lang_code_source lang_code_target GOOGLEAPIKEY
</source>
For example :
<source lang="bash">
php autotranslator.php en_US pt_PT GOOGLEAPIKEY
</source>
to translate into Portuguese (pt_PT) using English (en_US) files.

All non existing files will be created, all existing files will be updated.
The tool use [http://translate.google.com Google translation] service to find the translation value of a string, so a working Internet connection is required from station running the script. Also a GOOGLEAPIKEY is required and Google charges a fee for using this service (20 euros / 1 000 000 of translated chars).
Your PHP must also have permissions to write into '''htdocs/langs''' directory and must have curl functions available.

= [[File:Language.png]] Distribute or include your translation into core source =

== Including your translation in the official Dolibarr sources ==

Once you start translating, it's a smart decision to share it, so it can be included into the official code of Dolibarr.
If you keep it for you, others will not be able to improve it when new terms are added or previous terms are modified, and you will still have to manage the translation on your own.

If you translated through the Transifex system, there's nothing to be done. Your translation will be included in the next version of Dolibarr. No additional work! In technical terms, the translation will be exported from Transifex and imported into Dolibarr by our developers, at least once every month.

If, however, you translated directly in Dolibarr files, then you will first have to transfer those translations to Transifex before they can be included. So, really, you should start translating into Transifex.
If you send us your translation through a Pull Request on Github, sadly, it will be overwritten by the next import from Transifex, so it would be very short-lived.

=== Adding new variables ===

The reference language is en_US and is always complete. You can find it in the htdocs/langs/en_US/ folder. All other language files are likely to be slightly or highly incomplete, depending on the language.

If you are developing a new module, you are likely going to need the addition of new language variables. This is done exclusively through the update of the en_US language (htdocs/langs/en_US/ folder). Just modify these files to add the variable you need and send the resulting folder as part of your Pull Request. Refer to the developer documentation to learn how to contribute code (you will need an account on {{TemplateUrlSCM}}.

== As an extension ==
When you create a new language, if it is not already integrated into Dolibarr, it can still be broadcast to all other users. You can make a distribution package using the '''build/makepack-dolibarrlang.pl''' script or making a zip archive manually and posting it on dolistore.com or sending it to the developers' mailing list '''dolibarr-dev''' ({{TemplateURLMLDev}}).

New language files are immediately available in an installation as soon as the archive is unzipped in the correct directory.

= [[File:Language.png]] Translate documentation on wiki =
The wiki is written in 3 languages: English, French and Spanish.
If you want to enhance documentation on one of these languages, all you have to do is to create an account on this wiki.
Then, you can edit existing pages to correct a bad translation or translate pages waiting for translation [[:Category:Page_waiting_for_translation]].

Translator documentation

2015-09-30T18:20:04Z

Rdoursenaud: Streamlined joining process description

<keywords content="translation, documentation, translator, localize, localization, i18n, internationalization, language" />

= [[File:Language.png]] Translate Dolibarr Application into your language =

Dolibarr language files are already translated in several languages.
English is the default and always complete. Other languages depend on contributions. This tutorial can help you complete a translation for a language not yet available or somehow incorrect.
Dolibarr can be translated by three different means:

# Manually using Transifex (Official and recommended method).
# Manually editing language files
# Completely automatic: autotranslator

== Manual Translation using Transifex online service (recommended) ==

Transifex is a web application that provides an online platform for translation projects. It includes teams and discussion tools, translation memory, glossary, proofreading and a lot of other features.
It is quite easy to use and all translations can be uploaded and downloaded through the web interface or using their TX client from a terminal.
Transifex is an open source project and the "community edition" can be freely downloaded and installed, but we will use the online hosted service.

===Using the web interface (for translators)===
If you want to help translating Dolibarr in your own language, check the project's page at https://www.transifex.com/dolibarr-association/dolibarr/

You can then register an account and request joining the project team for language(s) you're targeting. A manager will have to accept your request, so please be patient.

Once accepted, you can start translating right away.

For more informations, please check Transifex "Getting Started" introduction: http://docs.transifex.com/introduction/translators/

====Note about en_US====
The web interface can not be used to translate the en_US language which is source.
Any change must be done in Dolibarr source code and submitted using a Pull Request on our GitHub repository.

=== Using TX command line client (for Dolibarr [[:Category:Yoda]] team) ===
This describe how to use Transifex from command line. However, this is reserved to Dolibarr admin users to synchronize Transifex with Dolibarr main sources.

[http://docs.transifex.com/developer/client/ Official documentation]

====TX Client configuration====
First install TX Client.
With Debian/Ubuntu/Mint:
<source lang="bash">
apt-get install python-pip
pip install transifex-client
</source>
Then you have to initialize your TX environment. This is done by running '''tx init''' into dolibarr project root directory.
<source lang="bash">
cd git/dolibarr
tx init
</source>
Accept to overwrite config file. Keep default value for Transifex instance, then enter your Transifex login and password.

After this, a .transifexrc has been created into your HOME dir and a generic config file has been created as '''.tx/config''' in project's root.
So your directory's contents will look like that:
<code><pre>
.
|-- build
|-- build.xml
|-- ChangeLog
|-- COPYING
|-- COPYRIGHT
|-- dev
|-- doc
|-- .gitignore
|-- htdocs
|-- INSTALL
|-- pom.xml
|-- quickbuild.xml
|-- README
|-- README-FR
|-- README.md
|-- robots.txt
|-- scripts
|-- test
`-- .tx
</pre></code>

The current config file can be downloaded from https://github.com/Dolibarr/dolibarr/tree/develop/.tx , put it into .tx directory, overwriting the one created by '''tx init'''

This project configuration file is used to store the project’s details and the file-to-resource mappings.

That is a sample of what the config file contains:

<source lang="ini">
[main]
host = https://www.transifex.com
lang_map = uz: uz_UZ

[dolibarr.admin]
file_filter = htdocs/langs/<lang>/admin.lang
source_file = htdocs/langs/en_US/admin.lang
source_lang = en_US
type = MOZILLAPROPERTIES
</source>

Here is an explanation of the sections and options used in the config file:

<nowiki>[main] section</nowiki>

In this section we have project-wide options, such as the default transifex host for all projects. These can be overridden by each resource, in case it is needed.

<nowiki>[dolibarr.resource]</nowiki>

source_lang: this is the source language of the resource. 
source_file: this points to the source file directly. 
file_filter: here we hold the expression used to identify translation files under the specific project. ''not mandatory'' 
trans.<lang>: this is used for translation files that don’t follow a common naming schema and the file expression cannot be used to track them. ''not mandatory'' 
host: in case the project doesn’t use the default Transifex server as specified in the [main] section, it can override it using this option. ''not mandatory'' 

====TX Client use====
Some useful information on '''tx''' commands.

'''tx status'''

Show status of translations

'''tx push'''

Used to push changes from your computer to Transifex server 
Additional options for the tx push command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to push (defaults to all)
-r <resource> - Specify the resource for which you want to push the translations (defaults to all)
-f - Push source files without checking modification times
--skip - Don't stop on errors. Useful when pushing many files concurrently.
-s - Push the source file to the server
-t - Push the translation files to the server
--no-interactive - Don't require user input when forcing a push</pre></code>

'''tx pull'''

Used to pull changes from Transifex server to your computer 
Additional options for the tx pull command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to pull (defaults to all)
-r <resource> - Specify the resource for which you want to pull the translations (defaults to all)
-a - Fetch all translation files from server (even new ones)
-s - Force the fetching of the source file (default: False)
-f - Force download of translations files
--skip - Don't stop on errors. Useful when pushing many files concurrently.
--disable-overwrite - By default Transifex will fetch new translations files and replace existing ones. Use this flag if you want to disable this feature.
--minimum_perc=VALUE - Specify the minimum acceptable percentage of a translation in order to download it.</pre></code>

'''Examples'''

To pull translation files, you can use:

<source lang="bash">
tx -d pull -l it_IT # Get italian language only
tx -d pull -a # Get all languages
</source>

To push source files, just type:

<source lang="bash">
tx -d push -t -l it_IT [-r dolibarr.file] # To push only a specific translation file
tx -d push -s # To push source file
</source>

=== Other questions on transifex process ===
This is short questions and answer you may also ask about transifex translation process:

1) Is the sync on a regular time interval ?

No. It is done where there is enough translation submitted. It is also done on a beta branch just before creating the final release package.

2) Are all the translations synced to git, or only the reviewed translations. Do I need to review before sync is done ?

When a Sync is done, transifex files overwrites files into git, but only if there is at least on record modified for the file.
You don't have to make review before sync is done. Making review is above all to know which lines were manually reviewed and which one were initially translated using a robot.

3) In which Dolibarr releases will translations be available ? Are transifex translations also synced to maintenance releases ?

Sync is always done on develop and/or beta.
So transifex changes appear in all version whose branch is created after the transifex change (a sync is always done before creating a new branch). Once a branch is created, then new changes into transifex will be available only for next branch. Reason of this is that transifex is not able to manage branch/versions (not yet).

== Manual Translation (not recommended) ==

To translate Dolibarr into another language, go to the langs directory and create a folder/directory named with the code language to translate (follow the existing format, for example en_US, en_GB, es_ES, de_DE, etc...). Then copy the files from an existing language directory (for example en_US/main.lang, en_GB/bills.lang), into the new language directory that you have just created.

These files have the format of key/value pairs in each line like the followings:

<source lang="ini">
Code1 = translate phrase 1
Code2 = translate phrase 2
...
Coden = translate phrase n
</source>

Translate the phrases (the value portion of the key/value pairs) on right side of the "=" as seen above, the code (the key portion) on left side of "=" should remain unchanged. It is possible to translate the files one by one, without bringing them all at once. If a file has not been translated into the new language, Dolibarr uses English.

To have a localised (translated) string into the PHP code, all you have to do is load the language file and use the method to get the translated value, like this:

<source lang="php">
$langs->load("myfile"); // or use $langs->load("myfile@mymodule") if myfile.lang is inside directory htdocs/mymodule/langs/xx_XX

print $langs->trans("CodeX")
</source>

An entry type;

<source lang="ini">
CodeX = phrase X
</source>

must be present or added to the myfile.lang file.

== Automatic Translation with autotranslator.php tool ==

* Translator OS: All
* Tool: '''autotranslator.php''' provided with Dolibarr in directory '''dev/translation'''.
This method is recommended when starting translation for a language not already initialized. If there is already a translation available but you need to add missing key or correct errors, try to use method using Transifex (see later).

To make or update all files of a language code, just run the script:
<source lang="bash">
php autotranslator.php lang_code_source lang_code_target GOOGLEAPIKEY
</source>
For example :
<source lang="bash">
php autotranslator.php en_US pt_PT GOOGLEAPIKEY
</source>
to translate into Portuguese (pt_PT) using English (en_US) files.

All non existing files will be created, all existing files will be updated.
The tool use [http://translate.google.com Google translation] service to find the translation value of a string, so a working Internet connection is required from station running the script. Also a GOOGLEAPIKEY is required and Google charges a fee for using this service (20 euros / 1 000 000 of translated chars).
Your PHP must also have permissions to write into '''htdocs/langs''' directory and must have curl functions available.

= [[File:Language.png]] Distribute or include your translation into core source =

== Including your translation in the official Dolibarr sources ==

Once you start translating, it's a smart decision to share it, so it can be included into the official code of Dolibarr.
If you keep it for you, others will not be able to improve it when new terms are added or previous terms are modified, and you will still have to manage the translation on your own.

If you translated through the Transifex system, there's nothing to be done. Your translation will be included in the next version of Dolibarr. No additional work! In technical terms, the translation will be exported from Transifex and imported into Dolibarr by our developers, at least once every month.

If, however, you translated directly in Dolibarr files, then you will first have to transfer those translations to Transifex before they can be included. So, really, you should start translating into Transifex.
If you send us your translation through a Pull Request on Github, sadly, it will be overwritten by the next import from Transifex, so it would be very short-lived.

=== Adding new variables ===

The reference language is en_US and is always complete. You can find it in the htdocs/langs/en_US/ folder. All other language files are likely to be slightly or highly incomplete, depending on the language.

If you are developing a new module, you are likely going to need the addition of new language variables. This is done exclusively through the update of the en_US language (htdocs/langs/en_US/ folder). Just modify these files to add the variable you need and send the resulting folder as part of your Pull Request. Refer to the developer documentation to learn how to contribute code (you will need an account on {{TemplateUrlSCM}}.

== As an extension ==
When you create a new language, if it is not already integrated into Dolibarr, it can still be broadcast to all other users. You can make a distribution package using the '''build/makepack-dolibarrlang.pl''' script or making a zip archive manually and posting it on dolistore.com or sending it to the developers' mailing list '''dolibarr-dev''' ({{TemplateURLMLDev}}).

New language files are immediately available in an installation as soon as the archive is unzipped in the correct directory.

= [[File:Language.png]] Translate documentation on wiki =
The wiki is written in 3 languages: English, French and Spanish.
If you want to enhance documentation on one of these languages, all you have to do is to create an account on this wiki.
Then, you can edit existing pages to correct a bad translation or translate pages waiting for translation [[:Category:Page_waiting_for_translation]].

Translator documentation

2015-09-30T18:05:44Z

Rdoursenaud: Updated project links

<keywords content="translation, documentation, translator, localize, localization, i18n, internationalization, language" />

= [[File:Language.png]] Translate Dolibarr Application into your language =

Dolibarr language files are already translated in several languages.
English is the default and always complete. Other languages depend on contributions. This tutorial can help you complete a translation for a language not yet available or somehow incorrect.
Dolibarr can be translated by three different means:

# Manually using Transifex (Official and recommended method).
# Manually editing language files
# Completely automatic: autotranslator

== Manual Translation using Transifex online service (recommended) ==

Transifex is a web application that provides an online platform for translation projects. It includes teams and discussion tools, translation memory, glossary, proofreading and a lot of other features.
It is quite easy to use and all translations can be uploaded and downloaded through the web interface or using their TX client from a terminal.
Transifex is an open source project and the "community edition" can be freely downloaded and installed, but we will use the online hosted service.

===Create transifex account and choose language===
If you want to help translating Dolibarr in your own language, first create a Transifex account on https://www.transifex.com

Then refer to https://www.transifex.com/dolibarr-association/dolibarr/ and see if language is already supported. If it exists (many teams are already working for the project), you can ask to join the team and start to translate right away; if there is not a team for your language, you should request a new translation team on Transifex. It can be done directly using transifex.com interface on the website.

===Using the web interface (for translators) ===
If language is already available onto page https://www.transifex.com/dolibarr-association/dolibarr/, just create an account and follow instruction of transifex web site to translate files.

Note, that this web interface must not be used to translate en_US language that is source. Any change on source language must be done by submitting code change using GitHub Pull Requests.

=== Using TX command line client (for Dolibarr [[:Category:Yoda]] team) ===
This describe how to use Transifex from command line. However, this is reserved to Dolibarr admin users to synchronize Transifex with Dolibarr main sources.

[http://docs.transifex.com/developer/client/ Official documentation]

====TX Client configuration====
First install TX Client.
With Debian/Ubuntu/Mint:
<source lang="bash">
apt-get install python-pip
pip install transifex-client
</source>
Then you have to initialize your TX environment. This is done by running '''tx init''' into dolibarr project root directory.
<source lang="bash">
cd git/dolibarr
tx init
</source>
Accept to overwrite config file. Keep default value for Transifex instance, then enter your Transifex login and password.

After this, a .transifexrc has been created into your HOME dir and a generic config file has been created as '''.tx/config''' in project's root.
So your directory's contents will look like that:
<code><pre>
.
|-- build
|-- build.xml
|-- ChangeLog
|-- COPYING
|-- COPYRIGHT
|-- dev
|-- doc
|-- .gitignore
|-- htdocs
|-- INSTALL
|-- pom.xml
|-- quickbuild.xml
|-- README
|-- README-FR
|-- README.md
|-- robots.txt
|-- scripts
|-- test
`-- .tx
</pre></code>

The current config file can be downloaded from https://github.com/Dolibarr/dolibarr/tree/develop/.tx , put it into .tx directory, overwriting the one created by '''tx init'''

This project configuration file is used to store the project’s details and the file-to-resource mappings.

That is a sample of what the config file contains:

<source lang="ini">
[main]
host = https://www.transifex.com
lang_map = uz: uz_UZ

[dolibarr.admin]
file_filter = htdocs/langs/<lang>/admin.lang
source_file = htdocs/langs/en_US/admin.lang
source_lang = en_US
type = MOZILLAPROPERTIES
</source>

Here is an explanation of the sections and options used in the config file:

<nowiki>[main] section</nowiki>

In this section we have project-wide options, such as the default transifex host for all projects. These can be overridden by each resource, in case it is needed.

<nowiki>[dolibarr.resource]</nowiki>

source_lang: this is the source language of the resource. 
source_file: this points to the source file directly. 
file_filter: here we hold the expression used to identify translation files under the specific project. ''not mandatory'' 
trans.<lang>: this is used for translation files that don’t follow a common naming schema and the file expression cannot be used to track them. ''not mandatory'' 
host: in case the project doesn’t use the default Transifex server as specified in the [main] section, it can override it using this option. ''not mandatory'' 

====TX Client use====
Some useful information on '''tx''' commands.

'''tx status'''

Show status of translations

'''tx push'''

Used to push changes from your computer to Transifex server 
Additional options for the tx push command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to push (defaults to all)
-r <resource> - Specify the resource for which you want to push the translations (defaults to all)
-f - Push source files without checking modification times
--skip - Don't stop on errors. Useful when pushing many files concurrently.
-s - Push the source file to the server
-t - Push the translation files to the server
--no-interactive - Don't require user input when forcing a push</pre></code>

'''tx pull'''

Used to pull changes from Transifex server to your computer 
Additional options for the tx pull command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to pull (defaults to all)
-r <resource> - Specify the resource for which you want to pull the translations (defaults to all)
-a - Fetch all translation files from server (even new ones)
-s - Force the fetching of the source file (default: False)
-f - Force download of translations files
--skip - Don't stop on errors. Useful when pushing many files concurrently.
--disable-overwrite - By default Transifex will fetch new translations files and replace existing ones. Use this flag if you want to disable this feature.
--minimum_perc=VALUE - Specify the minimum acceptable percentage of a translation in order to download it.</pre></code>

'''Examples'''

To pull translation files, you can use:

<source lang="bash">
tx -d pull -l it_IT # Get italian language only
tx -d pull -a # Get all languages
</source>

To push source files, just type:

<source lang="bash">
tx -d push -t -l it_IT [-r dolibarr.file] # To push only a specific translation file
tx -d push -s # To push source file
</source>

=== Other questions on transifex process ===
This is short questions and answer yuo may also ask about transifex translation process:

1) Is the sync on a regular time interval ?

No. It is done where there is enough translation submited. It is also done on a beta branch just before creating the final release package.

2) Are all the translations synced to git, or only the reviewed translations. Do I need to review before sync is done ?

When a Sync is done, transifex files overwrites files into git, but only if there is at least on record modified for the file.
You don't have to make review before sync is done. Making review is above all to know which lines were manually reviewed and which one were initially translated using a robot.

3) In which Dolibarr releases will translations be available ? Are transifex translations also synced to maintenance releases ?

Sync is always done on develop and/or beta.
So transifex changes appear in all version whose branch is created after the transifex change (a sync is always done before creating a new branch). Once a branch is created, then new changes into transifex will be available only for next branch. Reason of this is that transifex is not able to manage branch/versions (not yet).

== Manual Translation (not recommended) ==

To translate Dolibarr into another language, go to the langs directory and create a folder/directory named with the code language to translate (follow the existing format, for example en_US, en_GB, es_ES, de_DE, etc...). Then copy the files from an existing language directory (for example en_US/main.lang, en_GB/bills.lang), into the new language directory that you have just created.

These files have the format of key/value pairs in each line like the followings:

<source lang="ini">
Code1 = translate phrase 1
Code2 = translate phrase 2
...
Coden = translate phrase n
</source>

Translate the phrases (the value portion of the key/value pairs) on right side of the "=" as seen above, the code (the key portion) on left side of "=" should remain unchanged. It is possible to translate the files one by one, without bringing them all at once. If a file has not been translated into the new language, Dolibarr uses English.

To have a localised (translated) string into the PHP code, all you have to do is load the language file and use the method to get the translated value, like this:

<source lang="php">
$langs->load("myfile"); // or use $langs->load("myfile@mymodule") if myfile.lang is inside directory htdocs/mymodule/langs/xx_XX

print $langs->trans("CodeX")
</source>

An entry type;

<source lang="ini">
CodeX = phrase X
</source>

must be present or added to the myfile.lang file.

== Automatic Translation with autotranslator.php tool ==

* Translator OS: All
* Tool: '''autotranslator.php''' provided with Dolibarr in directory '''dev/translation'''.
This method is recommended when starting translation for a language not already initialized. If there is already a translation available but you need to add missing key or correct errors, try to use method using Transifex (see later).

To make or update all files of a language code, just run the script:
<source lang="bash">
php autotranslator.php lang_code_source lang_code_target GOOGLEAPIKEY
</source>
For example :
<source lang="bash">
php autotranslator.php en_US pt_PT GOOGLEAPIKEY
</source>
to translate into Portuguese (pt_PT) using English (en_US) files.

All non existing files will be created, all existing files will be updated.
The tool use [http://translate.google.com Google translation] service to find the translation value of a string, so a working Internet connection is required from station running the script. Also a GOOGLEAPIKEY is required and Google charges a fee for using this service (20 euros / 1 000 000 of translated chars).
Your PHP must also have permissions to write into '''htdocs/langs''' directory and must have curl functions available.

= [[File:Language.png]] Distribute or include your translation into core source =

== Including your translation in the official Dolibarr sources ==

Once you start translating, it's a smart decision to share it, so it can be included into the official code of Dolibarr.
If you keep it for you, others will not be able to improve it when new terms are added or previous terms are modified, and you will still have to manage the translation on your own.

If you translated through the Transifex system, there's nothing to be done. Your translation will be included in the next version of Dolibarr. No additional work! In technical terms, the translation will be exported from Transifex and imported into Dolibarr by our developers, at least once every month.

If, however, you translated directly in Dolibarr files, then you will first have to transfer those translations to Transifex before they can be included. So, really, you should start translating into Transifex.
If you send us your translation through a Pull Request on Github, sadly, it will be overwritten by the next import from Transifex, so it would be very short-lived.

=== Adding new variables ===

The reference language is en_US and is always complete. You can find it in the htdocs/langs/en_US/ folder. All other language files are likely to be slightly or highly incomplete, depending on the language.

If you are developing a new module, you are likely going to need the addition of new language variables. This is done exclusively through the update of the en_US language (htdocs/langs/en_US/ folder). Just modify these files to add the variable you need and send the resulting folder as part of your Pull Request. Refer to the developer documentation to learn how to contribute code (you will need an account on {{TemplateUrlSCM}}.

== As an extension ==
When you create a new language, if it is not already integrated into Dolibarr, it can still be broadcast to all other users. You can make a distribution package using the '''build/makepack-dolibarrlang.pl''' script or making a zip archive manually and posting it on dolistore.com or sending it to the developers' mailing list '''dolibarr-dev''' ({{TemplateURLMLDev}}).

New language files are immediately available in an installation as soon as the archive is unzipped in the correct directory.

= [[File:Language.png]] Translate documentation on wiki =
The wiki is written in 3 languages: English, French and Spanish.
If you want to enhance documentation on one of these languages, all you have to do is to create an account on this wiki.
Then, you can edit existing pages to correct a bad translation or translate pages waiting for translation [[:Category:Page_waiting_for_translation]].

Translator documentation

2015-09-30T18:00:38Z

Rdoursenaud: Wording and typos

<keywords content="translation, documentation, translator, localize, localization, i18n, internationalization, language" />

= [[File:Language.png]] Translate Dolibarr Application into your language =

Dolibarr language files are already translated in several languages.
English is the default and always complete. Other languages depend on contributions. This tutorial can help you complete a translation for a language not yet available or somehow incorrect.
Dolibarr can be translated by three different means:

# Manually using Transifex.com (Official and recommended method).
# Manually editing language files
# Completely automatic: autotranslator

== Manual Translation using Transifex online service (recommended) ==

Transifex is a web application that provides an online platform for translation projects. It includes teams and discussion tools, translation memory, glossary, proofreading and a lot of other features.
It is quite easy to use and all translations can be uploaded and downloaded through the web interface or using their TX client from a terminal.
Transifex is an open source project and the "community edition" can be freely downloaded and installed, but we will use the online hosted service.

===Create transifex account and choose language===
If you want to help translating Dolibarr in your own language, first create a Transifex account on http://transifex.com

Then refer to http://transifex.com/projects/p/dolibarr/ and see if language is already supported. If it exists (many teams are already working for the project), you can ask to join the team and start to translate right away; if there is not a team for your language, you should request a new translation team on Transifex. It can be done directly using transifex.com interface on the website.

===Using the web interface (for translators) ===
If language is already available onto page http://transifex.com/projects/p/dolibarr/, just create an account and follow instruction of transifex web site to translate files.

Note, that this web interface must not be used to translate en_US language that is source. Any change on source language must be done by submitting code change using GitHub Pull Requests.

=== Using TX command line client (for Dolibarr [[:Category:Yoda]] team) ===
This describe how to use Transifex from command line. However, this is reserved to Dolibarr admin users to synchronize Transifex with Dolibarr main sources.

[http://docs.transifex.com/developer/client/ Official documentation]

====TX Client configuration====
First install TX Client.
With Debian/Ubuntu/Mint:
<source lang="bash">
apt-get install python-pip
pip install transifex-client
</source>
Then you have to initialize your TX environment. This is done by running '''tx init''' into dolibarr project root directory.
<source lang="bash">
cd git/dolibarr
tx init
</source>
Accept to overwrite config file. Keep default value for Transifex instance, then enter your Transifex login and password.

After this, a .transifexrc has been created into your HOME dir and a generic config file has been created as '''.tx/config''' in project's root.
So your directory's contents will look like that:
<code><pre>
.
|-- build
|-- build.xml
|-- ChangeLog
|-- COPYING
|-- COPYRIGHT
|-- dev
|-- doc
|-- .gitignore
|-- htdocs
|-- INSTALL
|-- pom.xml
|-- quickbuild.xml
|-- README
|-- README-FR
|-- README.md
|-- robots.txt
|-- scripts
|-- test
`-- .tx
</pre></code>

The current config file can be downloaded from https://github.com/Dolibarr/dolibarr/tree/develop/.tx , put it into .tx directory, overwriting the one created by '''tx init'''

This project configuration file is used to store the project’s details and the file-to-resource mappings.

That is a sample of what the config file contains:

<source lang="ini">
[main]
host = https://www.transifex.com
lang_map = uz: uz_UZ

[dolibarr.admin]
file_filter = htdocs/langs/<lang>/admin.lang
source_file = htdocs/langs/en_US/admin.lang
source_lang = en_US
type = MOZILLAPROPERTIES
</source>

Here is an explanation of the sections and options used in the config file:

<nowiki>[main] section</nowiki>

In this section we have project-wide options, such as the default transifex host for all projects. These can be overridden by each resource, in case it is needed.

<nowiki>[dolibarr.resource]</nowiki>

source_lang: this is the source language of the resource. 
source_file: this points to the source file directly. 
file_filter: here we hold the expression used to identify translation files under the specific project. ''not mandatory'' 
trans.<lang>: this is used for translation files that don’t follow a common naming schema and the file expression cannot be used to track them. ''not mandatory'' 
host: in case the project doesn’t use the default Transifex server as specified in the [main] section, it can override it using this option. ''not mandatory'' 

====TX Client use====
Some useful information on '''tx''' commands.

'''tx status'''

Show status of translations

'''tx push'''

Used to push changes from your computer to Transifex server 
Additional options for the tx push command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to push (defaults to all)
-r <resource> - Specify the resource for which you want to push the translations (defaults to all)
-f - Push source files without checking modification times
--skip - Don't stop on errors. Useful when pushing many files concurrently.
-s - Push the source file to the server
-t - Push the translation files to the server
--no-interactive - Don't require user input when forcing a push</pre></code>

'''tx pull'''

Used to pull changes from Transifex server to your computer 
Additional options for the tx pull command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to pull (defaults to all)
-r <resource> - Specify the resource for which you want to pull the translations (defaults to all)
-a - Fetch all translation files from server (even new ones)
-s - Force the fetching of the source file (default: False)
-f - Force download of translations files
--skip - Don't stop on errors. Useful when pushing many files concurrently.
--disable-overwrite - By default Transifex will fetch new translations files and replace existing ones. Use this flag if you want to disable this feature.
--minimum_perc=VALUE - Specify the minimum acceptable percentage of a translation in order to download it.</pre></code>

'''Examples'''

To pull translation files, you can use:

<source lang="bash">
tx -d pull -l it_IT # Get italian language only
tx -d pull -a # Get all languages
</source>

To push source files, just type:

<source lang="bash">
tx -d push -t -l it_IT [-r dolibarr.file] # To push only a specific translation file
tx -d push -s # To push source file
</source>

=== Other questions on transifex process ===
This is short questions and answer yuo may also ask about transifex translation process:

1) Is the sync on a regular time interval ?

No. It is done where there is enough translation submited. It is also done on a beta branch just before creating the final release package.

2) Are all the translations synced to git, or only the reviewed translations. Do I need to review before sync is done ?

When a Sync is done, transifex files overwrites files into git, but only if there is at least on record modified for the file.
You don't have to make review before sync is done. Making review is above all to know which lines were manually reviewed and which one were initially translated using a robot.

3) In which Dolibarr releases will translations be available ? Are transifex translations also synced to maintenance releases ?

Sync is always done on develop and/or beta.
So transifex changes appear in all version whose branch is created after the transifex change (a sync is always done before creating a new branch). Once a branch is created, then new changes into transifex will be available only for next branch. Reason of this is that transifex is not able to manage branch/versions (not yet).

== Manual Translation (not recommended) ==

To translate Dolibarr into another language, go to the langs directory and create a folder/directory named with the code language to translate (follow the existing format, for example en_US, en_GB, es_ES, de_DE, etc...). Then copy the files from an existing language directory (for example en_US/main.lang, en_GB/bills.lang), into the new language directory that you have just created.

These files have the format of key/value pairs in each line like the followings:

<source lang="ini">
Code1 = translate phrase 1
Code2 = translate phrase 2
...
Coden = translate phrase n
</source>

Translate the phrases (the value portion of the key/value pairs) on right side of the "=" as seen above, the code (the key portion) on left side of "=" should remain unchanged. It is possible to translate the files one by one, without bringing them all at once. If a file has not been translated into the new language, Dolibarr uses English.

To have a localised (translated) string into the PHP code, all you have to do is load the language file and use the method to get the translated value, like this:

<source lang="php">
$langs->load("myfile"); // or use $langs->load("myfile@mymodule") if myfile.lang is inside directory htdocs/mymodule/langs/xx_XX

print $langs->trans("CodeX")
</source>

An entry type;

<source lang="ini">
CodeX = phrase X
</source>

must be present or added to the myfile.lang file.

== Automatic Translation with autotranslator.php tool ==

* Translator OS: All
* Tool: '''autotranslator.php''' provided with Dolibarr in directory '''dev/translation'''.
This method is recommended when starting translation for a language not already initialized. If there is already a translation available but you need to add missing key or correct errors, try to use method using Transifex (see later).

To make or update all files of a language code, just run the script:
<source lang="bash">
php autotranslator.php lang_code_source lang_code_target GOOGLEAPIKEY
</source>
For example :
<source lang="bash">
php autotranslator.php en_US pt_PT GOOGLEAPIKEY
</source>
to translate into Portuguese (pt_PT) using English (en_US) files.

All non existing files will be created, all existing files will be updated.
The tool use [http://translate.google.com Google translation] service to find the translation value of a string, so a working Internet connection is required from station running the script. Also a GOOGLEAPIKEY is required and Google charges a fee for using this service (20 euros / 1 000 000 of translated chars).
Your PHP must also have permissions to write into '''htdocs/langs''' directory and must have curl functions available.

= [[File:Language.png]] Distribute or include your translation into core source =

== Including your translation in the official Dolibarr sources ==

Once you start translating, it's a smart decision to share it, so it can be included into the official code of Dolibarr.
If you keep it for you, others will not be able to improve it when new terms are added or previous terms are modified, and you will still have to manage the translation on your own.

If you translated through the Transifex system, there's nothing to be done. Your translation will be included in the next version of Dolibarr. No additional work! In technical terms, the translation will be exported from Transifex and imported into Dolibarr by our developers, at least once every month.

If, however, you translated directly in Dolibarr files, then you will first have to transfer those translations to Transifex before they can be included. So, really, you should start translating into Transifex.
If you send us your translation through a Pull Request on Github, sadly, it will be overwritten by the next import from Transifex, so it would be very short-lived.

=== Adding new variables ===

The reference language is en_US and is always complete. You can find it in the htdocs/langs/en_US/ folder. All other language files are likely to be slightly or highly incomplete, depending on the language.

If you are developing a new module, you are likely going to need the addition of new language variables. This is done exclusively through the update of the en_US language (htdocs/langs/en_US/ folder). Just modify these files to add the variable you need and send the resulting folder as part of your Pull Request. Refer to the developer documentation to learn how to contribute code (you will need an account on {{TemplateUrlSCM}}.

== As an extension ==
When you create a new language, if it is not already integrated into Dolibarr, it can still be broadcast to all other users. You can make a distribution package using the '''build/makepack-dolibarrlang.pl''' script or making a zip archive manually and posting it on dolistore.com or sending it to the developers' mailing list '''dolibarr-dev''' ({{TemplateURLMLDev}}).

New language files are immediately available in an installation as soon as the archive is unzipped in the correct directory.

= [[File:Language.png]] Translate documentation on wiki =
The wiki is written in 3 languages: English, French and Spanish.
If you want to enhance documentation on one of these languages, all you have to do is to create an account on this wiki.
Then, you can edit existing pages to correct a bad translation or translate pages waiting for translation [[:Category:Page_waiting_for_translation]].

Template:ListOfOtherPHPExtensions

2015-09-25T10:10:41Z

Rdoursenaud: Added required calendar extension for functions like easter_date() in date.lib.php

* for date manipulations:
** calendar
* for PHPExcel:
** zip (handling of .xlsx, .ods and .gnumeric files)
** xml
** gd2 (optional, but required for exact column width autocalculation)

Environment and development tools - Optional

2015-06-08T11:39:20Z

Rdoursenaud: Added tuning configuration for alternative webservers (Nginx)

{{TemplateDocDev}}
This page describe all optional components you can install to support more technologies for development around Dolibarr.
They are not required to develop Dolibarr nor modules but may be usefull for specific development.

== If you manage other projects with SVN ==
* Install Eclipse plugin for SVN: SubClipse
For this, use the '''Find And Install process''' and add the SVN update URL:

http://subclipse.tigris.org/install.html

or
* Install Eclispe plugin for SVN: Subversive

http://community.polarion.com/projects/subversive/download/eclipse/2.0/ganymede-site/ - [required] Subversive SVN Connectors

http://community.polarion.com/projects/subversive/download/integrations/ganymede-site/ - [optional] Subversive Integrations

== If you want to make Perl scripts ==
* Install the Eclipse plugin for Perl: EPIC
For this, use the '''Find And Install process''' and add the update URL: http://e-p-i-c.sourceforge.net/updates

== If you want to make Python scripts ==
* Install the Eclipse plugin for Python: PyDev
For this, use the '''Find And Install process''' and add the update URL: http://pydev.org/updates

== If you are using Windows ==

* Notepad++ (for those which can't stand java or using a computer too old for Eclipse).

* WinMerge (to compare files and directories)

* CygWin (to have the "patch" command)

== To make FirePHP Debug ==
If using Ubuntu, you can also complete PHP with FirePHP module by running
<source lang="php">
pear channel-discover pear.firephp.org
pear install firephp/FirePHPCore
</source>

== If you want to make step by step debugging or tunning (XDebug) ==
* To add global tuning information, from dolibarr 3.8, for pages on your browser javascript console log, add environment variable MAIN_SHOW_TUNING_INFO to 1 on your webserver.
For Apache, just add the following line into your apache.conf:
<source lang="ini">
SetEnv MAIN_SHOW_TUNING_INFO 1
</source>
For Nginx, add the following line to your php location:
<source lang="ini">
fastcgi_param MAIN_SHOW_TUNING_INFO true;
</source>
The variable name is DOL_TUNING for versions of Dolibarr < 3.8.

* Install XDebug:
=== [[File:Logo_windows.png|24px]] In Windows ===
* Download dll file '''php_debug_xxx.dll''' on http://www.xdebug.org and store it in directory /ext of php. Then enable plugin.

* Modify php.ini file to add parameters:
<source lang="ini">
[xdebug]
xdebug.remote_enable=on
xdebug.remote_handle=dbgp
xdebug.remote_host=localhost
xdebug.remote_port=9000
xdebug.show_local_vars=off
xdebug.profiler_output_dir=c:/temp
xdebug.profiler_append=0
xdebug.profiler_enable=0
xdebug.profiler_enable_trigger=1
</source>

=== [[File:Logo_ubuntu.png|24px]] In Ubuntu / Linux ===
* Install package '''php-xdebug''':
<source lang="bash">
sudo apt-get install php5-xdebug
</source>

* Modify xdebug.ini to add parameters after the line zend_extension=xxx (or similar):
<source lang="ini">
; With xdebug 2.1 and more
xdebug.remote_enable=on
xdebug.remote_handle=dbgp
xdebug.remote_host=localhost
xdebug.remote_port=9000
xdebug.show_local_vars=off
xdebug.profiler_output_dir=/var/tmp
xdebug.profiler_enable=0
xdebug.profiler_enable_trigger=1
; Add also this with xdebug 2.2 and more
xdebug.show_mem_delta=1
xdebug.trace_output_dir=/var/tmp
xdebug.auto_trace=0
xdebug.trace_enable_trigger=1
</source>

=== [[File:Eclipsephp.jpg|24px]] Eclipse configuration ===
* Open Eclipse. In Window->Preferences->General->Web Browser, select external web browser, and set it to Default system web browser.

* Go into the debug section, by Window->Preferences->PHP->Debug, and set the PHP Debugger option to XDebug (by default this is set to the Zend Debugger). Note the chekbox “Break at first line” in this page as well – you can change this later on, as required.

* After you’ve applied your changes, go into the PHP Debug prespective, and go to menu Debug Configurations… Here, make sure the Server Debugger is set to XDebug, and that the PHP server points to http://localhost/ or an appropriate server location. The file section should point to the file to be debugged, relative to your workspace, the relative path maybe something /dolibarr/htdocs/index.php.

* Check the URL section to see whether it points to the correct location – if not, make sure you uncheck the “Auto-Generate” check box, and enter in the correct location. Apply the changes and close the dialog box.

* You should now be ready to debug Dolibarr. Click on Run->Debug or F11 to enable debugging, Eclipse should switch to the Debug View, and the page should start loading in your external browser. If “Break at First Line” checkbox was checked previously, then the program would have “stopped” at the first line. You can step into or step over subsequent lines using the controls on your top left corner. Alternatively, you can place breakpoints at various locations and stop code execution there as well.

Then to analyze files generated by XDebug profiling, you must call the page by adding parameter XDEBUG_PROFILE=1 to generate the file and then install KCacheGrind (Linux) or WinCacheGrind (Windows) to analyze them.

== To develop or use Quality controls (PHPUnit, PHPCodeSniffer, PHPCpd, PHPDepends) ==
=== From Eclipse ===
You can also optionnally install The PHP Tools integration (PTI) using the Eclipse plugin installer menu with this following URL:

http://www.phpsrc.org/eclipse/pti/

If you do so, menu to launch tools tests are available in your Eclipse menu.

Modify your Eclipse setup (Windows-Preferences-PHPTools-PHPCodeSniffer) to add a new directory standard found into''' dev/codesniffer'''.

Modify your Eclipse setup (Windows-Preferences-PHPTools-PHPUnit) like on screen shot (click to zoom):

[[File:Eclipse setup PHPUnit.png|100px]]

If you did not install PTI, you must install and run PHPUnit and other quality tools manually from command line.

=== From Command Line ===
==== Instal PHPUnit ====
* Download a release archive from http://pear.phpunit.de/get/ and extract it to a directory that is listed in the include_path of your php.ini configuration file.
* Prepare the phpunit script:
** For Linux: Rename the phpunit.php script to phpunit and replace the @php_bin@ string in it with the path to your PHP command-line interpreter (usually /usr/bin/php).
** For Windows: Replace the @php_bin@ string in file phpunit.bat with the path of your PHP command-line interpreter and @bin_dir@ string with the path of the PHPunit directory.
** Edit your Path to inclulde PHPunit directory
** Make script runnable (chmod +x phpunit on Linux).
* Prepare the PHPUnit/Util/PHP.php script:
** Replace the @php_bin@ string if it exists in file it with the path to your PHP command-line interpreter (usually /usr/bin/php).
* Module xdebug can also be required if you plan to make reporting of test code covering.

==== Execute PHPUnit tests or generate code coverage reports ====
* Go into directory '''/test''' of sources. Read file '''README''' to know the process to execute a unit test campaign.

==== Install other quality tools (phpcs, phpcd, phpdepends) ====
* Take a look at tools documentation (PHPCodeSniffer, PHPPcd, PHPDepends). For example, to install or upgrade PHPCodeSniffer
<source lang="bash">
sudo pear upgrade PHP_CodeSniffer
</source>

== To develop or use Selenium tests ==
=== From Firefox ===
==== Install plugin for Firefox Selenium IDE ====
* Download file of plugin "Selenium IDE" for Firefox.
* Add it into firefox in menu Tools - Complementary modules.

==== Execute Selenium tests ====
* Go into menu Tools - Selinum IDE of Firefox.
* Open xml file of the suite tests.
* Execute the test.

== To build Doxygen documentation ==
* Install Doxygen available for download at http://www.doxygen.org (or install package doxygen with Ubuntu).
* Install Eclipse plugin by adding source http://download.gna.org/eclox/update/ into your Eclipse update setup. Then setup your Eclipse (Window-Preferences-Doxygen) to define path to Doxygen tool.

== To develop Android component ==
* Download android SDK and unzip it: http://developer.android.com/sdk
* Install Android Eclipse plugin:
** Start Eclipse, then select Help > Install New Software.
** Click Add, in the top-right corner.
** In the Add Repository dialog that appears, enter "ADT Plugin" for the Name and the following URL for the Location: https://dl-ssl.google.com/android/eclipse/
** If you have trouble acquiring the plugin, try using "http" in the Location URL, instead of "https" (https is preferred for security reasons).
** In the Available Software dialog, select the checkbox next to Developer Tools and click Next.
** In the next window, you'll see a list of the tools to be downloaded. Click Next.
** Read and accept the license agreements, then click Finish.
** If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.
** When the installation completes, restart Eclipse.

Setup Other

2015-05-21T09:16:37Z

Rdoursenaud: Add a warning to MAIN_USE_JQUERY_MULTISELECT to avoid https://github.com/Dolibarr/dolibarr/issues/2860

[[Category:Admin]]
{{TemplateDocUser}}

'''Help about screen:''' Other setup

'''Menu path:''' Home -> Setup -> Other

= Goal =
This page is built to add/edit new parameters without a dedicated page to edit them. In most cases, it is parameters for your own development, external modules, or hidden features.

For a standard usage of Dolibarr, this screen must be kept empty and not be used.

= List of known hidden options =
Some options are not visible in the interface (often because they are deprecated or beta features). In most cases you do not need these functions and their use may make the application unstable.

To enable them you have to define a constant to 1 in '''Home -> Setup -> Other setup''':

== Global options ==
* MAIN_APPLICATION_TITLE => This will change the title of software (that appears on the login page by default). Warning, changing this may make Dolibarr version detection fails by smartphone applications like [[Application Android - DoliDroid]]

* MAIN_AUTOFILL_DATE => If this constant is defined (to something else than 0), the date of invoice, proposal, order or payment are filled with current date. It is highly recommended to NOT ENABLE this feature. This create a lot of input errors with no data not validated by users. This lead in bad values saved in database giving headaches when you have to do your accountancy reports ! However some users want it, so we provide it.

* MAIN_DISABLE_FULL_SCANLIST => Constant to define to disable complete scan of tables to know the total amount of element to allow the pagination to show total number of pages. To activate on systems with a very important number of data (Tables with more than 500 000 records).

* MAIN_FIRST_TO_UPPER => Dolibarr add upper case to thirdparties, contacts or members names if not done. Warning, with some languages (whose words with uppercase are not same words, or pagecode does not always have an uppercase, like cyrillic languages), this feature may alter your data.

* MAIN_LOGTOHTML => If this constants is defined, it is possible to have logs inside pages by adding the parameter &logtohtml=1 into URL.

* MAIN_USE_HOURMIN_IN_DATE_RANGE => On all entities lines (invoice, order, contract...), it is possible to add hour and minutes with date on fields "date start" and "date end".

* MAIN_REMOVE_INSTALL_WARNING => Remove all security warning that appears to administrator users if URL /install is public. You shoud solve the problem if warning occurs instead of removing this warning. For this, put a file called install.lock into Dolibarr root directory. This will remove warning but also make the page /install not possible to use to protect your installation.

* MAIN_OPTIMIZE_SPEED => Use some speed enhancements. See page [[Increase_Performance]] for more information.

* MAIN_OVERWRITE_TRANS_xx_YY => You can use this to change value of a translation key for language xx_YY (ie: en_US) without editing language files. For example: "TranslationKey1:New value1,TranslationKey2:New value 2". Note that using this option slow down seriously your instance. If you can, it is better to edit directly the language files into htdocs/lang/xx_YY.

* MAIN_REPEATCONTACTONEACHTAB => If added and set to 1, this add contacts on all tabs, not only main tab.

* MAIN_DISABLE_JQUERY_JNOTIFY => Disable usage of JNotify to show confirm or error messages

* MAIN_USE_JQUERY_JEDITABLE => Allow to update from screnn, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this features, because, it overpass some business actions (updates onother data that should be done consitently) and ignore business controls on data you saved. So this feature breaks consitency of data and stability of software.

* MAIN_USE_JQUERY_LAYOUT => Allow hidding the left menu

* MAIN_USE_JQUERY_MULTISELECT => Allow to use Ajax when a choice that require multiselect is used (for the moment only external modules uses select box with multiselect values). Set the value to the jQuery plugin name to use (multiselect, multiple-select, select2…). Setting it to any other value will result in unwanted side-effects and/or bugs.

* MAIN_HELPCENTER_LINKTOUSE => Define a target link "I need help" onto logon page

* MAIN_MODULES_FOR_EXTERNAL => Limit available modules for external users. By defaut value is 'facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda'

* MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE => Avoid Custom code and country of origin to be set as product description when added to Propal/Order/Invoice

* MAIN_SHOW_TUNING_INFO => Add tuning information into javascript console. Better when xdebug is enabled.

* MAIN_DOL_SCRIPTS_ROOT => Define directory who contains 'scripts' directory (e.g /var/www/dolibarr)

* MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING => A warning saying setup of modules is not complete is shown if number of enabled modules is lower or equal than this value (1 if not defined)

* MAIN_ADD_SALE_REP_SIGNATURE_IN_NOTE => Add signature of first sale representative into documents (at end of public notes).

* MAIN_DISABLE_AJAX_COMBOX => If you have a large amount of thirdparty or product, you can disable the autocomplete feature on thirdparties list by setting constant MAIN_DISABLE_AJAX_COMBOX to 1 into Home-Setup-Other (with Dolibarr v3.6.0+).

* MAIN_USE_CACHE_MANIFEST => Add an HTML5 cache manifest to the page

* MAIN_FORCELANGDIR => relative path of the directory holding your custom langs folder.

* MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS => allow to define a default VAT rate

* MAIN_HTML_TITLE => can be used to control how html title is formated. If value contains key 'noapp', application name will not be output. If value contains 'thirdpartynameonly', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: 'noapp;thirdpartynameonly'

* MAIN_MENU_HIDE_UNAUTHORIZED => Hide menu if user not autorized rather than just grey them

== Email and SMS ==
* MAIN_MAIL_DEBUG => Write content with header of last mail into file dolibarr_mail.log into directory dolibarr_main_data_root.

* MAIN_SMS_DEBUG => Write content of SMS sent into file dolibarr_sms.log into directory dolibarr_main_data_root.

* MAIN_MAIL_ALLOW_SENDMAIL_F => On Linux or BSD system, PHP email function use the command sendmail local to server. In some cases, the sender email must be provided on command line of sendmail with option -f. This option is here to ask Dolibarr to call the function '''mail''' of PHP by adding value for the option -f. Note that in most cases, even with sendmail, sender email is correctly managed as it is added in the email technical header. This option is here only for rare setup of sendmail that ask the '''-f''' option to be mandatory or for sendmail setup that does not use by default the Return-path of header email to define the sender (with this option, the return-path will be provided also on command line and not lost by sendmail).

* MAIN_MAIL_SENDMAIL_FORCE_BA => On Lunix or BSD system, PHP email function use the command sendmail local to server. In some case, we want to recipient to be provided to sendmail into the email content instead of its command line parameter. For this we must add the '''-ba''' parameter to sendmail. This option ask PHP to provide this parameter when sending a mail. Note that another solution is to edit the '''mail.force_extra_parameters=-ba''' into '''php.ini''' file.

* MAIN_MAIL_NO_FULL_EMAIL => Recipient email and sender are cleaned to be on form "<email>" instead of "Name <email>". This might solve problem of compatibility with very old mailers.

* MAIN_FIX_FOR_BUGGED_MTA => Some MTA agent are bugged and add some CR chars each time they saw a LF. Because Dolibarr emails are forged to be already cleaned, if MTA agent do that, you will send an email with two CR chars. This may result in having recipient not able to read your email. To fix this, add this constant to 1. Dolibarr will then create an email that is not RFC compliant but because the MTA agent is bugged, the email will be modified and become correct during sending, solving the problem of bad email received. Add this constant if your recipient experience problems when opening email for example users using webmail of orange.fr or hotmail.com

* MAIN_MAIL_DO_NOT_USE_SIGN => Do not add user signature at end of suggested predefined email

* MAIL_FORCE_DELIVERY_RECEIPT_INVOICE, MAIL_FORCE_DELIVERY_RECEIPT_ORDER, MAIL_FORCE_DELIVERY_RECEIPT_PROPAL => Force delivery receipt to "Yes" onto form to send email.

* MAIN_EMAIL_USECCC => Show field BCC into email forms.

* MAIN_MAIL_AUTOCOPY_PROPOSAL_TO, MAIN_MAIL_AUTOCOPY_ORDER_TO, MAIN_MAIL_AUTOCOPY_INVOICE_TO => Send a BCC to the recipients when sending email for proposal, order or invoice. If option MAIN_EMAIL_USECCC is also set, you will see recipient email of BCC into email form on same line used to enter BCC.

* MAIN_EMAIL_ADD_TRACK_ID => When value is 1: The record "Message-id" added into smtp header includes a tracking id to define where the email was sent from.
When value is 2: you send an email from thirdparty card, the sender email is completed with the email source tracking string "+thiXXX" on email (your email will be sent with the "From" that is myname+thi123@mycompany.com). So when user receiving email will make "Answer", email will be sent to myname@mycompany.com but with the tracking id included, allowing you to know on wich thirdparty email exchange is related to.

== Third parties module ==
* SOCIETE_DISABLE_CUSTOMERS => Remove all menu and features related to customers
* SOCIETE_DISABLE_PROSPECTS => Remove all menu and features related to prospects
* SOCIETE_DISABLE_STATE => Do not use field "state/province"
* THIRDPARTY_NOTCUSTOMERPROSPECT_BY_DEFAULT => Do not set status "Customer/Prospect" to "on" when creating a new thirdparty from menu "New thirdparty".
* THIRDPARTY_NOTSUPPLIER_BY_DEFAULT => Do not set status "Supplier" to "on" when creating a new thirdparty from menu "New thirdparty".
* MAIN_THIRPARTY_CREATION_INDIVIDUAL => Default Thirparty create are individual

== Proposals module ==
* PROPAL_CLONE_ON_CREATE_PAGE => On the create proposal page, ask if we want to create the proposal by cloning an already existing one. You should use instead the "Clone" button available on existing proposals.
* MAIN_PROPAL_CHOOSE_ODT_DOCUMENT => On setup page, you'll be able to select which ODT document to use when close or cancel proposals.
* <s>MAIN_GENERATE_DOCUMENTS_WITH_PICTURE</s> MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Add picture of product (the first one found if there is several) into the generated PDF of proposals. Note that using this reduce available width for product description.
* WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES => Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.

== Invoice module ==
* FACTURE_SHOW_SEND_REMINDER => Show link "Send reminder by mail", same feature than "Send by mail" (obsolete feature).
* INVOICE_CAN_ALWAYS_BE_REMOVED => Allow to always delete invoices (even if invoice is not last one).
* INVOICE_CAN_NEVER_BE_REMOVED => Never allow to delete invoices (except draft invoices).
* INVOICE_POSITIVE_CREDIT_NOTE => All amounts on PDF credit notes are positive.
* FACTURE_CHANGE_THIRDPARTY => Allow to change the third party in the draft invoices. If a discount was set from the original thirdparty, then discount remain, making data not coherent.
* FACTURE_USE_PROFORMAT => Enable PROFORMAT invoices type.
* FACTURE_DEPOSITS_ARE_JUST_PAYMENTS => Treats deposit invoices as a special case. Deposit invoices don't get counted on turnover. They are then applied as a payment, like a discount, on the final invoice.
* FACTURE_SENDBYEMAIL_FOR_ALL_STATUS => Can send invoice by email to customer even if invoice has status "draft".
* MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT => Disable VAT on genrated documents. like for an association. (it's work with crabe template)
* FAC_AUTO_FILLJS => Display a button to autofill the payment amount for each invoice on the payment creation page

== Order module ==
* COMMANDE_REQUIRE_SOURCE => Make the input field "Source of order" mandatory.
* COMMANDE_VALID_AFTER_CLOSE_PROPAL => When an order is created on a proposal close, the order is directly defined with status "Validated".

== Export module ==
* EXPORT_CSV_SEPARATOR_TO_USE => String value to use as separator to delimit fields int exported files (by default Dolibarr use ","). Example: EXPORT_CSV_SEPARATOR_TO_USE=;
* EXPORT_CSV_FORCE_CHARSET => Choose the charset of file built by CSV export. By default: UTF-8. Example: EXPORT_CSV_FORCE_CHARSET=ISO-8859-1

== Agenda module ==
* AGENDA_MAX_EVENTS_DAY_VIEW => Define the maximum number of visible entries for each day in agenda. Default value is 3. Value 0 means no limit.
* AGENDA_USE_EVENT_TYPE => Add a mandatory field "Type" when creating an event (deprecated).
* AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS => To automatically set end date of event to start date + delta on event creation page.

== Products module ==
* PRODUCT_ADD_TYPE_IN_DOCUMENTS => Add text "Product" or "Service" at beginning of details lines on built PDF documents.
* PRODUCT_SHOW_WHEN_CREATE => Old option no more supported (create problems) to be able to add lines of product during first step of element creation.
* PRODUCT_DONOTSEARCH_ANYWHERE => When Ajax search is enabled, search is done on criteria anywhere in label of product. By adding this option, search is done only on start of label. This is really faster when you have a huge number of products.
* PRODUIT_DESC_IN_LIST => Show long description of product/service into lists.
* PRODUIT_MULTIPRICES_LABELx (where x = 1,2,...) => When option mode to set prices are PRODUIT_MULTIPRICES (n different prices per product according to a customer level), this option will force a label for the level x. Value must be a key. If the key is found into translation files, it will be replaced by the translated value.

== Services module ==
* SERVICE_ARE_ECOMMERCE_200238EC => If this option is enabled, services are processed like eServices according to directove of EU Council Directive 2002/38/EC (http://ec.europa.eu/taxation_customs/taxation/vat/traders/e-commerce/article_1610_en.htm). Default VAT rate are based on buying country instead of selling country for BtoC sells.

== Stocks ==
* STOCK_SUPPORTS_SERVICES => Services are also increased/decreased into stocks.

== Point of Sale ==
* CASHDESK_SHOW_KEYPAD => Show a mouse key pad into Point Of Sale.

== Contracts ==
* CONTRACT_SUPPORT_PRODUCTS => Products are also suggested into module contract.

== Projects module ==
* PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS => Enable linking a project to any supplier even when using the third party link feature. Note: Set to 1 by default from 3.7.
* PROJECT_TIME_ON_ALL_TASKS_MY_PROJECTS => Can add time spent on tasks, even if i am not assigned to task (however, task must be a project i am a contact).
* PROJECT_SHOW_REF_INTO_LISTS => Add column with project ref into list (with 3.7 list of supplier invoices only, will be expanded to other lists)
* PROJECT_HIDE_UNSELECTABLES => Hide into select list, all project that we can't select (closed or draft)
* PROJECT_HIDE_TASKS => Hide tasks. For user using project only as an analytics key and not using tasks.
* PROJECT_LIST_SHOW_STARTDATE => Shows start date of projects in project lists.

== Foundation module ==
* MEMBER_URL_REDIRECT_SUBSCRIPTION => Link called and shown when a member account is autocreated in member module by a guest user.
* MEMBER_EXT_URL_SUBSCRIPTION_INFO => Link of external page pointed by the "Show here" link to add in fron off payment cell form into the page to make online subscription.

== Interventions module ==
* FICHINTER_CLASSIFY_BILLED => Allow to classify an intervention card as "Billed". This add also trigger FICHINTER_CLASSIFY_BILLED into list of possible automatic event into agenda.
* FICHINTER_DISABLE_DETAILS => Disable entry of details line on intervention. Can validate with no line.

== Suppliers module ==
* FOURN_PRODUCT_AVAILABILITY => On the Suppliers price page of the products, active the supplier product availability. This is duplicate feature with delivery_delay introduced with 3.8.
* SUPPLIER_ORDER_AUTOADD_USER_CONTACT => Add user approving supplier order as a contact automatically.
* SUPPLIER_ORDER_USE_DISPATCH_STATUS => Add a status on each dispatch order line
* SUPPLIER_ORDER_NO_DIRECT_APPROVE => No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

== PDF options ==
* MAIN_DISABLE_FORCE_SAVEAS => If your browser ask always to save downloaded files on disk (like PDF), try to add this option. File might appears directly into your browser.

* MAIN_DISABLE_PDF_COMPRESSION => Disable PDF compression.

* MAIN_INVERT_SENDER_RECIPIENT => Invert sender and recipient in some PDF.

* MAIN_DISABLE_PDF_AUTOUPDATE => Disable automatic generation of PDF each time we add/update/delete a product line (we can still build document by clicking on "Generate"). This option may increase interface speed on server with low CPU.

* MAIN_USE_BACKGROUND_ON_PDF => Define this constant with short name of an image (example "myimage.jpg") that must be saved into directory "documents/mycompany/logos". This will add this background image into your generated PDF files. Warning: This option make TCPDF library beeing crazy sometime and content on image disappeared !

* MAIN_ADD_PDF_BACKGROUND => Define this constant with short name of a PDF file (example "mypdf.pdf") that must be saved into directory "documents/mycompany". This will add PDF as a background of some of your generated PDF files (proposals,invoices,orders). If you need to concat PDF, see instead [[Module Concat PDF]].

* MAIN_PDF_FORCE_FONT => To ignore font defined into language file and force usage of a particular font. For example "DejaVuSans".

* MAIN_PDF_MARGIN_LEFT, MAIN_PDF_MARGIN_RIGHT, MAIN_PDF_MARGIN_TOP, MAIN_PDF_MARGIN_BOTTOM => To force the margins (mm) of PDF documents (10 is default).

* MAIN_PDF_FREETEXT_HEIGHT => Change height of space reserved to output the free text.

* MAIN_PDF_TITLE_BACKGROUND_COLOR => Can define a background color onto title line. Example: '220,220,200'

* MAIN_USE_COMPANY_NAME_OF_CONTACT => Use contact name and information rather than company

* MAIN_ODT_AS_PDF => Activate PDF conversion from ODT document. If value is 'jodconverter', java and jodconverter command line tool must be available. If value is '/pathto/jodconverter.jar', then java and the jodconvertar jar must exists. soffice must also be available. MAIN_DOL_SCRIPTS_ROOT Must also be defined to path where the "scripts" directory is stored (for example /var/www/mydolibarr).

* MAIN_ODT_AS_PDF_DEL_SOURCE => For ODT generation. If set then initial behaviour is conserved, odt file is removed when generate pdf. Disabled by default

* MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Include first image of product into line of generated PDF proposal.

* MAIN_GENERATE_INVOICES_WITH_PICTURE => Include first image of product into line of generated PDF invoice.

* MAIN_DOCUMENTS_WITH_PICTURE_WIDTH => Can change size of picture when hidden option MAIN_GENERATE_PROPOSALS_WITH_PICTURE is used. By default value is 20.

* PDF_SHOW_PROJECT => Show project onto PDF (supported on supplier order only for the moment)

== WYSIWYG editor ==

* FCKEDITOR_ENABLE_DETAILS_FULL => Can cut and paste external images (hosted on external server) into description of proposal, orders or invoices. WARNING: PDF generation is not guaranted with this. Also if the image is removed or renamed by the image hoster, your proposal, order or invoice will be broken.

Setup Other

2015-05-07T09:00:48Z

Rdoursenaud: Reverted edits by Rdoursenaud (talk) to last revision by Eldy

[[Category:Admin]]
{{TemplateDocUser}}

'''Help about screen:''' Other setup

'''Menu path:''' Home -> Setup -> Other

= Goal =
This page is built to add/edit new parameters without a dedicated page to edit them. In most cases, it is parameters for your own development, external modules, or hidden features.

For a standard usage of Dolibarr, this screen must be kept empty and not be used.

= List of known hidden options =
Some options are not visible in the interface (often because they are deprecated or beta features). In most cases you do not need these functions and their use may make the application unstable.

To enable them you have to define a constant to 1 in '''Home -> Setup -> Other setup''':

== Global options ==
* MAIN_APPLICATION_TITLE => This will change the title of software (that appears on the login page by default). Warning, changing this may make Dolibarr version detection fails by smartphone applications like [[Application Android - DoliDroid]]

* MAIN_AUTOFILL_DATE => If this constant is defined (to something else than 0), the date of invoice, proposal, order or payment are filled with current date. It is highly recommended to NOT ENABLE this feature. This create a lot of input errors with no data not validated by users. This lead in bad values saved in database giving headaches when you have to do your accountancy reports ! However some users want it, so we provide it.

* MAIN_DISABLE_FULL_SCANLIST => Constant to define to disable complete scan of tables to know the total amount of element to allow the pagination to show total number of pages. To activate on systems with a very important number of data (Tables with more than 500 000 records).

* MAIN_FIRST_TO_UPPER => Dolibarr add upper case to thirdparties, contacts or members names if not done. Warning, with some languages (whose words with uppercase are not same words, or pagecode does not always have an uppercase, like cyrillic languages), this feature may alter your data.

* MAIN_LOGTOHTML => If this constants is defined, it is possible to have logs inside pages by adding the parameter &logtohtml=1 into URL.

* MAIN_USE_HOURMIN_IN_DATE_RANGE => On all entities lines (invoice, order, contract...), it is possible to add hour and minutes with date on fields "date start" and "date end".

* MAIN_REMOVE_INSTALL_WARNING => Remove all security warning that appears to administrator users if URL /install is public. You shoud solve the problem if warning occurs instead of removing this warning. For this, put a file called install.lock into Dolibarr root directory. This will remove warning but also make the page /install not possible to use to protect your installation.

* MAIN_OPTIMIZE_SPEED => Use some speed enhancements. See page [[Increase_Performance]] for more information.

* MAIN_OVERWRITE_TRANS_xx_YY => You can use this to change value of a translation key for language xx_YY (ie: en_US) without editing language files. For example: "TranslationKey1:New value1,TranslationKey2:New value 2". Note that using this option slow down seriously your instance. If you can, it is better to edit directly the language files into htdocs/lang/xx_YY.

* MAIN_REPEATCONTACTONEACHTAB => If added and set to 1, this add contacts on all tabs, not only main tab.

* MAIN_DISABLE_JQUERY_JNOTIFY => Disable usage of JNotify to show confirm or error messages

* MAIN_USE_JQUERY_JEDITABLE => Allow to update from screnn, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this features, because, it overpass some business actions (updates onother data that should be done consitently) and ignore business controls on data you saved. So this feature breaks consitency of data and stability of software.

* MAIN_USE_JQUERY_LAYOUT => Allow hidding the left menu

* MAIN_USE_JQUERY_MULTISELECT => Allow to use Ajax when a choice that require multiselect is used (for the moment only external modules uses select box with multiselect values).

* MAIN_HELPCENTER_LINKTOUSE => Define a target link "I need help" onto logon page

* MAIN_MODULES_FOR_EXTERNAL => Limit available modules for external users. By defaut value is 'facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda'

* MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE => Avoid Custom code and country of origin to be set as product description when added to Propal/Order/Invoice

* MAIN_SHOW_TUNING_INFO => Add tuning information into javascript console. Better when xdebug is enabled.

* MAIN_DOL_SCRIPTS_ROOT => Define directory who contains 'scripts' directory (e.g /var/www/dolibarr)

* MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING => A warning saying setup of modules is not complete is shown if number of enabled modules is lower or equal than this value (1 if not defined)

* MAIN_ADD_SALE_REP_SIGNATURE_IN_NOTE => Add signature of first sale representative into documents (at end of public notes).

* MAIN_DISABLE_AJAX_COMBOX => If you have a large amount of thirdparty or product, you can disable the autocomplete feature on thirdparties list by setting constant MAIN_DISABLE_AJAX_COMBOX to 1 into Home-Setup-Other (with Dolibarr v3.6.0+).

* MAIN_USE_CACHE_MANIFEST => Add an HTML5 cache manifest to the page

* MAIN_FORCELANGDIR => relative path of the directory holding your custom langs folder.

* MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS => allow to define a default VAT rate

* MAIN_HTML_TITLE => can be used to control how html title is formated. If value contains key 'noapp', application name will not be output. If value contains 'thirdpartynameonly', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: 'noapp;thirdpartynameonly'

* MAIN_MENU_HIDE_UNAUTHORIZED => Hide menu if user not autorized rather than just grey them

== Email and SMS ==
* MAIN_MAIL_DEBUG => Write content with header of last mail into file dolibarr_mail.log into directory dolibarr_main_data_root.

* MAIN_SMS_DEBUG => Write content of SMS sent into file dolibarr_sms.log into directory dolibarr_main_data_root.

* MAIN_MAIL_ALLOW_SENDMAIL_F => On Linux or BSD system, PHP email function use the command sendmail local to server. In some cases, the sender email must be provided on command line of sendmail with option -f. This option is here to ask Dolibarr to call the function '''mail''' of PHP by adding value for the option -f. Note that in most cases, even with sendmail, sender email is correctly managed as it is added in the email technical header. This option is here only for rare setup of sendmail that ask the '''-f''' option to be mandatory or for sendmail setup that does not use by default the Return-path of header email to define the sender (with this option, the return-path will be provided also on command line and not lost by sendmail).

* MAIN_MAIL_SENDMAIL_FORCE_BA => On Lunix or BSD system, PHP email function use the command sendmail local to server. In some case, we want to recipient to be provided to sendmail into the email content instead of its command line parameter. For this we must add the '''-ba''' parameter to sendmail. This option ask PHP to provide this parameter when sending a mail. Note that another solution is to edit the '''mail.force_extra_parameters=-ba''' into '''php.ini''' file.

* MAIN_MAIL_NO_FULL_EMAIL => Recipient email and sender are cleaned to be on form "<email>" instead of "Name <email>". This might solve problem of compatibility with very old mailers.

* MAIN_FIX_FOR_BUGGED_MTA => Some MTA agent are bugged and add some CR chars each time they saw a LF. Because Dolibarr emails are forged to be already cleaned, if MTA agent do that, you will send an email with two CR chars. This may result in having recipient not able to read your email. To fix this, add this constant to 1. Dolibarr will then create an email that is not RFC compliant but because the MTA agent is bugged, the email will be modified and become correct during sending, solving the problem of bad email received. Add this constant if your recipient experience problems when opening email for example users using webmail of orange.fr or hotmail.com

* MAIN_MAIL_DO_NOT_USE_SIGN => Do not add user signature at end of suggested predefined email

* MAIL_FORCE_DELIVERY_RECEIPT_INVOICE, MAIL_FORCE_DELIVERY_RECEIPT_ORDER, MAIL_FORCE_DELIVERY_RECEIPT_PROPAL => Force delivery receipt to "Yes" onto form to send email.

* MAIN_EMAIL_USECCC => Show field BCC into email forms.

* MAIN_MAIL_AUTOCOPY_PROPOSAL_TO, MAIN_MAIL_AUTOCOPY_ORDER_TO, MAIN_MAIL_AUTOCOPY_INVOICE_TO => Send a BCC to the recipients when sending email for proposal, order or invoice. If option MAIN_EMAIL_USECCC is also set, you will see recipient email of BCC into email form on same line used to enter BCC.

* MAIN_EMAIL_ADD_TRACK_ID => When value is 1: The record "Message-id" added into smtp header includes a tracking id to define where the email was sent from.
When value is 2: you send an email from thirdparty card, the sender email is completed with the email source tracking string "+thiXXX" on email (your email will be sent with the "From" that is myname+thi123@mycompany.com). So when user receiving email will make "Answer", email will be sent to myname@mycompany.com but with the tracking id included, allowing you to know on wich thirdparty email exchange is related to.

== Third parties module ==
* SOCIETE_DISABLE_CUSTOMERS => Remove all menu and features related to customers
* SOCIETE_DISABLE_PROSPECTS => Remove all menu and features related to prospects
* SOCIETE_DISABLE_STATE => Do not use field "state/province"
* MAIN_THIRPARTY_CREATION_INDIVIDUAL => Default Thirparty create are individual

== Proposals module ==
* PROPAL_CLONE_ON_CREATE_PAGE => On the create proposal page, ask if we want to create the proposal by cloning an already existing one. You should use instead the "Clone" button available on existing proposals.
* MAIN_PROPAL_CHOOSE_ODT_DOCUMENT => On setup page, you'll be able to select which ODT document to use when close or cancel proposals.
* <s>MAIN_GENERATE_DOCUMENTS_WITH_PICTURE</s> MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Add picture of product (the first one found if there is several) into the generated PDF of proposals. Note that using this reduce available width for product description.
* WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES => Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.

== Invoice module ==
* FACTURE_SHOW_SEND_REMINDER => Show link "Send reminder by mail", same feature than "Send by mail" (obsolete feature).
* INVOICE_CAN_ALWAYS_BE_REMOVED => Allow to always delete invoices (even if invoice is not last one).
* INVOICE_CAN_NEVER_BE_REMOVED => Never allow to delete invoices (except draft invoices).
* INVOICE_POSITIVE_CREDIT_NOTE => All amounts on PDF credit notes are positive.
* FACTURE_CHANGE_THIRDPARTY => Allow to change the third party in the draft invoices. If a discount was set from the original thirdparty, then discount remain, making data not coherent.
* FACTURE_USE_PROFORMAT => Enable PROFORMAT invoices type.
* FACTURE_DEPOSITS_ARE_JUST_PAYMENTS => Treats deposit invoices as a special case. Deposit invoices don't get counted on turnover. They are then applied as a payment, like a discount, on the final invoice.
* FACTURE_SENDBYEMAIL_FOR_ALL_STATUS => Can send invoice by email to customer even if invoice has status "draft".
* MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT => Disable VAT on genrated documents. like for an association. (it's work with crabe template)
* FAC_AUTO_FILLJS => Display a button to autofill the payment amount for each invoice on the payment creation page

== Order module ==
* COMMANDE_REQUIRE_SOURCE => Make the input field "Source of order" mandatory.
* COMMANDE_VALID_AFTER_CLOSE_PROPAL => When an order is created on a proposal close, the order is directly defined with status "Validated".

== Export module ==
* EXPORT_CSV_SEPARATOR_TO_USE => String value to use as separator to delimit fields int exported files (by default Dolibarr use ","). Example: EXPORT_CSV_SEPARATOR_TO_USE=;
* EXPORT_CSV_FORCE_CHARSET => Choose the charset of file built by CSV export. By default: UTF-8. Example: EXPORT_CSV_FORCE_CHARSET=ISO-8859-1

== Agenda module ==
* AGENDA_MAX_EVENTS_DAY_VIEW => Define the maximum number of visible entries for each day in agenda. Default value is 3. Value 0 means no limit.
* AGENDA_USE_EVENT_TYPE => Add a mandatory field "Type" when creating an event (deprecated).
* AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS => To automatically set end date of event to start date + delta on event creation page.

== Products module ==
* PRODUCT_ADD_TYPE_IN_DOCUMENTS => Add text "Product" or "Service" at beginning of details lines on built PDF documents.
* PRODUCT_SHOW_WHEN_CREATE => Old option no more supported (create problems) to be able to add lines of product during first step of element creation.
* PRODUCT_DONOTSEARCH_ANYWHERE => When Ajax search is enabled, search is done on criteria anywhere in label of product. By adding this option, search is done only on start of label. This is really faster when you have a huge number of products.
* PRODUIT_DESC_IN_LIST => Show long description of product/service into lists.
* PRODUIT_MULTIPRICES_LABELx (where x = 1,2,...) => When option mode to set prices are PRODUIT_MULTIPRICES (n different prices per product according to a customer level), this option will force a label for the level x. Value must be a key. If the key is found into translation files, it will be replaced by the translated value.

== Services module ==
* SERVICE_ARE_ECOMMERCE_200238EC => If this option is enabled, services are processed like eServices according to directove of EU Council Directive 2002/38/EC (http://ec.europa.eu/taxation_customs/taxation/vat/traders/e-commerce/article_1610_en.htm). Default VAT rate are based on buying country instead of selling country for BtoC sells.

== Stocks ==
* STOCK_SUPPORTS_SERVICES => Services are also increased/decreased into stocks.

== Point of Sale ==
* CASHDESK_SHOW_KEYPAD => Show a mouse key pad into Point Of Sale.

== Contracts ==
* CONTRACT_SUPPORT_PRODUCTS => Products are also suggested into module contract.

== Projects module ==
* PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS => Enable linking a project to any supplier even when using the third party link feature. Note: Set to 1 by default from 3.7.
* PROJECT_TIME_ON_ALL_TASKS_MY_PROJECTS => Can add time spent on tasks, even if i am not assigned to task (however, task must be a project i am a contact).
* PROJECT_SHOW_REF_INTO_LISTS => Add column with project ref into list (with 3.7 list of supplier invoices only, will be expanded to other lists)
* PROJECT_HIDE_UNSELECTABLES => Hide into select list, all project that we can't select (closed or draft)
* PROJECT_HIDE_TASKS => Hide tasks. For user using project only as an analytics key and not using tasks.
* PROJECT_LIST_SHOW_STARTDATE => Shows start date of projects in project lists.

== Foundation module ==
* MEMBER_URL_REDIRECT_SUBSCRIPTION => Link called and shown when a member account is autocreated in member module by a guest user.
* MEMBER_EXT_URL_SUBSCRIPTION_INFO => Link of external page pointed by the "Show here" link to add in fron off payment cell form into the page to make online subscription.

== Interventions module ==
* FICHINTER_CLASSIFY_BILLED => Allow to classify an intervention card as "Billed". This add also trigger FICHINTER_CLASSIFY_BILLED into list of possible automatic event into agenda.
* FICHINTER_DISABLE_DETAILS => Disable entry of details line on intervention. Can validate with no line.

== Suppliers module ==
* FOURN_PRODUCT_AVAILABILITY => On the Suppliers price page of the products, active the supplier product availability. This is duplicate feature with delivery_delay introduced with 3.8.
* SUPPLIER_ORDER_AUTOADD_USER_CONTACT => Add user approving supplier order as a contact automatically.
* SUPPLIER_ORDER_USE_DISPATCH_STATUS => Add a status on each dispatch order line
* SUPPLIER_ORDER_NO_DIRECT_APPROVE => No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

== PDF options ==
* MAIN_DISABLE_FORCE_SAVEAS => If your browser ask always to save downloaded files on disk (like PDF), try to add this option. File might appears directly into your browser.

* MAIN_DISABLE_PDF_COMPRESSION => Disable PDF compression.

* MAIN_INVERT_SENDER_RECIPIENT => Invert sender and recipient in some PDF.

* MAIN_DISABLE_PDF_AUTOUPDATE => Disable automatic generation of PDF each time we add/update/delete a product line (we can still build document by clicking on "Generate"). This option may increase interface speed on server with low CPU.

* MAIN_USE_BACKGROUND_ON_PDF => Define this constant with short name of an image (example "myimage.jpg") that must be saved into directory "documents/mycompany/logos". This will add this background image into your generated PDF files. Warning: This option make TCPDF library beeing crazy sometime and content on image disappeared !

* MAIN_ADD_PDF_BACKGROUND => Define this constant with short name of a PDF file (example "mypdf.pdf") that must be saved into directory "documents/mycompany". This will add PDF as a background of some of your generated PDF files (proposals,invoices,orders). If you need to concat PDF, see instead [[Module Concat PDF]].

* MAIN_PDF_FORCE_FONT => To ignore font defined into language file and force usage of a particular font. For example "DejaVuSans".

* MAIN_PDF_MARGIN_LEFT, MAIN_PDF_MARGIN_RIGHT, MAIN_PDF_MARGIN_TOP, MAIN_PDF_MARGIN_BOTTOM => To force the margins (mm) of PDF documents (10 is default).

* MAIN_PDF_FREETEXT_HEIGHT => Change height of space reserved to output the free text.

* MAIN_PDF_TITLE_BACKGROUND_COLOR => Can define a background color onto title line. Example: '220,220,200'

* MAIN_USE_COMPANY_NAME_OF_CONTACT => Use contact name and information rather than company

* MAIN_ODT_AS_PDF => Activate PDF conversion from ODT document. If value is 'jodconverter', java and jodconverter command line tool must be available. If value is '/pathto/jodconverter.jar', then java and the jodconvertar jar must exists. soffice must also be available. MAIN_DOL_SCRIPTS_ROOT Must also be defined to path where the "scripts" directory is stored (for example /var/www/mydolibarr).

* MAIN_ODT_AS_PDF_DEL_SOURCE => For ODT generation. If set then initial behaviour is conserved, odt file is removed when generate pdf. Disabled by default

* MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Include first image of product into line of generated PDF proposal.

* MAIN_GENERATE_INVOICES_WITH_PICTURE => Include first image of product into line of generated PDF invoice.

* MAIN_DOCUMENTS_WITH_PICTURE_WIDTH => Can change size of picture when hidden option MAIN_GENERATE_PROPOSALS_WITH_PICTURE is used. By default value is 20.

* PDF_SHOW_PROJECT => Show project onto PDF (supported on supplier order only for the moment)

== WYSIWYG editor ==

* FCKEDITOR_ENABLE_DETAILS_FULL => Can cut and paste external images (hosted on external server) into description of proposal, orders or invoices. WARNING: PDF generation is not guaranted with this. Also if the image is removed or renamed by the image hoster, your proposal, order or invoice will be broken.

Setup Other

2015-05-07T08:47:56Z

Rdoursenaud: Added MAIN_BUGTRACK_ENABLELINK

[[Category:Admin]]
{{TemplateDocUser}}

'''Help about screen:''' Other setup

'''Menu path:''' Home -> Setup -> Other

= Goal =
This page is built to add/edit new parameters without a dedicated page to edit them. In most cases, it is parameters for your own development, external modules, or hidden features.

For a standard usage of Dolibarr, this screen must be kept empty and not be used.

= List of known hidden options =
Some options are not visible in the interface (often because they are deprecated or beta features). In most cases you do not need these functions and their use may make the application unstable.

To enable them you have to define a constant to 1 in '''Home -> Setup -> Other setup''':

== Global options ==
* MAIN_APPLICATION_TITLE => This will change the title of software (that appears on the login page by default). Warning, changing this may make Dolibarr version detection fails by smartphone applications like [[Application Android - DoliDroid]]

* MAIN_AUTOFILL_DATE => If this constant is defined (to something else than 0), the date of invoice, proposal, order or payment are filled with current date. It is highly recommended to NOT ENABLE this feature. This create a lot of input errors with no data not validated by users. This lead in bad values saved in database giving headaches when you have to do your accountancy reports ! However some users want it, so we provide it.

* MAIN_BUGTRACK_ENABLELINK => Adds a link in the left menu for direct pre-filled bug reports.

* MAIN_DISABLE_FULL_SCANLIST => Constant to define to disable complete scan of tables to know the total amount of element to allow the pagination to show total number of pages. To activate on systems with a very important number of data (Tables with more than 500 000 records).

* MAIN_FIRST_TO_UPPER => Dolibarr add upper case to thirdparties, contacts or members names if not done. Warning, with some languages (whose words with uppercase are not same words, or pagecode does not always have an uppercase, like cyrillic languages), this feature may alter your data.

* MAIN_LOGTOHTML => If this constants is defined, it is possible to have logs inside pages by adding the parameter &logtohtml=1 into URL.

* MAIN_USE_HOURMIN_IN_DATE_RANGE => On all entities lines (invoice, order, contract...), it is possible to add hour and minutes with date on fields "date start" and "date end".

* MAIN_REMOVE_INSTALL_WARNING => Remove all security warning that appears to administrator users if URL /install is public. You shoud solve the problem if warning occurs instead of removing this warning. For this, put a file called install.lock into Dolibarr root directory. This will remove warning but also make the page /install not possible to use to protect your installation.

* MAIN_OPTIMIZE_SPEED => Use some speed enhancements. See page [[Increase_Performance]] for more information.

* MAIN_OVERWRITE_TRANS_xx_YY => You can use this to change value of a translation key for language xx_YY (ie: en_US) without editing language files. For example: "TranslationKey1:New value1,TranslationKey2:New value 2". Note that using this option slow down seriously your instance. If you can, it is better to edit directly the language files into htdocs/lang/xx_YY.

* MAIN_REPEATCONTACTONEACHTAB => If added and set to 1, this add contacts on all tabs, not only main tab.

* MAIN_DISABLE_JQUERY_JNOTIFY => Disable usage of JNotify to show confirm or error messages

* MAIN_USE_JQUERY_JEDITABLE => Allow to update from screnn, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this features, because, it overpass some business actions (updates onother data that should be done consitently) and ignore business controls on data you saved. So this feature breaks consitency of data and stability of software.

* MAIN_USE_JQUERY_LAYOUT => Allow hidding the left menu

* MAIN_USE_JQUERY_MULTISELECT => Allow to use Ajax when a choice that require multiselect is used (for the moment only external modules uses select box with multiselect values).

* MAIN_HELPCENTER_LINKTOUSE => Define a target link "I need help" onto logon page

* MAIN_MODULES_FOR_EXTERNAL => Limit available modules for external users. By defaut value is 'facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda'

* MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE => Avoid Custom code and country of origin to be set as product description when added to Propal/Order/Invoice

* MAIN_SHOW_TUNING_INFO => Add tuning information into javascript console. Better when xdebug is enabled.

* MAIN_DOL_SCRIPTS_ROOT => Define directory who contains 'scripts' directory (e.g /var/www/dolibarr)

* MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING => A warning saying setup of modules is not complete is shown if number of enabled modules is lower or equal than this value (1 if not defined)

* MAIN_ADD_SALE_REP_SIGNATURE_IN_NOTE => Add signature of first sale representative into documents (at end of public notes).

* MAIN_DISABLE_AJAX_COMBOX => If you have a large amount of thirdparty or product, you can disable the autocomplete feature on thirdparties list by setting constant MAIN_DISABLE_AJAX_COMBOX to 1 into Home-Setup-Other (with Dolibarr v3.6.0+).

* MAIN_USE_CACHE_MANIFEST => Add an HTML5 cache manifest to the page

* MAIN_FORCELANGDIR => relative path of the directory holding your custom langs folder.

* MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS => allow to define a default VAT rate

* MAIN_HTML_TITLE => can be used to control how html title is formated. If value contains key 'noapp', application name will not be output. If value contains 'thirdpartynameonly', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: 'noapp;thirdpartynameonly'

* MAIN_MENU_HIDE_UNAUTHORIZED => Hide menu if user not autorized rather than just grey them

== Email and SMS ==
* MAIN_MAIL_DEBUG => Write content with header of last mail into file dolibarr_mail.log into directory dolibarr_main_data_root.

* MAIN_SMS_DEBUG => Write content of SMS sent into file dolibarr_sms.log into directory dolibarr_main_data_root.

* MAIN_MAIL_ALLOW_SENDMAIL_F => On Linux or BSD system, PHP email function use the command sendmail local to server. In some cases, the sender email must be provided on command line of sendmail with option -f. This option is here to ask Dolibarr to call the function '''mail''' of PHP by adding value for the option -f. Note that in most cases, even with sendmail, sender email is correctly managed as it is added in the email technical header. This option is here only for rare setup of sendmail that ask the '''-f''' option to be mandatory or for sendmail setup that does not use by default the Return-path of header email to define the sender (with this option, the return-path will be provided also on command line and not lost by sendmail).

* MAIN_MAIL_SENDMAIL_FORCE_BA => On Lunix or BSD system, PHP email function use the command sendmail local to server. In some case, we want to recipient to be provided to sendmail into the email content instead of its command line parameter. For this we must add the '''-ba''' parameter to sendmail. This option ask PHP to provide this parameter when sending a mail. Note that another solution is to edit the '''mail.force_extra_parameters=-ba''' into '''php.ini''' file.

* MAIN_MAIL_NO_FULL_EMAIL => Recipient email and sender are cleaned to be on form "<email>" instead of "Name <email>". This might solve problem of compatibility with very old mailers.

* MAIN_FIX_FOR_BUGGED_MTA => Some MTA agent are bugged and add some CR chars each time they saw a LF. Because Dolibarr emails are forged to be already cleaned, if MTA agent do that, you will send an email with two CR chars. This may result in having recipient not able to read your email. To fix this, add this constant to 1. Dolibarr will then create an email that is not RFC compliant but because the MTA agent is bugged, the email will be modified and become correct during sending, solving the problem of bad email received. Add this constant if your recipient experience problems when opening email for example users using webmail of orange.fr or hotmail.com

* MAIN_MAIL_DO_NOT_USE_SIGN => Do not add user signature at end of suggested predefined email

* MAIL_FORCE_DELIVERY_RECEIPT_INVOICE, MAIL_FORCE_DELIVERY_RECEIPT_ORDER, MAIL_FORCE_DELIVERY_RECEIPT_PROPAL => Force delivery receipt to "Yes" onto form to send email.

* MAIN_EMAIL_USECCC => Show field BCC into email forms.

* MAIN_MAIL_AUTOCOPY_PROPOSAL_TO, MAIN_MAIL_AUTOCOPY_ORDER_TO, MAIN_MAIL_AUTOCOPY_INVOICE_TO => Send a BCC to the recipients when sending email for proposal, order or invoice. If option MAIN_EMAIL_USECCC is also set, you will see recipient email of BCC into email form on same line used to enter BCC.

* MAIN_EMAIL_ADD_TRACK_ID => When value is 1: The record "Message-id" added into smtp header includes a tracking id to define where the email was sent from.
When value is 2: you send an email from thirdparty card, the sender email is completed with the email source tracking string "+thiXXX" on email (your email will be sent with the "From" that is myname+thi123@mycompany.com). So when user receiving email will make "Answer", email will be sent to myname@mycompany.com but with the tracking id included, allowing you to know on wich thirdparty email exchange is related to.

== Third parties module ==
* SOCIETE_DISABLE_CUSTOMERS => Remove all menu and features related to customers
* SOCIETE_DISABLE_PROSPECTS => Remove all menu and features related to prospects
* SOCIETE_DISABLE_STATE => Do not use field "state/province"
* MAIN_THIRPARTY_CREATION_INDIVIDUAL => Default Thirparty create are individual

== Proposals module ==
* PROPAL_CLONE_ON_CREATE_PAGE => On the create proposal page, ask if we want to create the proposal by cloning an already existing one. You should use instead the "Clone" button available on existing proposals.
* MAIN_PROPAL_CHOOSE_ODT_DOCUMENT => On setup page, you'll be able to select which ODT document to use when close or cancel proposals.
* <s>MAIN_GENERATE_DOCUMENTS_WITH_PICTURE</s> MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Add picture of product (the first one found if there is several) into the generated PDF of proposals. Note that using this reduce available width for product description.
* WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES => Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.

== Invoice module ==
* FACTURE_SHOW_SEND_REMINDER => Show link "Send reminder by mail", same feature than "Send by mail" (obsolete feature).
* INVOICE_CAN_ALWAYS_BE_REMOVED => Allow to always delete invoices (even if invoice is not last one).
* INVOICE_CAN_NEVER_BE_REMOVED => Never allow to delete invoices (except draft invoices).
* INVOICE_POSITIVE_CREDIT_NOTE => All amounts on PDF credit notes are positive.
* FACTURE_CHANGE_THIRDPARTY => Allow to change the third party in the draft invoices. If a discount was set from the original thirdparty, then discount remain, making data not coherent.
* FACTURE_USE_PROFORMAT => Enable PROFORMAT invoices type.
* FACTURE_DEPOSITS_ARE_JUST_PAYMENTS => Treats deposit invoices as a special case. Deposit invoices don't get counted on turnover. They are then applied as a payment, like a discount, on the final invoice.
* FACTURE_SENDBYEMAIL_FOR_ALL_STATUS => Can send invoice by email to customer even if invoice has status "draft".
* MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT => Disable VAT on genrated documents. like for an association. (it's work with crabe template)
* FAC_AUTO_FILLJS => Display a button to autofill the payment amount for each invoice on the payment creation page

== Order module ==
* COMMANDE_REQUIRE_SOURCE => Make the input field "Source of order" mandatory.
* COMMANDE_VALID_AFTER_CLOSE_PROPAL => When an order is created on a proposal close, the order is directly defined with status "Validated".

== Export module ==
* EXPORT_CSV_SEPARATOR_TO_USE => String value to use as separator to delimit fields int exported files (by default Dolibarr use ","). Example: EXPORT_CSV_SEPARATOR_TO_USE=;
* EXPORT_CSV_FORCE_CHARSET => Choose the charset of file built by CSV export. By default: UTF-8. Example: EXPORT_CSV_FORCE_CHARSET=ISO-8859-1

== Agenda module ==
* AGENDA_MAX_EVENTS_DAY_VIEW => Define the maximum number of visible entries for each day in agenda. Default value is 3. Value 0 means no limit.
* AGENDA_USE_EVENT_TYPE => Add a mandatory field "Type" when creating an event (deprecated).
* AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS => To automatically set end date of event to start date + delta on event creation page.

== Products module ==
* PRODUCT_ADD_TYPE_IN_DOCUMENTS => Add text "Product" or "Service" at beginning of details lines on built PDF documents.
* PRODUCT_SHOW_WHEN_CREATE => Old option no more supported (create problems) to be able to add lines of product during first step of element creation.
* PRODUCT_DONOTSEARCH_ANYWHERE => When Ajax search is enabled, search is done on criteria anywhere in label of product. By adding this option, search is done only on start of label. This is really faster when you have a huge number of products.
* PRODUIT_DESC_IN_LIST => Show long description of product/service into lists.
* PRODUIT_MULTIPRICES_LABELx (where x = 1,2,...) => When option mode to set prices are PRODUIT_MULTIPRICES (n different prices per product according to a customer level), this option will force a label for the level x. Value must be a key. If the key is found into translation files, it will be replaced by the translated value.

== Services module ==
* SERVICE_ARE_ECOMMERCE_200238EC => If this option is enabled, services are processed like eServices according to directove of EU Council Directive 2002/38/EC (http://ec.europa.eu/taxation_customs/taxation/vat/traders/e-commerce/article_1610_en.htm). Default VAT rate are based on buying country instead of selling country for BtoC sells.

== Stocks ==
* STOCK_SUPPORTS_SERVICES => Services are also increased/decreased into stocks.

== Point of Sale ==
* CASHDESK_SHOW_KEYPAD => Show a mouse key pad into Point Of Sale.

== Contracts ==
* CONTRACT_SUPPORT_PRODUCTS => Products are also suggested into module contract.

== Projects module ==
* PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS => Enable linking a project to any supplier even when using the third party link feature. Note: Set to 1 by default from 3.7.
* PROJECT_TIME_ON_ALL_TASKS_MY_PROJECTS => Can add time spent on tasks, even if i am not assigned to task (however, task must be a project i am a contact).
* PROJECT_SHOW_REF_INTO_LISTS => Add column with project ref into list (with 3.7 list of supplier invoices only, will be expanded to other lists)
* PROJECT_HIDE_UNSELECTABLES => Hide into select list, all project that we can't select (closed or draft)
* PROJECT_HIDE_TASKS => Hide tasks. For user using project only as an analytics key and not using tasks.
* PROJECT_LIST_SHOW_STARTDATE => Shows start date of projects in project lists.

== Foundation module ==
* MEMBER_URL_REDIRECT_SUBSCRIPTION => Link called and shown when a member account is autocreated in member module by a guest user.
* MEMBER_EXT_URL_SUBSCRIPTION_INFO => Link of external page pointed by the "Show here" link to add in fron off payment cell form into the page to make online subscription.

== Interventions module ==
* FICHINTER_CLASSIFY_BILLED => Allow to classify an intervention card as "Billed". This add also trigger FICHINTER_CLASSIFY_BILLED into list of possible automatic event into agenda.
* FICHINTER_DISABLE_DETAILS => Disable entry of details line on intervention. Can validate with no line.

== Suppliers module ==
* FOURN_PRODUCT_AVAILABILITY => On the Suppliers price page of the products, active the supplier product availability. This is duplicate feature with delivery_delay introduced with 3.8.
* SUPPLIER_ORDER_AUTOADD_USER_CONTACT => Add user approving supplier order as a contact automatically.
* SUPPLIER_ORDER_USE_DISPATCH_STATUS => Add a status on each dispatch order line
* SUPPLIER_ORDER_NO_DIRECT_APPROVE => No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

== PDF options ==
* MAIN_DISABLE_FORCE_SAVEAS => If your browser ask always to save downloaded files on disk (like PDF), try to add this option. File might appears directly into your browser.

* MAIN_DISABLE_PDF_COMPRESSION => Disable PDF compression.

* MAIN_INVERT_SENDER_RECIPIENT => Invert sender and recipient in some PDF.

* MAIN_DISABLE_PDF_AUTOUPDATE => Disable automatic generation of PDF each time we add/update/delete a product line (we can still build document by clicking on "Generate"). This option may increase interface speed on server with low CPU.

* MAIN_USE_BACKGROUND_ON_PDF => Define this constant with short name of an image (example "myimage.jpg") that must be saved into directory "documents/mycompany/logos". This will add this background image into your generated PDF files. Warning: This option make TCPDF library beeing crazy sometime and content on image disappeared !

* MAIN_ADD_PDF_BACKGROUND => Define this constant with short name of a PDF file (example "mypdf.pdf") that must be saved into directory "documents/mycompany". This will add PDF as a background of some of your generated PDF files (proposals,invoices,orders). If you need to concat PDF, see instead [[Module Concat PDF]].

* MAIN_PDF_FORCE_FONT => To ignore font defined into language file and force usage of a particular font. For example "DejaVuSans".

* MAIN_PDF_MARGIN_LEFT, MAIN_PDF_MARGIN_RIGHT, MAIN_PDF_MARGIN_TOP, MAIN_PDF_MARGIN_BOTTOM => To force the margins (mm) of PDF documents (10 is default).

* MAIN_PDF_FREETEXT_HEIGHT => Change height of space reserved to output the free text.

* MAIN_PDF_TITLE_BACKGROUND_COLOR => Can define a background color onto title line. Example: '220,220,200'

* MAIN_USE_COMPANY_NAME_OF_CONTACT => Use contact name and information rather than company

* MAIN_ODT_AS_PDF => Activate PDF conversion from ODT document. If value is 'jodconverter', java and jodconverter command line tool must be available. If value is '/pathto/jodconverter.jar', then java and the jodconvertar jar must exists. soffice must also be available. MAIN_DOL_SCRIPTS_ROOT Must also be defined to path where the "scripts" directory is stored (for example /var/www/mydolibarr).

* MAIN_ODT_AS_PDF_DEL_SOURCE => For ODT generation. If set then initial behaviour is conserved, odt file is removed when generate pdf. Disabled by default

* MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Include first image of product into line of generated PDF proposal.

* MAIN_GENERATE_INVOICES_WITH_PICTURE => Include first image of product into line of generated PDF invoice.

* MAIN_DOCUMENTS_WITH_PICTURE_WIDTH => Can change size of picture when hidden option MAIN_GENERATE_PROPOSALS_WITH_PICTURE is used. By default value is 20.

* PDF_SHOW_PROJECT => Show project onto PDF (supported on supplier order only for the moment)

== WYSIWYG editor ==

* FCKEDITOR_ENABLE_DETAILS_FULL => Can cut and paste external images (hosted on external server) into description of proposal, orders or invoices. WARNING: PDF generation is not guaranted with this. Also if the image is removed or renamed by the image hoster, your proposal, order or invoice will be broken.

DevCamp Pau April 2015 Organization

2015-04-15T08:56:31Z

Rdoursenaud: Added general assembly of the association to the planning

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Title: Dolibarr DevCamp 2015'''

The event is split in two parts this year:
* A public presentation of the project
* The usual community meeting

== Price ==
The full event is ''free'' but since space is limited, registrations are required (see below).

== Dates ==
April, 17 to 19

* Public presentation: 17 afternoon
* Community meeting: 18 to 19

=== Registrations ===
* Public presentation:
** Fill the form at goo.gl/67ZDAW before '''april, 10'''
* Community meeting:
** Here on the wiki before '''march, 28'''

== Location ==
Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France

=== Capacity ===
* Public presentation: ~100 people (friday afternoon)
* Community meeting: ~20 people

=== How to come ===
Please see directions at goo.gl/7ipG5z

== Main languages ==
* Public presentation: French
* Community meeting: English & French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc (contact@helioparc.fr)
* Lodging and Catering: GPC.solutions
* Attendees information & communication: Technopole Hélioparc
* Sponsoring management: GPC.solutions

=== Sponsors ===
* Technopole Hélioparc
* PauLLA

=== Partners ===
* La Mêlée Adour
* GRETA Béarn et Soule
* NumLab

== Lodging and catering ==

=== Hotel ===

We have negociated 42€/night/person at a nearby hotel.

Please book through us for the discounted price.

=== Food ===
Traiteur Latour

==== Saturday lunch ====

* Taboulé
* Tomates
* Rosette, chorizo
* Rôti de porc
* Fromage
* Tarte aux pommes
* Pain

==== Saturday dinner ====

* Salade de gésiers
* Axoa de porc
* Gâteau basque

==== Sunday lunch ====

* Pâtes fraîches
* Concombre
* Saucisson, jambon de Bayonne
* Rôti de bœuf
* Fromage du pays
* Dessert
* Pain

= Planning =

== Day 1 (Friday) ==

Auditorium
* 9:00: Breakfast (Organisers only)
* 10:00: Opening and free discussion
* 12:00: Lunch (Organisers and presenters only)
* 14:00: Start of general public presentations
* 14:15: Présentation du projet — Laurent Destailleur — teclib’ & NLTechno, Dolibarr Preferred Partners — Développeur principal et président de l’association
* 15:00: Retour d’expérience, organisation des Rencontres Mondiales du Logiciel Libre 2014 — Jean-François Ferry — Aternatik, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 15:45: Gérer un centre de formation — Florian Henry — Open-Concept.pro, Dolibarr Preferred Partner — Secrétaire de l’association
* 16:30: Opportunités pour le e-commerce — Jean Heimburger — Tiaris, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 17:15: Nouveautés des prochaines versions du logiciel — Laurent Destailleur
* 18:30: Apéritif and buffet supper (Invitations only)

Atelier numérique
* 21:00: Free play / code / hangout

''Next days are still in a'' '''Draft''' state ''. These will be updated as soon as we have more informations.''

== Day 2 (Saturday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 11:00: General Assembly of the Association
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Dinner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Workshop topics =

If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

Lorenzo Novaro: I propose to have a "panel" about translations and a moment to revise the english language files.

= Attendees registration =

== Public presentation ==

Please go to goo.gl/67ZDAW

== Community meeting ==

Registration is done here, on the wiki

Please copy the template below to the registered attendees section and fill it with your informations.

You'll need a wiki account. If you don't have one please ask via email at '''contact@dolibarr.org'''.

'''Registration for Dolibarr devcamp 2015 at Pau are now closed'''

(You are however still welcome the friday afternoon 17th of april, for the public presentation, free entry)

== Registration template ==

------------------------------------------
* Firstname Lastname:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:
------------------------------------------

== Community meeting registered attendees ==

------------------------------------------
[[File:Raphaël Doursenaud.png|40px]]
* Firstname Lastname: [[Raphaël Doursenaud]]
* Age: 33
* Coming from (town, country): Pau, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Home :D
* Book hotel for me (yes/no): N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: rdoursenaud@gpcsolutions.fr
------------------------------------------
------------------------------------------
[[File:Florian_Henry.png|40px]]
* Firstname Lastname: [[Florian Henry]]
* Age: 34
* Coming from (town, country): Manduel, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: florian.henry@open-concept.pro
------------------------------------------
------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname: [[Jean Heimburger]]
* Age: 54
* Coming from (town, country): Sarrebourg, France
* Arrival date and hour: 17/04/2015 Pau gar 6h40
* Departure date and hour: 19/04/2015 Pau gare 11h05
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): none
* Accommodation (Common booked hotel/self…):hotel
* Book hotel for me (yes/no):yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:jean.heimburger@tiaris.info
------------------------------------------
------------------------------------------
* Firstname Lastname: [[Jean-François Ferry]]
* Age: 34
* Coming from (town, country): Montpellier, France
* Arrival date and hour: 17, morning
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel?
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: jfefe@aternatik.fr
------------------------------------------
------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 42
* Coming from (town, country): Pessac, France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Charles-Fr Benke]]
* Age: 47
* Coming from (town, country): Lyon, France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): GOOD
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charles.fr@benke.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------
------------------------------------------
[[File:Maxime Kohlhaas.png|40px]]
* Firstname Lastname: [[Maxime Kohlhaas]]
* Age: 28
* Coming from (town, country): Valence, France
* Arrival date and hour: 16, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hotel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: maxime@atm-consulting.fr
------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: [[Lorenzo Novaro]]
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation (Train/Bus/Car/Plane): Train/Plane
* Food (Special diet, allergies, vegetarian…): nuts
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Tommaso Basilici.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 36
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation: Train/Plane
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): Transport: TBD - Hotel: TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Juanjo Menent.png|40px]]
* Firstname Lastname: [[Juanjo Menent]]
* Age: 42
* Coming from (town, country): Gandia, Spain
* Arrival date and hour: 16, 20h57
* Departure date and hour: 20, 05h53
* Transportation (Train/Bus/Car/Plane): Train
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: Hotel
* Book hotel for me: Yes
* Estimated expenses: Transport: 229.70€ - Hotel: 168€.
* Contact email: jmenent@2byte.es
------------------------------------------
[[File:Arnaud Aujon Chevallier.png|40px]]
* Firstname Lastname: [[Arnaud Aujon Chevallier]]
* Age: 26
* Coming from (town, country): Toulouse, France
* Arrival date and hour: 18, 10h00
* Departure date and hour: 18, 18h00
* Transportation (Train/Bus/Car/Plane): Car
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: self
* Book hotel for me: No
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: arnaud@intelibre.fr
------------------------------------------
* Firstname Lastname: Francis Appels
* Age: 49
* Coming from (town, country): Herselt, Belgium
* Arrival date and hour: 16, 18h00
* Departure date and hour: 19, 21h00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: francis.appels@z-application.com
------------------------------------------
[[File:Marcos García.png|40px]]
* Firstname Lastname: [[Marcos García]]
* Age: 22
* Coming from (town, country): Valladolid, Spain
* Arrival date and hour: 17, 17:00h
* Departure date and hour: 20, 06:00h
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): Lactose.
* Accommodation (Common booked hotel/self…): Airbnb
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...): 180 €
* Contact email: marcosgdf@gmail.com
------------------------------------------
* Firstname Lastname: Pierre-Yvan Aupiais
* Age: 59
* Coming from (town, country): Toulouse , France
* Arrival date and hour: 17/04/2015 , 9h00
* Departure date and hour: 18/04/2015 , 17h00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A
* Contact email:py.aupiais@val-talents.fr
-------------------------------------------
* Firstname Lastname: Estephe LORIDAN
* Age: 36 ans
* Coming from (town, country): Noisiel, France
* Arrival date and hour: Dont know yet, friday end of morning.
* Departure date and hour: Sunday evening.
* Transportation (Train/Bus/Car/Plane): Plane (my charge)
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): yes.
* Estimated expenses (ticket, parking, toll, hotel...): no expense.
* Contact email: dolibarr@estephe.me
-------------------------------------------
* Firstname Lastname: PAQUIER Bernard
* Age: 32
* Coming from (town, country): Bordeaux, France
* Arrival date and hour: 17/04 - 10h
* Departure date and hour: 19/04 -18h
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N/A
* Accommodation (Common booked hotel/self…): Self
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: contact@dolibarr-addict.com
-------------------------------------------
[[File:Bahfir Abbes.jpeg|40px]]
* Firstname Lastname: Bahfir Abbes
* Age:49
* Coming from (town, country): Oran - Algeria
* Arrival date and hour:16 April 2015
* Departure date and hour: 19-20 April 2015
* Transportation (Train/Bus/Car/Plane): Plane/Train/Bus
* Food (Special diet, allergies, vegetarian…):normal
* Accommodation (Common booked hotel/self…): -
* Book hotel for me (yes/no): -
* Estimated expenses (ticket, parking, toll, hotel...): -
* Contact email:bafbes@gmail.com
------------------------------------------
[[File:Philippe Grand.png|40px]]
* Firstname Lastname: [[Philippe Grand]]
* Age:
* Coming from (town, country):Orléans - France
* Arrival date and hour: 17/04/2015 à 10:15 à Pau, Aéroport Pyrenees (PUF)
* Departure date and hour: 19/04/2015 à 16:20 de Pau, Aéroport Pyrenees (PUF)
* Transportation (Train/Bus/Car/Plane):car + Plane
* Food (Special diet, allergies, vegetarian…): normal
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: philippe.grand@atoo-net.com
------------------------------------------

DevCamp Pau April 2015 Organization

2015-04-15T08:54:15Z

Rdoursenaud: Added menus

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Title: Dolibarr DevCamp 2015'''

The event is split in two parts this year:
* A public presentation of the project
* The usual community meeting

== Price ==
The full event is ''free'' but since space is limited, registrations are required (see below).

== Dates ==
April, 17 to 19

* Public presentation: 17 afternoon
* Community meeting: 18 to 19

=== Registrations ===
* Public presentation:
** Fill the form at goo.gl/67ZDAW before '''april, 10'''
* Community meeting:
** Here on the wiki before '''march, 28'''

== Location ==
Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France

=== Capacity ===
* Public presentation: ~100 people (friday afternoon)
* Community meeting: ~20 people

=== How to come ===
Please see directions at goo.gl/7ipG5z

== Main languages ==
* Public presentation: French
* Community meeting: English & French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc (contact@helioparc.fr)
* Lodging and Catering: GPC.solutions
* Attendees information & communication: Technopole Hélioparc
* Sponsoring management: GPC.solutions

=== Sponsors ===
* Technopole Hélioparc
* PauLLA

=== Partners ===
* La Mêlée Adour
* GRETA Béarn et Soule
* NumLab

== Lodging and catering ==

=== Hotel ===

We have negociated 42€/night/person at a nearby hotel.

Please book through us for the discounted price.

=== Food ===
Traiteur Latour

==== Saturday lunch ====

* Taboulé
* Tomates
* Rosette, chorizo
* Rôti de porc
* Fromage
* Tarte aux pommes
* Pain

==== Saturday dinner ====

* Salade de gésiers
* Axoa de porc
* Gâteau basque

==== Sunday lunch ====

* Pâtes fraîches
* Concombre
* Saucisson, jambon de Bayonne
* Rôti de bœuf
* Fromage du pays
* Dessert
* Pain

= Planning =

== Day 1 (Friday) ==

Auditorium
* 9:00: Breakfast (Organisers only)
* 10:00: Opening and free discussion
* 12:00: Lunch (Organisers and presenters only)
* 14:00: Start of general public presentations
* 14:15: Présentation du projet — Laurent Destailleur — teclib’ & NLTechno, Dolibarr Preferred Partners — Développeur principal et président de l’association
* 15:00: Retour d’expérience, organisation des Rencontres Mondiales du Logiciel Libre 2014 — Jean-François Ferry — Aternatik, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 15:45: Gérer un centre de formation — Florian Henry — Open-Concept.pro, Dolibarr Preferred Partner — Secrétaire de l’association
* 16:30: Opportunités pour le e-commerce — Jean Heimburger — Tiaris, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 17:15: Nouveautés des prochaines versions du logiciel — Laurent Destailleur
* 18:30: Apéritif and buffet supper (Invitations only)
Atelier numérique
* 21:00: Free play / code / hangout

''Next days are still in a'' '''Draft''' state ''. These will be updated as soon as we have more informations.''

== Day 2 (Saturday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Workshop topics =

If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

Lorenzo Novaro: I propose to have a "panel" about translations and a moment to revise the english language files.

= Attendees registration =

== Public presentation ==

Please go to goo.gl/67ZDAW

== Community meeting ==

Registration is done here, on the wiki

Please copy the template below to the registered attendees section and fill it with your informations.

You'll need a wiki account. If you don't have one please ask via email at '''contact@dolibarr.org'''.

'''Registration for Dolibarr devcamp 2015 at Pau are now closed'''

(You are however still welcome the friday afternoon 17th of april, for the public presentation, free entry)

== Registration template ==

------------------------------------------
* Firstname Lastname:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:
------------------------------------------

== Community meeting registered attendees ==

------------------------------------------
[[File:Raphaël Doursenaud.png|40px]]
* Firstname Lastname: [[Raphaël Doursenaud]]
* Age: 33
* Coming from (town, country): Pau, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Home :D
* Book hotel for me (yes/no): N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: rdoursenaud@gpcsolutions.fr
------------------------------------------
------------------------------------------
[[File:Florian_Henry.png|40px]]
* Firstname Lastname: [[Florian Henry]]
* Age: 34
* Coming from (town, country): Manduel, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: florian.henry@open-concept.pro
------------------------------------------
------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname: [[Jean Heimburger]]
* Age: 54
* Coming from (town, country): Sarrebourg, France
* Arrival date and hour: 17/04/2015 Pau gar 6h40
* Departure date and hour: 19/04/2015 Pau gare 11h05
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): none
* Accommodation (Common booked hotel/self…):hotel
* Book hotel for me (yes/no):yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:jean.heimburger@tiaris.info
------------------------------------------
------------------------------------------
* Firstname Lastname: [[Jean-François Ferry]]
* Age: 34
* Coming from (town, country): Montpellier, France
* Arrival date and hour: 17, morning
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel?
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: jfefe@aternatik.fr
------------------------------------------
------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 42
* Coming from (town, country): Pessac, France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Charles-Fr Benke]]
* Age: 47
* Coming from (town, country): Lyon, France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): GOOD
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charles.fr@benke.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------
------------------------------------------
[[File:Maxime Kohlhaas.png|40px]]
* Firstname Lastname: [[Maxime Kohlhaas]]
* Age: 28
* Coming from (town, country): Valence, France
* Arrival date and hour: 16, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hotel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: maxime@atm-consulting.fr
------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: [[Lorenzo Novaro]]
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation (Train/Bus/Car/Plane): Train/Plane
* Food (Special diet, allergies, vegetarian…): nuts
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Tommaso Basilici.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 36
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation: Train/Plane
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): Transport: TBD - Hotel: TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Juanjo Menent.png|40px]]
* Firstname Lastname: [[Juanjo Menent]]
* Age: 42
* Coming from (town, country): Gandia, Spain
* Arrival date and hour: 16, 20h57
* Departure date and hour: 20, 05h53
* Transportation (Train/Bus/Car/Plane): Train
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: Hotel
* Book hotel for me: Yes
* Estimated expenses: Transport: 229.70€ - Hotel: 168€.
* Contact email: jmenent@2byte.es
------------------------------------------
[[File:Arnaud Aujon Chevallier.png|40px]]
* Firstname Lastname: [[Arnaud Aujon Chevallier]]
* Age: 26
* Coming from (town, country): Toulouse, France
* Arrival date and hour: 18, 10h00
* Departure date and hour: 18, 18h00
* Transportation (Train/Bus/Car/Plane): Car
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: self
* Book hotel for me: No
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: arnaud@intelibre.fr
------------------------------------------
* Firstname Lastname: Francis Appels
* Age: 49
* Coming from (town, country): Herselt, Belgium
* Arrival date and hour: 16, 18h00
* Departure date and hour: 19, 21h00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: francis.appels@z-application.com
------------------------------------------
[[File:Marcos García.png|40px]]
* Firstname Lastname: [[Marcos García]]
* Age: 22
* Coming from (town, country): Valladolid, Spain
* Arrival date and hour: 17, 17:00h
* Departure date and hour: 20, 06:00h
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): Lactose.
* Accommodation (Common booked hotel/self…): Airbnb
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...): 180 €
* Contact email: marcosgdf@gmail.com
------------------------------------------
* Firstname Lastname: Pierre-Yvan Aupiais
* Age: 59
* Coming from (town, country): Toulouse , France
* Arrival date and hour: 17/04/2015 , 9h00
* Departure date and hour: 18/04/2015 , 17h00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A
* Contact email:py.aupiais@val-talents.fr
-------------------------------------------
* Firstname Lastname: Estephe LORIDAN
* Age: 36 ans
* Coming from (town, country): Noisiel, France
* Arrival date and hour: Dont know yet, friday end of morning.
* Departure date and hour: Sunday evening.
* Transportation (Train/Bus/Car/Plane): Plane (my charge)
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): yes.
* Estimated expenses (ticket, parking, toll, hotel...): no expense.
* Contact email: dolibarr@estephe.me
-------------------------------------------
* Firstname Lastname: PAQUIER Bernard
* Age: 32
* Coming from (town, country): Bordeaux, France
* Arrival date and hour: 17/04 - 10h
* Departure date and hour: 19/04 -18h
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N/A
* Accommodation (Common booked hotel/self…): Self
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: contact@dolibarr-addict.com
-------------------------------------------
[[File:Bahfir Abbes.jpeg|40px]]
* Firstname Lastname: Bahfir Abbes
* Age:49
* Coming from (town, country): Oran - Algeria
* Arrival date and hour:16 April 2015
* Departure date and hour: 19-20 April 2015
* Transportation (Train/Bus/Car/Plane): Plane/Train/Bus
* Food (Special diet, allergies, vegetarian…):normal
* Accommodation (Common booked hotel/self…): -
* Book hotel for me (yes/no): -
* Estimated expenses (ticket, parking, toll, hotel...): -
* Contact email:bafbes@gmail.com
------------------------------------------
[[File:Philippe Grand.png|40px]]
* Firstname Lastname: [[Philippe Grand]]
* Age:
* Coming from (town, country):Orléans - France
* Arrival date and hour: 17/04/2015 à 10:15 à Pau, Aéroport Pyrenees (PUF)
* Departure date and hour: 19/04/2015 à 16:20 de Pau, Aéroport Pyrenees (PUF)
* Transportation (Train/Bus/Car/Plane):car + Plane
* Food (Special diet, allergies, vegetarian…): normal
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: philippe.grand@atoo-net.com
------------------------------------------

Setup Other

2015-04-14T13:16:16Z

Rdoursenaud: Added documentation for PROJECT_LIST_SHOW_STARTDATE introduced in commit f323e89919cfd68f117bca2b927412f9efa381bb

[[Category:Admin]]
{{TemplateDocUser}}

'''Help about screen:''' Other setup

'''Menu path:''' Home -> Setup -> Other

= Goal =
This page is built to add/edit new parameters without a dedicated page to edit them. In most cases, it is parameters for your own development, external modules, or hidden features.

For a standard usage of Dolibarr, this screen must be kept empty and not be used.

= List of known hidden options =
Some options are not visible in the interface (often because they are deprecated or beta features). In most cases you do not need these functions and their use may make the application unstable.

To enable them you have to define a constant to 1 in '''Home -> Setup -> Other setup''':

== Global options ==
* MAIN_APPLICATION_TITLE => This will change the title of software (that appears on the login page by default). Warning, changing this may make Dolibarr version detection fails by smartphone applications like [[Application Android - DoliDroid]]

* MAIN_AUTOFILL_DATE => If this constant is defined (to something else than 0), the date of invoice, proposal, order or payment are filled with current date. It is highly recommended to NOT ENABLE this feature. This create a lot of input errors with no data not validated by users. This lead in bad values saved in database giving headaches when you have to do your accountancy reports ! However some users want it, so we provide it.

* MAIN_DISABLE_FULL_SCANLIST => Constant to define to disable complete scan of tables to know the total amount of element to allow the pagination to show total number of pages. To activate on systems with a very important number of data (Tables with more than 500 000 records).

* MAIN_FIRST_TO_UPPER => Dolibarr add upper case to thirdparties, contacts or members names if not done. Warning, with some languages (whose words with uppercase are not same words, or pagecode does not always have an uppercase, like cyrillic languages), this feature may alter your data.

* MAIN_LOGTOHTML => If this constants is defined, it is possible to have logs inside pages by adding the parameter &logtohtml=1 into URL.

* MAIN_USE_HOURMIN_IN_DATE_RANGE => On all entities lines (invoice, order, contract...), it is possible to add hour and minutes with date on fields "date start" and "date end".

* MAIN_REMOVE_INSTALL_WARNING => Remove all security warning that appears to administrator users if URL /install is public. You shoud solve the problem if warning occurs instead of removing this warning. For this, put a file called install.lock into Dolibarr root directory. This will remove warning but also make the page /install not possible to use to protect your installation.

* MAIN_OPTIMIZE_SPEED => Use some speed enhancements. See page [[Increase_Performance]] for more information.

* MAIN_OVERWRITE_TRANS_xx_YY => You can use this to change value of a translation key for language xx_YY (ie: en_US) without editing language files. For example: "TranslationKey1:New value1,TranslationKey2:New value 2". Note that using this option slow down seriously your instance. If you can, it is better to edit directly the language files into htdocs/lang/xx_YY.

* MAIN_REPEATCONTACTONEACHTAB => If added and set to 1, this add contacts on all tabs, not only main tab.

* MAIN_DISABLE_JQUERY_JNOTIFY => Disable usage of JNotify to show confirm or error messages

* MAIN_USE_JQUERY_JEDITABLE => Allow to update from screnn, directly into database, some properties of elements (invoices, proposals, ...) using Ajax. This make response time faster, but avoid using this features, because, it overpass some business actions (updates onother data that should be done consitently) and ignore business controls on data you saved. So this feature breaks consitency of data and stability of software.

* MAIN_USE_JQUERY_LAYOUT => Allow hidding the left menu

* MAIN_USE_JQUERY_MULTISELECT => Allow to use Ajax when a choice that require multiselect is used (for the moment only external modules uses select box with multiselect values).

* MAIN_HELPCENTER_LINKTOUSE => Define a target link "I need help" onto logon page

* MAIN_MODULES_FOR_EXTERNAL => Limit available modules for external users. By defaut value is 'facture,commande,contact,propal,projet,contrat,societe,ficheinter,expedition,agenda'

* MAIN_PRODUCT_DISABLE_CUSTOMCOUNTRYCODE => Avoid Custom code and country of origin to be set as product description when added to Propal/Order/Invoice

* MAIN_SHOW_TUNING_INFO => Add tuning information into javascript console. Better when xdebug is enabled.

* MAIN_DOL_SCRIPTS_ROOT => Define directory who contains 'scripts' directory (e.g /var/www/dolibarr)

* MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING => A warning saying setup of modules is not complete is shown if number of enabled modules is lower or equal than this value (1 if not defined)

* MAIN_ADD_SALE_REP_SIGNATURE_IN_NOTE => Add signature of first sale representative into documents (at end of public notes).

* MAIN_DISABLE_AJAX_COMBOX => If you have a large amount of thirdparty or product, you can disable the autocomplete feature on thirdparties list by setting constant MAIN_DISABLE_AJAX_COMBOX to 1 into Home-Setup-Other (with Dolibarr v3.6.0+).

* MAIN_USE_CACHE_MANIFEST => Add an HTML5 cache manifest to the page

* MAIN_FORCELANGDIR => relative path of the directory holding your custom langs folder.

* MAIN_VAT_DEFAULT_IF_AUTODETECT_FAILS => allow to define a default VAT rate

* MAIN_HTML_TITLE => can be used to control how html title is formated. If value contains key 'noapp', application name will not be output. If value contains 'thirdpartynameonly', on tab for thirdparties, only name of thirdparties are output. Value can be list of tags: 'noapp;thirdpartynameonly'

* MAIN_MENU_HIDE_UNAUTHORIZED => Hide menu if user not autorized rather than just grey them

== Email and SMS ==
* MAIN_MAIL_DEBUG => Write content with header of last mail into file dolibarr_mail.log into directory dolibarr_main_data_root.

* MAIN_SMS_DEBUG => Write content of SMS sent into file dolibarr_sms.log into directory dolibarr_main_data_root.

* MAIN_MAIL_ALLOW_SENDMAIL_F => On Linux or BSD system, PHP email function use the command sendmail local to server. In some cases, the sender email must be provided on command line of sendmail with option -f. This option is here to ask Dolibarr to call the function '''mail''' of PHP by adding value for the option -f. Note that in most cases, even with sendmail, sender email is correctly managed as it is added in the email technical header. This option is here only for rare setup of sendmail that ask the '''-f''' option to be mandatory or for sendmail setup that does not use by default the Return-path of header email to define the sender (with this option, the return-path will be provided also on command line and not lost by sendmail).

* MAIN_MAIL_SENDMAIL_FORCE_BA => On Lunix or BSD system, PHP email function use the command sendmail local to server. In some case, we want to recipient to be provided to sendmail into the email content instead of its command line parameter. For this we must add the '''-ba''' parameter to sendmail. This option ask PHP to provide this parameter when sending a mail. Note that another solution is to edit the '''mail.force_extra_parameters=-ba''' into '''php.ini''' file.

* MAIN_MAIL_NO_FULL_EMAIL => Recipient email and sender are cleaned to be on form "<email>" instead of "Name <email>". This might solve problem of compatibility with very old mailers.

* MAIN_FIX_FOR_BUGGED_MTA => Some MTA agent are bugged and add some CR chars each time they saw a LF. Because Dolibarr emails are forged to be already cleaned, if MTA agent do that, you will send an email with two CR chars. This may result in having recipient not able to read your email. To fix this, add this constant to 1. Dolibarr will then create an email that is not RFC compliant but because the MTA agent is bugged, the email will be modified and become correct during sending, solving the problem of bad email received. Add this constant if your recipient experience problems when opening email for example users using webmail of orange.fr or hotmail.com

* MAIN_MAIL_DO_NOT_USE_SIGN => Do not add user signature at end of suggested predefined email

* MAIL_FORCE_DELIVERY_RECEIPT_INVOICE, MAIL_FORCE_DELIVERY_RECEIPT_ORDER, MAIL_FORCE_DELIVERY_RECEIPT_PROPAL => Force delivery receipt to "Yes" onto form to send email.

* MAIN_EMAIL_USECCC => Show field BCC into email forms.

* MAIN_MAIL_AUTOCOPY_PROPOSAL_TO, MAIN_MAIL_AUTOCOPY_ORDER_TO, MAIN_MAIL_AUTOCOPY_INVOICE_TO => Send a BCC to the recipients when sending email for proposal, order or invoice. If option MAIN_EMAIL_USECCC is also set, you will see recipient email of BCC into email form on same line used to enter BCC.

== Third parties module ==
* SOCIETE_DISABLE_CUSTOMERS => Remove all menu and features related to customers
* SOCIETE_DISABLE_PROSPECTS => Remove all menu and features related to prospects
* SOCIETE_DISABLE_STATE => Do not use field "state/province"
* MAIN_THIRPARTY_CREATION_INDIVIDUAL => Default Thirparty create are individual

== Proposals module ==
* PROPAL_CLONE_ON_CREATE_PAGE => On the create proposal page, ask if we want to create the proposal by cloning an already existing one. You should use instead the "Clone" button available on existing proposals.
* MAIN_PROPAL_CHOOSE_ODT_DOCUMENT => On setup page, you'll be able to select which ODT document to use when close or cancel proposals.
* <s>MAIN_GENERATE_DOCUMENTS_WITH_PICTURE</s> MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Add picture of product (the first one found if there is several) into the generated PDF of proposals. Note that using this reduce available width for product description.
* WORKFLOW_PROPAL_CAN_CLASSIFY_BILLED_WITHOUT_INVOICES => Button "Classified Billed" is visible on proposal even if there is no invoice linked to proposal.

== Invoice module ==
* FACTURE_SHOW_SEND_REMINDER => Show link "Send reminder by mail", same feature than "Send by mail" (obsolete feature).
* INVOICE_CAN_ALWAYS_BE_REMOVED => Allow to always delete invoices (even if invoice is not last one).
* INVOICE_CAN_NEVER_BE_REMOVED => Never allow to delete invoices (except draft invoices).
* INVOICE_POSITIVE_CREDIT_NOTE => All amounts on PDF credit notes are positive.
* FACTURE_CHANGE_THIRDPARTY => Allow to change the third party in the draft invoices. If a discount was set from the original thirdparty, then discount remain, making data not coherent.
* FACTURE_USE_PROFORMAT => Enable PROFORMAT invoices type.
* FACTURE_DEPOSITS_ARE_JUST_PAYMENTS => Treats deposit invoices as a special case. Deposit invoices don't get counted on turnover. They are then applied as a payment, like a discount, on the final invoice.
* FACTURE_SENDBYEMAIL_FOR_ALL_STATUS => Can send invoice by email to customer even if invoice has status "draft".
* MAIN_GENERATE_DOCUMENTS_WITHOUT_VAT => Disable VAT on genrated documents. like for an association. (it's work with crabe template)
* FAC_AUTO_FILLJS => Display a button to autofill the payment amount for each invoice on the payment creation page

== Order module ==
* COMMANDE_REQUIRE_SOURCE => Make the input field "Source of order" mandatory.
* COMMANDE_VALID_AFTER_CLOSE_PROPAL => When an order is created on a proposal close, the order is directly defined with status "Validated".

== Export module ==
* EXPORT_CSV_SEPARATOR_TO_USE => String value to use as separator to delimit fields int exported files (by default Dolibarr use ","). Example: EXPORT_CSV_SEPARATOR_TO_USE=;
* EXPORT_CSV_FORCE_CHARSET => Choose the charset of file built by CSV export. By default: UTF-8. Example: EXPORT_CSV_FORCE_CHARSET=ISO-8859-1

== Agenda module ==
* AGENDA_MAX_EVENTS_DAY_VIEW => Define the maximum number of visible entries for each day in agenda. Default value is 3. Value 0 means no limit.
* AGENDA_USE_EVENT_TYPE => Add a mandatory field "Type" when creating an event (deprecated).
* AGENDA_AUTOSET_END_DATE_WITH_DELTA_HOURS => To automatically set end date of event to start date + delta on event creation page.

== Products module ==
* PRODUCT_ADD_TYPE_IN_DOCUMENTS => Add text "Product" or "Service" at beginning of details lines on built PDF documents.
* PRODUCT_SHOW_WHEN_CREATE => Old option no more supported (create problems) to be able to add lines of product during first step of element creation.
* PRODUCT_DONOTSEARCH_ANYWHERE => When Ajax search is enabled, search is done on criteria anywhere in label of product. By adding this option, search is done only on start of label. This is really faster when you have a huge number of products.
* PRODUIT_DESC_IN_LIST => Show long description of product/service into lists.
* PRODUIT_MULTIPRICES_LABELx (where x = 1,2,...) => When option mode to set prices are PRODUIT_MULTIPRICES (n different prices per product according to a customer level), this option will force a label for the level x. Value must be a key. If the key is found into translation files, it will be replaced by the translated value.

== Services module ==
* SERVICE_ARE_ECOMMERCE_200238EC => If this option is enabled, services are processed like eServices according to directove of EU Council Directive 2002/38/EC (http://ec.europa.eu/taxation_customs/taxation/vat/traders/e-commerce/article_1610_en.htm). Default VAT rate are based on buying country instead of selling country for BtoC sells.

== Stocks ==
* STOCK_SUPPORTS_SERVICES => Services are also increased/decreased into stocks.

== Point of Sale ==
* CASHDESK_SHOW_KEYPAD => Show a mouse key pad into Point Of Sale.

== Contracts ==
* CONTRACT_SUPPORT_PRODUCTS => Products are also suggested into module contract.

== Projects module ==
* PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS => Enable linking a project to any supplier even when using the third party link feature. Note: Set to 1 by default from 3.7.
* PROJECT_TIME_ON_ALL_TASKS_MY_PROJECTS => Can add time spent on tasks, even if i am not assigned to task (however, task must be a project i am a contact).
* PROJECT_SHOW_REF_INTO_LISTS => Add column with project ref into list (with 3.7 list of supplier invoices only, will be expanded to other lists)
* PROJECT_HIDE_UNSELECTABLES => Hide into select list, all project that we can't select (closed or draft)
* PROJECT_HIDE_TASKS => Hide tasks. For user using project only as an analytics key and not using tasks.
* PROJECT_LIST_SHOW_STARTDATE => Shows start date of projects in project lists.

== Foundation module ==
* MEMBER_URL_REDIRECT_SUBSCRIPTION => Link called and shown when a member account is autocreated in member module by a guest user.
* MEMBER_EXT_URL_SUBSCRIPTION_INFO => Link of external page pointed by the "Show here" link to add in fron off payment cell form into the page to make online subscription.

== Interventions module ==
* FICHINTER_CLASSIFY_BILLED => Allow to classify an intervention card as "Billed". This add also trigger FICHINTER_CLASSIFY_BILLED into list of possible automatic event into agenda.
* FICHINTER_DISABLE_DETAILS => Disable entry of details line on intervention. Can validate with no line.

== Suppliers module ==
* FOURN_PRODUCT_AVAILABILITY => On the Suppliers price page of the products, active the supplier product availability. This is duplicate feature with delivery_delay introduced with 3.8.
* SUPPLIER_ORDER_AUTOADD_USER_CONTACT => Add user approving supplier order as a contact automatically.
* SUPPLIER_ORDER_USE_DISPATCH_STATUS => Add a status on each dispatch order line
* SUPPLIER_ORDER_NO_DIRECT_APPROVE => No button "Validate and Approve". Always do step "Validate" and "Approve" in 2 steps.

== PDF options ==
* MAIN_DISABLE_FORCE_SAVEAS => If your browser ask always to save downloaded files on disk (like PDF), try to add this option. File might appears directly into your browser.

* MAIN_DISABLE_PDF_COMPRESSION => Disable PDF compression.

* MAIN_INVERT_SENDER_RECIPIENT => Invert sender and recipient in some PDF.

* MAIN_DISABLE_PDF_AUTOUPDATE => Disable automatic generation of PDF each time we add/update/delete a product line (we can still build document by clicking on "Generate"). This option may increase interface speed on server with low CPU.

* MAIN_USE_BACKGROUND_ON_PDF => Define this constant with short name of an image (example "myimage.jpg") that must be saved into directory "documents/mycompany/logos". This will add this background image into your generated PDF files. Warning: This option make TCPDF library beeing crazy sometime and content on image disappeared !

* MAIN_ADD_PDF_BACKGROUND => Define this constant with short name of a PDF file (example "mypdf.pdf") that must be saved into directory "documents/mycompany". This will add PDF as a background of some of your generated PDF files (proposals,invoices,orders). If you need to concat PDF, see instead [[Module Concat PDF]].

* MAIN_PDF_FORCE_FONT => To ignore font defined into language file and force usage of a particular font. For example "DejaVuSans".

* MAIN_PDF_MARGIN_LEFT, MAIN_PDF_MARGIN_RIGHT, MAIN_PDF_MARGIN_TOP, MAIN_PDF_MARGIN_BOTTOM => To force the margins (mm) of PDF documents (10 is default).

* MAIN_PDF_FREETEXT_HEIGHT => Change height of space reserved to output the free text.

* MAIN_PDF_TITLE_BACKGROUND_COLOR => Can define a background color onto title line. Example: '220,220,200'

* MAIN_USE_COMPANY_NAME_OF_CONTACT => Use contact name and information rather than company

* MAIN_ODT_AS_PDF => Activate PDF conversion from ODT document. If value is 'jodconverter', java and jodconverter command line tool must be available. If value is '/pathto/jodconverter.jar', then java and the jodconvertar jar must exists. soffice must also be available. MAIN_DOL_SCRIPTS_ROOT Must also be defined to path where the "scripts" directory is stored (for example /var/www/mydolibarr).

* MAIN_ODT_AS_PDF_DEL_SOURCE => For ODT generation. If set then initial behaviour is conserved, odt file is removed when generate pdf. Disabled by default

* MAIN_GENERATE_PROPOSALS_WITH_PICTURE => Include first image of product into line of generated PDF proposal.

* MAIN_GENERATE_INVOICES_WITH_PICTURE => Include first image of product into line of generated PDF invoice.

* MAIN_DOCUMENTS_WITH_PICTURE_WIDTH => Can change size of picture when hidden option MAIN_GENERATE_PROPOSALS_WITH_PICTURE is used. By default value is 20.

* PDF_SHOW_PROJECT => Show project onto PDF (supported on supplier order only for the moment)

== WYSIWYG editor ==

* FCKEDITOR_ENABLE_DETAILS_FULL => Can cut and paste external images (hosted on external server) into description of proposal, orders or invoices. WARNING: PDF generation is not guaranted with this. Also if the image is removed or renamed by the image hoster, your proposal, order or invoice will be broken.

DevCamp Pau April 2015 Organization

2015-04-08T10:29:14Z

Rdoursenaud: Added directions to come to the DevCamp

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Title: Dolibarr DevCamp 2015'''

The event is split in two parts this year:
* A public presentation of the project
* The usual community meeting

== Price ==
The full event is ''free'' but since space is limited, registrations are required (see below).

== Dates ==
April, 17 to 19

* Public presentation: 17 afternoon
* Community meeting: 18 to 19

=== Registrations ===
* Public presentation:
** Fill the form at goo.gl/67ZDAW before '''april, 10'''
* Community meeting:
** Here on the wiki before '''march, 28'''

== Location ==
Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France

=== Capacity ===
* Public presentation: ~100 people (friday afternoon)
* Community meeting: ~20 people

=== How to come ===
Please see directions at goo.gl/7ipG5z

== Main languages ==
* Public presentation: French
* Community meeting: English & French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc (contact@helioparc.fr)
* Lodging and Catering: GPC.solutions
* Attendees information & communication: Technopole Hélioparc
* Sponsoring management: GPC.solutions

=== Sponsors ===
* Technopole Hélioparc
* PauLLA

=== Partners ===
* La Mêlée Adour
* GRETA Béarn et Soule
* NumLab

== Lodging and catering ==

=== Hotel ===

We have negociated 42€/night/person at a nearby hotel.

Please book through us for the discounted price.

=== Food ===
''To be defined''

= Planning =

== Day 1 (Friday) ==

Auditorium
* 9:00: Breakfast (Organisers only)
* 10:00: Opening and free discussion
* 12:00: Lunch (Organisers and presenters only)
* 14:00: Start of general public presentations
* 14:15: Présentation du projet — Laurent Destailleur — teclib’ & NLTechno, Dolibarr Preferred Partners — Développeur principal et président de l’association
* 15:00: Retour d’expérience, organisation des Rencontres Mondiales du Logiciel Libre 2014 — Jean-François Ferry — Aternatik, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 15:45: Gérer un centre de formation — Florian Henry — Open-Concept.pro, Dolibarr Preferred Partner — Secrétaire de l’association
* 16:30: Opportunités pour le e-commerce — Jean Heimburger — Tiaris, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 17:15: Nouveautés des prochaines versions du logiciel — Laurent Destailleur
* 18:30: Apéritif and buffet supper (Invitations only)
Atelier numérique
* 21:00: Free play / code / hangout

''Next days are still in a'' '''Draft''' state ''. These will be updated as soon as we have more informations.''

== Day 2 (Saturday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Workshop topics =

If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

Lorenzo Novaro: I propose to have a "panel" about translations and a moment to revise the english language files.

= Attendees registration =

== Public presentation ==

Please go to goo.gl/67ZDAW

== Community meeting ==

Registration is done here, on the wiki

Please copy the template below to the registered attendees section and fill it with your informations.

You'll need a wiki account. If you don't have one please ask via email at '''contact@dolibarr.org'''.

'''Registration for Dolibarr devcamp 2015 at Pau are now closed'''

(You are however still welcome the friday afternoon 17th of april, for the public presentation, free entry)

== Registration template ==

------------------------------------------
* Firstname Lastname:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:
------------------------------------------

== Community meeting registered attendees ==

------------------------------------------
[[File:Raphaël Doursenaud.png|40px]]
* Firstname Lastname: [[Raphaël Doursenaud]]
* Age: 33
* Coming from (town, country): Pau, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Home :D
* Book hotel for me (yes/no): N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: rdoursenaud@gpcsolutions.fr
------------------------------------------
------------------------------------------
[[File:Florian_Henry.png|40px]]
* Firstname Lastname: [[Florian Henry]]
* Age: 34
* Coming from (town, country): Manduel, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: florian.henry@open-concept.pro
------------------------------------------
------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname: [[Jean Heimburger]]
* Age: 54
* Coming from (town, country): Sarrebourg, France
* Arrival date and hour: 17/04/2015 Pau Uzein 10h15 (depuis Orly)
* Departure date and hour: 19/04/2015 Pau Uzein 16h20
* Transportation (Train/Bus/Car/Plane): plane
* Food (Special diet, allergies, vegetarian…): none
* Accommodation (Common booked hotel/self…):hotel
* Book hotel for me (yes/no):yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:jean.heimburger@tiaris.info
------------------------------------------
------------------------------------------
* Firstname Lastname: [[Jean-François Ferry]]
* Age: 34
* Coming from (town, country): Montpellier, France
* Arrival date and hour: 17, morning
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel?
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: jfefe@aternatik.fr
------------------------------------------
------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 42
* Coming from (town, country): Pessac, France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Charles-Fr Benke]]
* Age: 47
* Coming from (town, country): Lyon, France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): GOOD
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charles.fr@benke.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------
------------------------------------------
[[File:Maxime Kohlhaas.png|40px]]
* Firstname Lastname: [[Maxime Kohlhaas]]
* Age: 28
* Coming from (town, country): Valence, France
* Arrival date and hour: 16, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hotel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: maxime@atm-consulting.fr
------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: Lorenzo Novaro
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation (Train/Bus/Car/Plane): Train/Plane
* Food (Special diet, allergies, vegetarian…): nuts
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 36
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation: Train/Plane
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): Transport: TBD - Hotel: TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Juanjo Menent.png|40px]]
* Firstname Lastname: [[Juanjo Menent]]
* Age: 42
* Coming from (town, country): Gandia, Spain
* Arrival date and hour: 16, 20h57
* Departure date and hour: 20, 05h53
* Transportation (Train/Bus/Car/Plane): Train
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: Hotel
* Book hotel for me: Yes
* Estimated expenses: Transport: 229.70€ - Hotel: 168€.
* Contact email: jmenent@2byte.es
------------------------------------------
[[File:Arnaud Aujon Chevallier.png|40px]]
* Firstname Lastname: [[Arnaud Aujon Chevallier]]
* Age: 26
* Coming from (town, country): Toulouse, France
* Arrival date and hour: 18, 10h00
* Departure date and hour: 18, 18h00
* Transportation (Train/Bus/Car/Plane): Car
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: self
* Book hotel for me: No
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: arnaud@intelibre.fr
------------------------------------------
* Firstname Lastname: Francis Appels
* Age: 49
* Coming from (town, country): Herselt, Belgium
* Arrival date and hour: 16, 18h00
* Departure date and hour: 19, 21h00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: francis.appels@z-application.com
------------------------------------------
[[File:Marcos García.png|40px]]
* Firstname Lastname: Marcos García
* Age: 22
* Coming from (town, country): Valladolid, Spain
* Arrival date and hour: 17, 17:00h
* Departure date and hour: 20, 06:00h
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): Lactose.
* Accommodation (Common booked hotel/self…): Airbnb
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...): 180 €
* Contact email: marcosgdf@gmail.com
------------------------------------------
* Firstname Lastname: Pierre-Yvan Aupiais
* Age: 59
* Coming from (town, country): Toulouse , France
* Arrival date and hour: 17/04/2015 , 9h00
* Departure date and hour: 18/04/2015 , 17h00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A
* Contact email:py.aupiais@val-talents.fr
-------------------------------------------
* Firstname Lastname: Estephe LORIDAN
* Age: 36 ans
* Coming from (town, country): Noisiel, France
* Arrival date and hour: Dont know yet, friday end of morning.
* Departure date and hour: Sunday evening.
* Transportation (Train/Bus/Car/Plane): Plane (my charge)
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): yes.
* Estimated expenses (ticket, parking, toll, hotel...): no expense.
* Contact email: dolibarr@estephe.me
-------------------------------------------
* Firstname Lastname: PAQUIER Bernard
* Age: 32
* Coming from (town, country): Bordeaux, France
* Arrival date and hour: 17/04 - 10h
* Departure date and hour: 19/04 -18h
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N/A
* Accommodation (Common booked hotel/self…): Self
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: contact@dolibarr-addict.com
-------------------------------------------
[[File:Bahfir Abbes.jpeg|40px]]
* Firstname Lastname:Bahfir Abbes
* Age:49
* Coming from (town, country): Oran - Algeria
* Arrival date and hour:16 April 2015
* Departure date and hour: 19-20 April 2015
* Transportation (Train/Bus/Car/Plane): Plane/Train/Bus
* Food (Special diet, allergies, vegetarian…):normal
* Accommodation (Common booked hotel/self…): -
* Book hotel for me (yes/no): -
* Estimated expenses (ticket, parking, toll, hotel...): -
* Contact email:bafbes@gmail.com

DevCamp Pau April 2015 Organization

2015-04-02T10:29:08Z

Rdoursenaud: Wrong date

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Title: Dolibarr DevCamp 2015'''

The event is split in two parts this year:
* A public presentation of the project
* The usual community meeting

== Price ==
The full event is ''free'' but since space is limited, registrations are required (see below).

== Dates ==
April, 17 to 19

* Public presentation: 17 afternoon
* Community meeting: 18 to 19

=== Registrations ===
* Public presentation:
** Fill the form at goo.gl/67ZDAW before '''april, 10'''
* Community meeting:
** Here on the wiki before '''march, 28'''

== Location ==
Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France

=== Capacity ===
* Public presentation: ~100 people (friday afternoon)
* Community meeting: ~20 people

== Main languages ==
* Public presentation: French
* Community meeting: English & French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc (contact@helioparc.fr)
* Lodging and Catering: GPC.solutions
* Attendees information & communication: Technopole Hélioparc
* Sponsoring management: GPC.solutions

=== Sponsors ===
* Technopole Hélioparc
* PauLLA

=== Partners ===
* La Mêlée Adour
* GRETA Béarn et Soule
* NumLab

== Lodging and catering ==

=== Hotel ===

We have negociated 42€/night/person at a nearby hotel.

Please book through us for the discounted price.

=== Food ===
''To be defined''

= Planning =

== Day 1 (Friday) ==

Auditorium
* 9:00: Breakfast (Organisers only)
* 10:00: Opening and free discussion
* 12:00: Lunch (Organisers and presenters only)
* 14:00: Start of general public presentations
* 14:15: Présentation du projet — Laurent Destailleur — teclib’ & NLTechno, Dolibarr Preferred Partners — Développeur principal et président de l’association
* 15:00: Retour d’expérience, organisation des Rencontres Mondiales du Logiciel Libre 2014 — Jean-François Ferry — Aternatik, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 15:45: Gérer un centre de formation — Florian Henry — Open-Concept.pro, Dolibarr Preferred Partner — Secrétaire de l’association
* 16:30: Opportunités pour le e-commerce — Jean Heimburger — Tiaris, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 17:15: Nouveautés des prochaines versions du logiciel — Laurent Destailleur
* 18:30: Apéritif and buffet supper (Invitations only)
Atelier numérique
* 21:00: Free play / code / hangout

''Next days are still in a'' '''Draft''' state ''. These will be updated as soon as we have more informations.''

== Day 2 (Saturday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Workshop topics =

If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

Lorenzo Novaro: I propose to have a "panel" about translations and a moment to revise the english language files.

= Attendees registration =

== Public presentation ==

Please go to goo.gl/67ZDAW

== Community meeting ==

Registration is done here, on the wiki

Please copy the template below to the registered attendees section and fill it with your informations.

You'll need a wiki account. If you don't have one please ask via email at '''contact@dolibarr.org'''.

'''Registration for Dolibarr devcamp 2015 at Pau are now closed''' (You are however still welcome the friday afternoon 17th of april, for the public presentation, free entry)

== Registration template ==

------------------------------------------
* Firstname Lastname:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:
------------------------------------------

== Community meeting registered attendees ==

------------------------------------------
[[File:Raphaël Doursenaud.png|40px]]
* Firstname Lastname: [[Raphaël Doursenaud]]
* Age: 33
* Coming from (town, country): Pau, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Home :D
* Book hotel for me (yes/no): N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: rdoursenaud@gpcsolutions.fr
------------------------------------------
------------------------------------------
[[File:Florian_Henry.png|40px]]
* Firstname Lastname: [[Florian Henry]]
* Age: 34
* Coming from (town, country): Manduel, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: florian.henry@open-concept.pro
------------------------------------------
------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname: [[Jean Heimburger]]
* Age: 54
* Coming from (town, country): Sarrebourg, France
* Arrival date and hour: 17/04/2015 Pau Uzein 10h15 (depuis Orly)
* Departure date and hour: 19/04/2015 Pau Uzein 16h20
* Transportation (Train/Bus/Car/Plane): plane
* Food (Special diet, allergies, vegetarian…): none
* Accommodation (Common booked hotel/self…):hotel
* Book hotel for me (yes/no):yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:jean.heimburger@tiaris.info
------------------------------------------
------------------------------------------
* Firstname Lastname: [[Jean-François Ferry]]
* Age: 34
* Coming from (town, country): Montpellier, France
* Arrival date and hour: 17, morning
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel?
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: jfefe@aternatik.fr
------------------------------------------
------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 42
* Coming from (town, country): Pessac, France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Charles-Fr Benke]]
* Age: 47
* Coming from (town, country): Lyon, France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): GOOD
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charles.fr@benke.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------
------------------------------------------
[[File:Maxime Kohlhaas.png|40px]]
* Firstname Lastname: [[Maxime Kohlhaas]]
* Age: 28
* Coming from (town, country): Valence, France
* Arrival date and hour: 16, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hotel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: maxime@atm-consulting.fr
------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: Lorenzo Novaro
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation (Train/Bus/Car/Plane): Train/Plane
* Food (Special diet, allergies, vegetarian…): nuts
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 36
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation: Train/Plane
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): Transport: TBD - Hotel: TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Juanjo Menent.png|40px]]
* Firstname Lastname: [[Juanjo Menent]]
* Age: 42
* Coming from (town, country): Gandia, Spain
* Arrival date and hour: 16, 20h57
* Departure date and hour: 20, 05h53
* Transportation (Train/Bus/Car/Plane): Train
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: Hotel
* Book hotel for me: Yes
* Estimated expenses: Transport: 229.70€ - Hotel: 168€.
* Contact email: jmenent@2byte.es
------------------------------------------
[[File:Arnaud Aujon Chevallier.png|40px]]
* Firstname Lastname: [[Arnaud Aujon Chevallier]]
* Age: 26
* Coming from (town, country): Toulouse, France
* Arrival date and hour: 18, 10h00
* Departure date and hour: 18, 18h00
* Transportation (Train/Bus/Car/Plane): Car
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: self
* Book hotel for me: No
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: arnaud@intelibre.fr
------------------------------------------
* Firstname Lastname: Francis Appels
* Age: 49
* Coming from (town, country): Herselt, Belgium
* Arrival date and hour: 16, 18h00
* Departure date and hour: 19, 21h00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: francis.appels@z-application.com
------------------------------------------
[[File:Marcos García.png|40px]]
* Firstname Lastname: Marcos García
* Age: 22
* Coming from (town, country): Valladolid, Spain
* Arrival date and hour: 16, TBD
* Departure date and hour: 19, TBD
* Transportation (Train/Bus/Car/Plane): Bus
* Food (Special diet, allergies, vegetarian…): Lactose.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): TBD
* Estimated expenses (ticket, parking, toll, hotel...): ~ 200 €
* Contact email: marcosgdf@gmail.com
------------------------------------------
* Firstname Lastname: Pierre-Yvan Aupiais
* Age: 59
* Coming from (town, country): Toulouse , France
* Arrival date and hour: 17/04/2015 , 9h00
* Departure date and hour: 18/04/2015 , 17h00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A
* Contact email:py.aupiais@val-talents.fr
-------------------------------------------
* Firstname Lastname: Estephe LORIDAN
* Age: 36 ans
* Coming from (town, country): Noisiel, France
* Arrival date and hour: Dont know yet, friday end of morning.
* Departure date and hour: Sunday evening.
* Transportation (Train/Bus/Car/Plane): Plane (my charge)
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): yes.
* Estimated expenses (ticket, parking, toll, hotel...): no expense.
* Contact email: dolibarr@estephe.me
-------------------------------------------
* Firstname Lastname: PAQUIER Bernard
* Age: 32
* Coming from (town, country): Bordeaux, France
* Arrival date and hour: 17/04 - 10h
* Departure date and hour: 19/04 -18h
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N/A
* Accommodation (Common booked hotel/self…): Self
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: contact@dolibarr-addict.com
-------------------------------------------
[[File:Bahfir Abbes.jpeg|40px]]
* Firstname Lastname:Bahfir Abbes
* Age:49
* Coming from (town, country): Oran - Algeria
* Arrival date and hour:16 April 2015
* Departure date and hour: 19-20 April 2015
* Transportation (Train/Bus/Car/Plane): Plane/Train/Bus
* Food (Special diet, allergies, vegetarian…):normal
* Accommodation (Common booked hotel/self…): -
* Book hotel for me (yes/no): -
* Estimated expenses (ticket, parking, toll, hotel...): -
* Contact email:bafbes@gmail.com

DevCamp Pau April 2015 Organization

2015-03-28T14:38:08Z

Rdoursenaud: Big update with latest informations

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
'''Title: Dolibarr DevCamp 2015'''

The event is split in two parts this year:
* A public presentation of the project
* The usual community meeting

== Price ==
The full event is ''free'' but since space is limited, registrations are required (see below).

== Dates ==
April, 17 to 19

* Public presentation: 17 afternoon
* Community meeting: 18 to 19

=== Registrations ===
* Public presentation:
** Fill the form at goo.gl/67ZDAW before '''april, 10'''
* Community meeting:
** Here on the wiki before '''march, 28'''

== Location ==
Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France

=== Capacity ===
* Public presentation: ~100 people
* Community meeting: ~20 people

== Main languages ==
* Public presentation: French
* Community meeting: English & French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc (contact@helioparc.fr)
* Lodging and Catering: GPC.solutions
* Attendees information & communication: Technopole Hélioparc
* Sponsoring management: GPC.solutions

=== Sponsors ===
* Technopole Hélioparc
* PauLLA

=== Partners ===
* La Mêlée Adour
* GRETA Béarn et Soule
* NumLab

== Lodging and catering ==

=== Hotel ===

We have negociated 42€/night/person at a nearby hotel.

Please book through us for the discounted price.

=== Food ===
''To be defined''

= Planning =

== Day 1 (Friday) ==

Auditorium
* 9:00: Breakfast (Organisers only)
* 10:00: Opening and free discussion
* 12:00: Lunch (Organisers and presenters only)
* 14:00: Start of general public presentations
* 14:15: Présentation du projet — Laurent Destailleur — teclib’ & NLTechno, Dolibarr Preferred Partners — Développeur principal et président de l’association
* 15:00: Retour d’expérience, organisation des Rencontres Mondiales du Logiciel Libre 2014 — Jean-François Ferry — Aternatik, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 15:45: Gérer un centre de formation — Florian Henry — Open-Concept.pro, Dolibarr Preferred Partner — Secrétaire de l’association
* 16:30: Opportunités pour le e-commerce — Jean Heimburger — Tiaris, Dolibarr Preferred Partner — Membre du conseil d’administration de l’association
* 17:15: Nouveautés des prochaines versions du logiciel — Laurent Destailleur
* 18:30: Apéritif and buffet supper (Invitations only)
Atelier numérique
* 21:00: Free play / code / hangout

''Next days are still in a'' '''Draft''' state ''. These will be updated as soon as we have more informations.''

== Day 2 (Saturday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==

Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Workshop topics =

If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

Lorenzo Novaro: I propose to have a "panel" about translations and a moment to revise the english language files.

= Attendees registration =

== Public presentation ==

Please go to goo.gl/67ZDAW

== Community meeting ==

Registration is done here, on the wiki

Please copy the template below to the registered attendees section and fill it with your informations.

You'll need a wiki account. If you don't have one please ask via email at '''contact@dolibarr.org'''.

== Registration template ==

------------------------------------------
* Firstname Lastname:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:
------------------------------------------

== Community meeting registered attendees ==

------------------------------------------
[[File:Raphaël Doursenaud.png|40px]]
* Firstname Lastname: [[Raphaël Doursenaud]]
* Age: 33
* Coming from (town, country): PAU, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Home :D
* Book hotel for me (yes/no): N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: rdoursenaud@gpcsolutions.fr
------------------------------------------
------------------------------------------
[[File:Florian_Henry.png|40px]]
* Firstname Lastname: [[Florian Henry]]
* Age: 34
* Coming from (town, country): MANDUEL, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: florian.henry@open-concept.pro
------------------------------------------
------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname: [[Jean Heimburger]]
* Age: 54
* Coming from (town, country): Sarrebourg
* Arrival date and hour: 17/04/2015 Pau Uzein 10h15 (depuis Orly)
* Departure date and hour: 19/04/2015 Pau Uzein 16h20
* Transportation (Train/Bus/Car/Plane): plane
* Food (Special diet, allergies, vegetarian…): none
* Accommodation (Common booked hotel/self…):hotel
* Book hotel for me (yes/no):yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:jean.heimburger@tiaris.info
------------------------------------------
------------------------------------------
* Firstname Lastname: [[Jean-François Ferry]]
* Age: 34
* Coming from (town, country): Montpellier, France
* Arrival date and hour: 17, morning
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel?
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: jfefe@aternatik.fr
------------------------------------------
------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 42
* Coming from (town, country): PESSAC
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Charles-Fr Benke]]
* Age: 47
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): GOOD
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charles.fr@benke.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------
------------------------------------------
[[File:Maxime Kohlhaas.png|40px]]
* Firstname Lastname: [[Maxime Kohlhaas]]
* Age: 28
* Coming from (town, country): Valence, France
* Arrival date and hour: 16, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hotel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: maxime@atm-consulting.fr
------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: Lorenzo Novaro
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation (Train/Bus/Car/Plane): Train/Plane
* Food (Special diet, allergies, vegetarian…): nuts
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 36
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation: Train/Plane
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): Transport: TBD - Hotel: TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Juanjo Menent.png|40px]]
* Firstname Lastname: [[Juanjo Menent]]
* Age: 42
* Coming from (town, country): Gandia, Spain
* Arrival date and hour: 16, 20h57
* Departure date and hour: 20, 05h53
* Transportation (Train/Bus/Car/Plane): Train
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: Hotel
* Book hotel for me: Yes
* Estimated expenses: Transport: 229.70€ - Hotel: 168€.
* Contact email: jmenent@2byte.es
------------------------------------------
[[File:Arnaud Aujon Chevallier.png|40px]]
* Firstname Lastname: [[Arnaud Aujon Chevallier]]
* Age: 26
* Coming from (town, country): Toulouse, France
* Arrival date and hour: 18, 10h00
* Departure date and hour: 18, 18h00
* Transportation (Train/Bus/Car/Plane): Car
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: self
* Book hotel for me: No
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: arnaud@intelibre.fr
------------------------------------------
* Firstname Lastname: Francis Appels
* Age: 49
* Coming from (town, country): Herselt, Belgium
* Arrival date and hour: 16, 18h00
* Departure date and hour: 19, 21h00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: francis.appels@z-application.com
------------------------------------------
[[File:Marcos García.png|40px]]
* Firstname Lastname: Marcos García
* Age: 22
* Coming from (town, country): Valladolid, Spain
* Arrival date and hour: 16, TBD
* Departure date and hour: 19, TBD
* Transportation (Train/Bus/Car/Plane): Bus
* Food (Special diet, allergies, vegetarian…): Lactose.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): TBD
* Estimated expenses (ticket, parking, toll, hotel...): ~ 200 €
* Contact email: marcosgdf@gmail.com
------------------------------------------
* Firstname Lastname: Pierre-Yvan Aupiais
* Age: 59
* Coming from (town, country): Toulouse , France
* Arrival date and hour: 17/04/2015 , 9h00
* Departure date and hour: 18/04/2015 , 17h00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A
* Contact email:py.aupiais@val-talents.fr
-------------------------------------------
* Firstname Lastname: Estephe LORIDAN
* Age: 36 ans
* Coming from (town, country): Noisiel, France
* Arrival date and hour: Dont know yet, friday end of morning.
* Departure date and hour: Sunday evening.
* Transportation (Train/Bus/Car/Plane): Plane (my charge)
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): yes.
* Estimated expenses (ticket, parking, toll, hotel...): no expense.
* Contact email: dolibarr@estephe.me

DevCamp Pau April 2015 Organization

2015-03-28T14:01:06Z

Rdoursenaud: New registrations received by email from people without a wiki account

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
* '''Title: Dolibarr DevCamp 2015'''
* Date: april, 17 to 19
* Location: PAU, France
* Main language: French for public presentations on friday afternoon.
* Main language: French and english during devcamp

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc
* Lodging and Catering: ''TBD''
* Attendees information & communication: ''TBD''
* Sponsoring management: GPC.solutions / ''Dolibarr foundation?''

== Sponsors ==
* Technopole Hélioparc
* PauLLA
* ''More to be announced later''

== Partners ==
* La Mêlée Adour
* GRETA Béarn et Soule
* NumLab
* ''More to be announced later''

== Dates ==
April, 17 to 19

Registration deadline: '''march, 28'''

== Location ==
* Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France
* Capacity: ~20 people

== Accommodation and food ==
''To be defined''

= Planning =
''This is a'' '''Draft''' ''. It will be updated as soon as we have more informations.''
== Day 1 (Friday) ==
Auditorium
* 9:00: Breakfast (Organisers only)
* 10:00: Opening and free discussion
* 12:00: Lunch (Organisers and presenters only)
* 14:00: Start of general public presentations (''TBD'') - Presentation hall auditorium, programm here http://wiki.dolibarr.org/index.php/DevCamp_Pau_April_2015_Organisation#Presentations
* 18:00: Apéritif and buffet supper
Atelier numérique
* 21:00: Free play / code / hangout

== Day 2 (Saturday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Call for sponsors and general public presentations =
We'd like to spend the Friday afternoon with the general public.

We'd love having volunteers to hold a booth where visitors could try the software and discuss with open minded people.

We also need people who wants to talk about the project to a general audience in a more formal way.

Finally, skilled people that could pull off live streaming and/or remote attendance would be awesome!

Feel free to submit your ideas or get in touch with the event's organizers.

== Presentations ==
''This section is a draft listing current volunteers and their main subject.''

* '''Laurent Destailleur''':
** The project: history, features and ecosystem
** News in upcoming 3.7 and 3.8 versions
* '''Jean Heimburger''':
** Community
** E-commerce
* '''Florian Henry''':
** Custom attributes
** Agefodd
* '''Jean-François Ferry'''
** Feedback on preparing and using Dolibarr for the RMLL 2014 organization
* '''Raphaël Doursenaud''':
** ? (Not sure yet.)

* ''More to be announced later''

= Workshop topics =
If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

Lorenzo Novaro: I propose to have a "panel" about translations and a moment to revise the english language files.

= Attendees registration =
Registration is done here, on the wiki.

Please copy the template below to the registered attendees section and fill it with your informations.

You'll need a wiki account. If you don't have one please ask via email at '''contact@dolibarr.org'''.

== Registration template ==

------------------------------------------
* Firstname Lastname:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:
------------------------------------------

== Registered attendees ==

------------------------------------------
[[File:Raphaël Doursenaud.png|40px]]
* Firstname Lastname: [[Raphaël Doursenaud]]
* Age: 33
* Coming from (town, country): PAU, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Home :D
* Book hotel for me (yes/no): N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: rdoursenaud@gpcsolutions.fr
------------------------------------------
------------------------------------------
[[File:Florian_Henry.png|40px]]
* Firstname Lastname: [[Florian Henry]]
* Age: 34
* Coming from (town, country): MANDUEL, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: florian.henry@open-concept.pro
------------------------------------------
------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname: [[Jean Heimburger]]
* Age: 54
* Coming from (town, country): Sarrebourg
* Arrival date and hour: 17/04/2015 Pau Uzein 10h15 (depuis Orly)
* Departure date and hour: 19/04/2015 Pau Uzein 16h20
* Transportation (Train/Bus/Car/Plane): plane
* Food (Special diet, allergies, vegetarian…): none
* Accommodation (Common booked hotel/self…):hotel
* Book hotel for me (yes/no):yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:jean.heimburger@tiaris.info
------------------------------------------
------------------------------------------
* Firstname Lastname: [[Jean-François Ferry]]
* Age: 34
* Coming from (town, country): Montpellier, France
* Arrival date and hour: 17, morning
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel?
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: jfefe@aternatik.fr
------------------------------------------
------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 42
* Coming from (town, country): PESSAC
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Charles-Fr Benke]]
* Age: 47
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): GOOD
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charles.fr@benke.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------
------------------------------------------
[[File:Maxime Kohlhaas.png|40px]]
* Firstname Lastname: [[Maxime Kohlhaas]]
* Age: 28
* Coming from (town, country): Valence, France
* Arrival date and hour: 16, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hotel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: maxime@atm-consulting.fr
------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: Lorenzo Novaro
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation (Train/Bus/Car/Plane): Train/Plane
* Food (Special diet, allergies, vegetarian…): nuts
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 36
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation: Train/Plane
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): Transport: TBD - Hotel: TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Juanjo Menent.png|40px]]
* Firstname Lastname: [[Juanjo Menent]]
* Age: 42
* Coming from (town, country): Gandia, Spain
* Arrival date and hour: 16, 20h57
* Departure date and hour: 20, 05h53
* Transportation (Train/Bus/Car/Plane): Train
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: Hotel
* Book hotel for me: Yes
* Estimated expenses: Transport: 229.70€ - Hotel: 168€.
* Contact email: jmenent@2byte.es
------------------------------------------
[[File:Arnaud Aujon Chevallier.png|40px]]
* Firstname Lastname: [[Arnaud Aujon Chevallier]]
* Age: 26
* Coming from (town, country): Toulouse, France
* Arrival date and hour: 18, 10h00
* Departure date and hour: 18, 18h00
* Transportation (Train/Bus/Car/Plane): Car
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: self
* Book hotel for me: No
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: arnaud@intelibre.fr
------------------------------------------
* Firstname Lastname: Francis Appels
* Age: 49
* Coming from (town, country): Herselt, Belgium
* Arrival date and hour: 16, 18h00
* Departure date and hour: 19, 21h00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: francis.appels@z-application.com
------------------------------------------
[[File:Marcos García.png|40px]]
* Firstname Lastname: Marcos García
* Age: 22
* Coming from (town, country): Valladolid, Spain
* Arrival date and hour: 16, TBD
* Departure date and hour: 19, TBD
* Transportation (Train/Bus/Car/Plane): Bus
* Food (Special diet, allergies, vegetarian…): Lactose.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): TBD
* Estimated expenses (ticket, parking, toll, hotel...): ~ 200 €
* Contact email: marcosgdf@gmail.com
------------------------------------------
* Firstname Lastname: Pierre-Yvan Aupiais
* Age: 59
* Coming from (town, country): Toulouse , France
* Arrival date and hour: 17/04/2015 , 9h00
* Departure date and hour: 18/04/2015 , 17h00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A
* Contact email:py.aupiais@val-talents.fr
-------------------------------------------
* Firstname Lastname: Estephe LORIDAN
* Age: 36 ans
* Coming from (town, country): Noisiel, France
* Arrival date and hour: Dont know yet, friday end of morning.
* Departure date and hour: Sunday evening.
* Transportation (Train/Bus/Car/Plane): Plane (my charge)
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no): yes.
* Estimated expenses (ticket, parking, toll, hotel...): no expense.
* Contact email: dolibarr@estephe.me

DevCamp Pau April 2015 Organization

2015-03-26T19:20:06Z

Rdoursenaud: /* Partners */

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
* '''Title: Dolibarr DevCamp 2015'''
* Date: april, 17 to 19
* Location: PAU, France
* Main language: French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc
* Lodging and Catering: ''TBD''
* Attendees information & communication: ''TBD''
* Sponsoring management: GPC.solutions / ''Dolibarr foundation?''

== Sponsors ==
* Technopole Hélioparc
* PauLLA
* ''More to be announced later''

== Partners ==
* La Mêlée Adour
* GRETA Béarn et Soule
* NumLab
* ''More to be announced later''

== Dates ==
April, 17 to 19

Registration deadline: '''march, 28'''

== Location ==
* Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France
* Capacity: ~20 people

== Accommodation and food ==
''To be defined''

= Planning =
''This is a'' '''Draft''' ''. It will be updated as soon as we have more informations.''
== Day 1 (Friday) ==
Auditorium
* 9:00: Breakfast (Organisers only)
* 10:00: Opening and free discussion
* 12:00: Lunch (Organisers and presenters only)
* 14:00: Start of general public presentations (''TBD'')
* 18:00: Apéritif and buffet supper
Atelier numérique
* 21:00: Free play / code / hangout

== Day 2 (Saturday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Call for sponsors and general public presentations =
We'd like to spend the Friday afternoon with the general public.

We'd love having volunteers to hold a booth where visitors could try the software and discuss with open minded people.

We also need people who wants to talk about the project to a general audience in a more formal way.

Finally, skilled people that could pull off live streaming and/or remote attendance would be awesome!

Feel free to submit your ideas or get in touch with the event's organizers.

== Presentations ==
''This section is a draft listing current volunteers and their main subject.''

* '''Laurent Destailleur''':
** The project: history, features and ecosystem
** News in upcoming 3.7 and 3.8 versions
* '''Jean Heimburger''':
** Community
** E-commerce
* '''Florian Henry''':
** Custom attributes
** Agefodd
* '''Jean-François Ferry'''
** Feedback on preparing and using Dolibarr for the RMLL 2014 organization
* '''Raphaël Doursenaud''':
** ? (Not sure yet.)

* ''More to be announced later''

= Workshop topics =
If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

= Attendees registration =
Registration is done here, on the wiki.

Please copy the template below to the registered attendees section and fill it with your informations.

You'll need a wiki account. If you don't have one please ask via email at '''contact@dolibarr.org'''.

== Registration template ==

------------------------------------------
* Firstname Lastname:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:
------------------------------------------

== Registered attendees ==

------------------------------------------
[[File:Raphaël Doursenaud.png|40px]]
* Firstname Lastname: [[Raphaël Doursenaud]]
* Age: 33
* Coming from (town, country): PAU, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Home :D
* Book hotel for me (yes/no): N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: rdoursenaud@gpcsolutions.fr
------------------------------------------
------------------------------------------
[[File:Florian_Henry.png|40px]]
* Firstname Lastname: [[Florian Henry]]
* Age: 34
* Coming from (town, country): MANDUEL, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: florian.henry@open-concept.pro
------------------------------------------
------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname: [[Jean Heimburger]]
* Age: 54
* Coming from (town, country): Sarrebourg
* Arrival date and hour: 17/04/2015 Pau Uzein 10h15 (depuis Orly)
* Departure date and hour: 19/04/2015 Pau Uzein 16h20
* Transportation (Train/Bus/Car/Plane): plane
* Food (Special diet, allergies, vegetarian…): none
* Accommodation (Common booked hotel/self…):hotel
* Book hotel for me (yes/no):yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:jean.heimburger@tiaris.info
------------------------------------------
------------------------------------------
* Firstname Lastname: [[Jean-François Ferry]]
* Age: 34
* Coming from (town, country): Montpellier, France
* Arrival date and hour: 17, morning
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel?
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: jfefe@aternatik.fr
------------------------------------------
------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 42
* Coming from (town, country): PESSAC
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Charles-Fr Benke]]
* Age: 47
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): GOOD
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charles.fr@benke.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------
------------------------------------------
[[File:Maxime Kohlhaas.png|40px]]
* Firstname Lastname: [[Maxime Kohlhaas]]
* Age: 28
* Coming from (town, country): Valence, France
* Arrival date and hour: 16, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hotel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: maxime@atm-consulting.fr
------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: Lorenzo Novaro
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation (Train/Bus/Car/Plane): Train/Plane
* Food (Special diet, allergies, vegetarian…): nuts
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 36
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation: Train/Plane
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): Transport: TBD - Hotel: TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Juanjo Menent.png|40px]]
* Firstname Lastname: [[Juanjo Menent]]
* Age: 42
* Coming from (town, country): Gandia, Spain
* Arrival date and hour: 16, 16h00
* Departure date and hour: 20, 04h30
* Transportation (Train/Bus/Car/Plane): Train
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: Hotel
* Book hotel for me: Yes
* Estimated expenses (ticket, parking, toll, hotel...): TBD.
* Contact email: jmenent@2byte.es
------------------------------------------
[[File:Arnaud Aujon Chevallier.png|40px]]
* Firstname Lastname: [[Arnaud Aujon Chevallier]]
* Age: 26
* Coming from (town, country): Toulouse, France
* Arrival date and hour: 18, 10h00
* Departure date and hour: 18, 18h00
* Transportation (Train/Bus/Car/Plane): Car
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: self
* Book hotel for me: No
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: arnaud@intelibre.fr
------------------------------------------
* Firstname Lastname: Francis Appels
* Age: 49
* Coming from (town, country): Herselt, Belgium
* Arrival date and hour: 16, 18h00
* Departure date and hour: 19, 21h00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: francis.appels@z-application.com
------------------------------------------
[[File:Marcos García.png|40px]]
* Firstname Lastname: Marcos García
* Age: 22
* Coming from (town, country): Valladolid, Spain
* Arrival date and hour: 16, TBD
* Departure date and hour: 19, TBD
* Transportation (Train/Bus/Car/Plane): Bus
* Food (Special diet, allergies, vegetarian…): Lactose.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): TBD
* Estimated expenses (ticket, parking, toll, hotel...): ~ 200 €
* Contact email: marcosgdf@gmail.com

DevCamp Pau April 2015 Organization

2015-03-23T10:51:06Z

Rdoursenaud: For dumbasses that didn't use the template

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
* '''Title: Dolibarr DevCamp 2015'''
* Date: april, 17 to 19
* Location: PAU, France
* Main language: French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc
* Lodging and Catering: ''TBD''
* Attendees information & communication: ''TBD''
* Sponsoring management: GPC.solutions / ''Dolibarr foundation?''

== Sponsors ==
* Technopole Hélioparc
* PauLLA
* ''More to be announced later''

== Partners ==
* La Mêlée Adour
* NumLab
* ''More to be announced later''

== Dates ==
April, 17 to 19

Registration deadline: '''march, 28'''

== Location ==
* Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France
* Capacity: ~20 people

== Accommodation and food ==
''To be defined''

= Planning =
''This is a'' '''Draft''' ''. It will be updated as soon as we have more informations.''
== Day 1 (Friday) ==
Auditorium
* 9:00: Breakfast (Organisers only)
* 10:00: Opening and free discussion
* 12:00: Lunch (Organisers and presenters only)
* 14:00: Start of general public presentations (''TBD'')
* 18:00: Apéritif and buffet supper
Atelier numérique
* 21:00: Free play / code / hangout

== Day 2 (Saturday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Call for sponsors and general public presentations =
We'd like to spend the Friday afternoon with the general public.

We'd love having volunteers to hold a booth where visitors could try the software and discuss with open minded people.

We also need people who wants to talk about the project to a general audience in a more formal way.

Finally, skilled people that could pull off live streaming and/or remote attendance would be awesome!

Feel free to submit your ideas or get in touch with the event's organizers.

== Presentations ==
''This section is a draft listing current volunteers and their main subject.''

* '''Laurent Destailleur''':
** The project: history, features and ecosystem
** News in upcoming 3.7 and 3.8 versions
* '''Jean Heimburger''':
** Community
** E-commerce
* '''Florian Henry''':
** Custom attributes
** Agefodd
* '''Jean-François Ferry'''
** Feedback on preparing and using Dolibarr for the RMLL 2014 organization
* '''Raphaël Doursenaud''':
** ? (Not sure yet.)

* ''More to be announced later''

= Workshop topics =
If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

= Attendees registration =
Registration is done here, on the wiki.

Please copy the template below to the registered attendees section and fill it with your informations.

You'll need a wiki account. If you don't have one please ask via email at '''contact@dolibarr.org'''.

== Registration template ==

------------------------------------------
* Firstname Lastname:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:
------------------------------------------

== Registered attendees ==

------------------------------------------
[[File:Raphaël Doursenaud.png|40px]]
* Firstname Lastname: [[Raphaël Doursenaud]]
* Age: 33
* Coming from (town, country): PAU, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Home :D
* Book hotel for me (yes/no): N.A.
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: rdoursenaud@gpcsolutions.fr
------------------------------------------
------------------------------------------
[[File:Florian_Henry.png|40px]]
* Firstname Lastname: [[Florian Henry]]
* Age: 34
* Coming from (town, country): MANDUEL, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: florian.henry@open-concept.pro
------------------------------------------
------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname: [[Jean Heimburger]]
* Age: 54
* Coming from (town, country): Sarrebourg
* Arrival date and hour: 17/04/2015 Pau Uzein 10h15 (depuis Orly)
* Departure date and hour: 19/04/2015 Pau Uzein 16h20
* Transportation (Train/Bus/Car/Plane): plane
* Food (Special diet, allergies, vegetarian…): none
* Accommodation (Common booked hotel/self…):hotel
* Book hotel for me (yes/no):yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:jean.heimburger@tiaris.info
------------------------------------------
------------------------------------------
* Firstname Lastname: [[Jean-François Ferry]]
* Age: 34
* Coming from (town, country): Montpellier, France
* Arrival date and hour: 17, morning
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel?
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: jfefe@aternatik.fr
------------------------------------------
------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 42
* Coming from (town, country): PESSAC, Pau
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Charles-Fr Benke]]
* Age: 47
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): GOOD
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charles.fr@benke.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------
------------------------------------------
[[File:Maxime Kohlhaas.png|40px]]
* Firstname Lastname: [[Maxime Kohlhaas]]
* Age: 28
* Coming from (town, country): Valence, France
* Arrival date and hour: 16, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hotel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: maxime@atm-consulting.fr
------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: Lorenzo Novaro
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation (Train/Bus/Car/Plane): Train/Plane
* Food (Special diet, allergies, vegetarian…): nuts
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 36
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation: Train/Plane
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): Transport: TBD - Hotel: TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Juanjo Menent.png|40px]]
* Firstname Lastname: [[Juanjo Menent]]
* Age: 42
* Coming from (town, country): Gandia, Spain
* Arrival date and hour: 16, 16h00
* Departure date and hour: 20, 04h30
* Transportation (Train/Bus/Car/Plane): Train
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: Hotel
* Book hotel for me: Yes
* Estimated expenses (ticket, parking, toll, hotel...): TBD.
* Contact email: jmenent@2byte.es
------------------------------------------
[[File:Arnaud Aujon Chevallier.png|40px]]
* Firstname Lastname: [[Arnaud Aujon Chevallier]]
* Age: 26
* Coming from (town, country): Toulouse, France
* Arrival date and hour: 18, 10h00
* Departure date and hour: 18, 18h00
* Transportation (Train/Bus/Car/Plane): Car
* Food:(Special diet, allergies, vegetarian…): N.A.
* Accommodation: self
* Book hotel for me: No
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: arnaud@intelibre.fr
------------------------------------------
* Firstname Lastname: Francis Appels
* Age: 49
* Coming from (town, country): Herselt, Belgium
* Arrival date and hour: 16, 18h00
* Departure date and hour: 19, 21h00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): hotel
* Book hotel for me (yes/no): no
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: francis.appels@z-application.com

DevCamp Pau April 2015 Organization

2015-03-12T15:34:51Z

Rdoursenaud: Added jfefe's presentation

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
* '''Title: Dolibarr DevCamp 2015'''
* Date: april, 17 to 19
* Location: PAU, France
* Main language: French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc
* Lodging and Catering: ''TBD''
* Attendees information & communication: ''TBD''
* Sponsoring management: GPC.solutions / ''Dolibarr foundation?''

== Sponsors ==
* Technopole Hélioparc
* PauLLA
* ''More to be announced later''

== Partners ==
* La Mêlée Adour
* NumLab
* ''More to be announced later''

== Dates ==
April, 17 to 19

Registration deadline: '''march, 28'''

== Location ==
* Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France
* Capacity: ~20 people

== Accommodation and food ==
''To be defined''

= Planning =
''This is a'' '''Draft''' ''. It will be updated as soon as we have more informations.''
== Day 1 (Friday) ==
Auditorium
* 9:00: Breakfast (Organisers only)
* 10:00: Opening and free discussion
* 12:00: Lunch (Organisers and presenters only)
* 14:00: Start of general public presentations (''TBD'')
* 18:00: Apéritif and buffet supper
Atelier numérique
* 21:00: Free play / code / hangout

== Day 2 (Saturday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Call for sponsors and general public presentations =
We'd like to spend the Friday afternoon with the general public.

We'd love having volunteers to hold a booth where visitors could try the software and discuss with open minded people.

We also need people who wants to talk about the project to a general audience in a more formal way.

Finally, skilled people that could pull off live streaming and/or remote attendance would be awesome!

Feel free to submit your ideas or get in touch with the event's organizers.

== Presentations ==
''This section is a draft listing current volunteers and their main subject.''

* '''Laurent Destailleur''':
** The project: history, features and ecosystem
** News in upcoming 3.7 and 3.8 versions
* '''Jean Heimburger''':
** Community
** E-commerce
* '''Florian Henry''':
** Custom attributes
** Agefodd
* '''Jean-François Ferry'''
** Feedback on preparing and using Dolibarr for the RMLL 2014 organization
* '''Raphaël Doursenaud''':
** ? (Not sure yet.)

* ''More to be announced later''

= Workshop topics =
If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

= Attendees registration =
Registration is done here, on the wiki.

Please copy the template below to the registered attendees section and fill it with your informations.

You'll need a wiki account. If you don't have one please ask via email at '''contact@dolibarr.org'''.

== Registration template ==

------------------------------------------
* Firstname Lastname:
* Age:
* Coming from (town, country):
* Arrival date and hour:
* Departure date and hour:
* Transportation (Train/Bus/Car/Plane):
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:
------------------------------------------

== Registered attendees ==

------------------------------------------
[[File:Raphaël Doursenaud.png|40px]]
* Firstname Lastname: [[Raphaël Doursenaud]]
* Age: 33
* Coming from (town, country): PAU, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Home :D
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: rdoursenaud@gpcsolutions.fr
------------------------------------------
------------------------------------------
[[File:Florian_Henry.png|40px]]
* Firstname Lastname: [[Florian Henry]]
* Age: 34
* Coming from (town, country): MANDUEL, France
* Arrival date and hour: 17, 9h00
* Departure date and hour: 19, 23h59
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: florian.henry@open-concept.pro
------------------------------------------
------------------------------------------
[[File:Jean_Heimburger.png|40px]]
* Firstname Lastname: [[Jean Heimburger]]
* Age: 54
* Coming from (town, country): Sarrebourg
* Arrival date and hour: 17/04/2015
* Departure date and hour: 19/04/2015
* Transportation (Train/Bus/Car/Plane): plane/train ?
* Food (Special diet, allergies, vegetarian…):
* Accommodation (Common booked hotel/self…):hotel
* Book hotel for me (yes/no):yes
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email:jean.heimburger@tiaris.info
------------------------------------------
------------------------------------------
* Firstname Lastname: [[Jean-François Ferry]]
* Age: 34
* Coming from (town, country): Montpellier, France
* Arrival date and hour: 17, morning
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel?
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: jfefe@aternatik.fr
------------------------------------------
------------------------------------------
[[File:Laurent Destailleur.png|40px]]
* Firstname Lastname: [[Laurent Destailleur]]
* Age: 42
* Coming from (town, country): PESSAC, Pau
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hostel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: contact@destailleur.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Charles-Fr Benke]]
* Age: 47
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): GOOD
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: charles.fr@benke.fr
------------------------------------------
------------------------------------------
Firstname Lastname: [[Romain Deschamps]]
* Age: 35
* Coming from (town, country): Lyon France
* Arrival date and hour: 17, 12h00
* Departure date and hour: 19, late
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…): Hotel
* Book hotel for me (yes/no): No
* Estimated expenses (ticket, parking, toll, hotel...):
* Contact email: r.deschamps@patas-monkey.com
------------------------------------------
------------------------------------------
[[File:Maxime Kohlhaas.png|40px]]
* Firstname Lastname: [[Maxime Kohlhaas]]
* Age: 28
* Coming from (town, country): Valence, France
* Arrival date and hour: 16, 12h00
* Departure date and hour: 19, 15h00
* Transportation (Train/Bus/Car/Plane): Car
* Food: N.A.
* Accommodation: Hotel
* Estimated expenses (ticket, parking, toll, hotel...): N.A.
* Contact email: maxime@atm-consulting.fr
------------------------------------------
[[File:Lorenzo Novaro.png|40px]]
* Firstname Lastname: Lorenzo Novaro
* Age: 35
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation (Train/Bus/Car/Plane): Train/Plane
* Food (Special diet, allergies, vegetarian…): nuts
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): TBD
* Contact email: info@19.coop
------------------------------------------
[[File:Firstname Lastname.png|40px]]
* Firstname Lastname: [[Tommaso Basilici]]
* Age: 36
* Coming from (town, country): Genova, Italy
* Arrival date and hour: TBD
* Departure date and hour: 19, end of devcamp
* Transportation: Train/Plane
* Food (Special diet, allergies, vegetarian…): N.A.
* Accommodation (Common booked hotel/self…):
* Book hotel for me (yes/no):
* Estimated expenses (ticket, parking, toll, hotel...): Transport: TBD - Hotel: TBD
* Contact email: info@19.coop

DevCamp Pau April 2015 Organization

2015-03-05T10:09:22Z

Rdoursenaud: Better transcription

DevCamp Pau April 2015 Organization

2015-03-05T10:07:53Z

Rdoursenaud: Added received presentations subjects

DevCamp Pau April 2015 Organization

2015-03-04T16:20:39Z

Rdoursenaud: Added presentations volunteers

DevCamp Pau April 2015 Organization

2015-03-04T11:07:48Z

Rdoursenaud: /* Attendees registration */

DevCamp Pau April 2015 Organization

2015-03-04T11:02:22Z

Rdoursenaud: /* Dates */

DevCamp Pau April 2015 Organization

2015-03-04T10:40:13Z

Rdoursenaud: /* Registered attendees */

DevCamp Pau April 2015 Organization

2015-03-04T10:38:08Z

Rdoursenaud: Added food to registration template

DevCamp Pau April 2015 Organization

2015-03-04T10:35:00Z

Rdoursenaud: Openned registrations

DevCamp Pau April 2015 Organization

2015-03-04T10:26:45Z

Rdoursenaud:

DevCamp Pau April 2015 Organization

2015-03-04T09:58:41Z

Rdoursenaud: Capacity update

DevCamp Pau April 2015 Organization

2015-03-04T09:55:33Z

Rdoursenaud: Sponsors and partners update

DevCamp Pau April 2015 Organization

2015-03-04T09:47:26Z

Rdoursenaud: Registration deadline update

Widget system

2015-02-16T14:07:55Z

Rdoursenaud: Tried to clarify some terms

[[Category:Core]]
{{TemplateDocDevEn}}

A box is a rectangular area that can be displayed on some pages (only the home page for moment). These are described by files in a specific directory.

Boxes content is left to the developer's imagination (graphics, text, tables, …) but a basic framework allows for easy table based presentation.

= [[File:art.png]] Create a new box =

Every standard box is stored inside the '''htdocs/core/boxes''' directory.

There is one file for each box.

Each file is a class inherited from the '''ModeleBoxes''' class.

To create a new box, you may copy an existing box file, rename it, for example to '''box_myownbox.php''' and change its content to match the new name.

You can now define the informations you want to show inside the box.

However if you plan distributing your box to other users, you must create a module and store your box files inside your module.
* Go to [[Module development]] page to learn how to create a module
* Create your box file into '''htdocs/mymodule/core/boxes/'''
* Once your module descriptor is created, add these lines to declare your box file
<source lang="php">
$this->boxes = array(
0 => array(
'file' => 'box_myownbox@mymodule',
'note' => 'My notes',
'enabledbydefaulton' => 'Home'
)
// You can declare as much boxes as you want by simply incrementing the index.
);
</source>
* For distribution, package the module containing your box (See [[Module development]] page).

= [[File:art.png]] Activate a box =

To activate a box, go to '''Home - Setup - Boxes''' page and click activate on the box you want to see.

It will be displayed on the page for which you have activated the box.

DevCamp Pau April 2015 Organization

2015-02-04T10:58:20Z

Rdoursenaud: Dates

Subscription amount Dolibarr Foundation

2015-01-22T17:17:18Z

Rdoursenaud: Fixed franglish

{{TemplateFoundation}}
[[Category:Foundation]]
Here you will find Dolibarr association minimum subscription fee depending on your status.

= Natural persons =
This is when you subscribe for yourself.

Minimum subscription fee for natural persons is:
'''20 € minimum'''.

= Moral persons =
If your subscription is for your company, association or university the fee depends on the institution characteristics.

==Companies==
Subscription fee depends on the turnover:
* Turnover lower than 100 000 € : subscription is '''50 €'''
* Turnover from 100 000 to 200 000 € : subscription is '''100 €'''
* Turnover from 200 000 to 500 000 € : subscription is '''200 €'''
* Turnover from 500 000 to 1.5 millions € : subscription is '''300 €'''
* Turnover from 1.5 to 3 millions € : subscription is '''600 €'''
* Turnover from 3 to 5 millions € : subscription is '''1 000 €'''
* Turnover higher than 5 millions € : subscription is '''2 000 €'''

==Associations==
Subscription fee depends on the budget:
* Budget lower than 100 000 € : subscription is '''50 €'''
* Budget from 100 000 € to 200 000 € : subscription is '''100 €'''
* Budget from 200 000 € to 500 000 € : subscription is '''200 €'''
* Budget from 500 000 € to 1.5 millions € : subscription is '''300 €'''
* Budget from 1.5 to 3 millions € : subscription is '''600 €'''
* Budget from 3 to 5 millions € : subscription is '''1 000 €'''
* Budget higher than 5 millions € : subscription is '''2 000 €'''

== Other ==
For towns, universities and any other institutions subscription is '''100€'''.

Subscription amount Dolibarr Foundation

2015-01-22T17:15:27Z

Rdoursenaud: Fixed franglish

{{TemplateFoundation}}
[[Category:Foundation]]
You will find here minimum amount for subscriptions to the Dolibarr foundation, depending on your status.

= Natural persons =
This is when you subscribe for yourself.

Minimum subscription fee for natural persons is:
'''20 € minimum'''.

= Moral persons =
If your subscription is for your company, association or university the fee depends on the institution characteristics.

==Companies==
Subscription fee depends on the turnover:
* Turnover lower than 100 000 € : subscription is '''50 €'''
* Turnover from 100 000 to 200 000 € : subscription is '''100 €'''
* Turnover from 200 000 to 500 000 € : subscription is '''200 €'''
* Turnover from 500 000 to 1.5 millions € : subscription is '''300 €'''
* Turnover from 1.5 to 3 millions € : subscription is '''600 €'''
* Turnover from 3 to 5 millions € : subscription is '''1 000 €'''
* Turnover higher than 5 millions € : subscription is '''2 000 €'''

==Associations==
Subscription fee depends on the budget:
* Budget lower than 100 000 € : subscription is '''50 €'''
* Budget from 100 000 € to 200 000 € : subscription is '''100 €'''
* Budget from 200 000 € to 500 000 € : subscription is '''200 €'''
* Budget from 500 000 € to 1.5 millions € : subscription is '''300 €'''
* Budget from 1.5 to 3 millions € : subscription is '''600 €'''
* Budget from 3 to 5 millions € : subscription is '''1 000 €'''
* Budget higher than 5 millions € : subscription is '''2 000 €'''

== Other ==
For towns, universities and any other institutions subscription is '''100€'''.

Subscription amount Dolibarr Foundation

2015-01-22T17:12:36Z

Rdoursenaud: Fixed franglish

{{TemplateFoundation}}
[[Category:Foundation]]
You will find here minimum amount for subscriptions to the Dolibarr foundation, depending on your status.

= Natural persons =
This is when you subscribe for yourself.

Minimum subscription fee for natural persons is:
'''20 € minimum'''.

= Moral persons =
If your subscription is for your company, foundation, university, the amount depends on characteristics of this company, foundation or university.

==Companies==
Subscription amount depends on company's turnover :
* Turnover lower than 100 000 € : subscription is '''50 €'''
* Turnover from 100 000 to 200 000 € : subscription is '''100 €'''
* Turnover from 200 000 to 500 000 € : subscription is '''200 €'''
* Turnover from 500 000 to 1.5 millions € : subscription is '''300 €'''
* Turnover from 1.5 to 3 millions € : subscription is '''600 €'''
* Turnover from 3 to 5 millions € : subscription is '''1 000 €'''
* Turnover higher than 5 millions € : subscription is '''2 000 €'''

==Associations==
For associations the subscription fee depends on your budget :
* Budget lower than 100 000 € : subscription is '''50 €'''
* Budget from 100 000 € to 200 000 € : subscription is '''100 €'''
* Budget from 200 000 € to 500 000 € : subscription is '''200 €'''
* Budget from 500 000 € to 1.5 millions € : subscription is '''300 €'''
* Budget from 1.5 to 3 millions € : subscription is '''600 €'''
* Budget from 3 to 5 millions € : subscription is '''1 000 €'''
* Budget higher than 5 millions € : subscription is '''2 000 €'''

== Other ==
For towns, universities and any other institutions, subscription is '''100€'''.

Subscription amount Dolibarr Foundation

2015-01-22T17:11:20Z

Rdoursenaud: Foundations and associations are not the same institutions

{{TemplateFoundation}}
[[Category:Foundation]]
You will find here minimum amount for subscriptions to the Dolibarr foundation, depending on your status.

= Physical persons =
This is when you subscribe for yourself.

Minimum amount of subscription for physical persons is:
'''20 € minimum'''.

= Moral persons =
If your subscription is for your company, foundation, university, the amount depends on characteristics of this company, foundation or university.

==Companies==
Subscription amount depends on company's turnover :
* Turnover lower than 100 000 € : subscription is '''50 €'''
* Turnover from 100 000 to 200 000 € : subscription is '''100 €'''
* Turnover from 200 000 to 500 000 € : subscription is '''200 €'''
* Turnover from 500 000 to 1.5 millions € : subscription is '''300 €'''
* Turnover from 1.5 to 3 millions € : subscription is '''600 €'''
* Turnover from 3 to 5 millions € : subscription is '''1 000 €'''
* Turnover higher than 5 millions € : subscription is '''2 000 €'''

==Associations==
For associations the subscription fee depends on your budget :
* Budget lower than 100 000 € : subscription is '''50 €'''
* Budget from 100 000 € to 200 000 € : subscription is '''100 €'''
* Budget from 200 000 € to 500 000 € : subscription is '''200 €'''
* Budget from 500 000 € to 1.5 millions € : subscription is '''300 €'''
* Budget from 1.5 to 3 millions € : subscription is '''600 €'''
* Budget from 3 to 5 millions € : subscription is '''1 000 €'''
* Budget higher than 5 millions € : subscription is '''2 000 €'''

== Other ==
For towns, universities and any other institutions, subscription is '''100€'''.

DevCamp Pau April 2015 Organization

2015-01-21T11:31:09Z

Rdoursenaud: Added link to dates survey

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
* '''Title: Dolibarr DevCamp 2015'''
* Date: ''To be defined''
* Location: PAU, France
* Main language: French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc
* Lodging and Catering: ''TBD''
* Attendees information & communication: ''TBD''
* Sponsoring management: GPC.solutions / ''Dolibarr foundation?''

== Sponsors ==
* Technopole Hélioparc
* ''More to be announced later''

== Dates ==
''To be defined''
* Tentative dates: end of week 16 or 17 (april, 17 to 19 or 24 to 26)
A [http://asso.dolibarr.org/dolibarr/opensurvey/public/studs.php?sondage=bohz9x6ioyowikf9 survey] is available for you to vote on your preferred dates.
* Registration deadline: ''TBD''

== Location ==
* Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France
* Capacity: ''TBD''

== Accommodation and food ==
''To be defined''

= Planning =
''This is a'' '''Draft''' ''. It will be updated as soon as we have more informations.''
== Day 1 (Friday) ==
Auditorium
* 9:00: Breakfast
* 10:00: Opening and free discussion
* 14:00: Start of general public presentations (''TBD'')
* 18:00: Apéritif and buffet supper
Atelier numérique
* 21:00: Free play / code / hangout

== Day 2 (Saturday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Call for sponsors and general public presentations =
We'd like to spend the Friday afternoon with the general public.

We'd love having volunteers to hold a booth where visitors could try the software and discuss with open minded people.

We also need people who wants to talk about the project to a general audience in a more formal way.

Finally, skilled people that could pull off live streaming and/or remote attendance would be awesome!

Feel free to submit your ideas or get in touch with the event's organizers.

= Workshop topics =
If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

= Attendees registration =
''Not opened yet''

DevCamps Organization

2015-01-21T11:28:44Z

Rdoursenaud: Review and franglish corrections

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

This page lists typical actions needed to organise a DevCamp. You can also use it as a template to start organization of a particular devcamp.

= Why =
== What is a DevCamp ==
Most of the time a DevCamp is a meeting between all kind of contributors around a specific technologies to provide training, remind best practice, exchange non formal information, massively improve a product.
Commonly a DevCamp is on a short time range, like a week-end or a week during manifestation.

== Who can come to a DevCamp ==
All kind of contributors (developers, translators, documentation writers) can come to a DevCamp. A leader is designated to schedule the program.
Expert and senior members will indicate and communicate about the technologies and help beginners.

== What kind topic at DevCamp ==
* Training
* Special feature to build (may be the goal of a DevCamp)
* Update project documentation

= Organization =
To start a devcamp organization, first thing to do is to create a wiki page with answers to several questions.
To save time, you can copy an existing page of a past camp (for example [[HackWeek_2010_Organisation]]) or use the generic template that follows.

== Title ==
Choose a name for the event. For example DevCamp Dolibarr 2013, Hackweek 2010, DoliMeeting summer 2013, …
* Event Name of: ___________
* Main language used: _______ (french, english ?)

== Organizers ==
Define name of organizers and managers (may be the same guys):
* Location manager: _____________
* Food manager: ____________
* Communication manager: _____________
* Sponsor manager (not mandatory): _____________

== Dates ==
Event dates and duration must be defined (one day, two days, three…).
But also limit date for subscriptions.

== Location ==
* Be sure the location where you want to organize is ok regarding security, mobility and insurance.
* Following data must be defined:
** Location for food: ________________________ (provide name of room or address for lunch. Better with link to openstreetmap)
** Location for bedrooms: ____________________ (provide address of sleeping rooms or nearest hotels. Better with link to openstreetmap)
** chairs: _____________
** tables: _____________
** video projector: _____________

== Planning suggestion ==
* Define a suggestion of Planning

= Participants planned =
Please enter here your record if you plan to be present to this devcamp. You need a wiki account. If you don't have it yet, send an email to '''contact@dolibarr.org''' to ask one.

------------------------------------------
* Lastname Firstname: _______________________
* Age: _________
* Coming from (town, country): ___________________
* Arrival date and hour: ____________
* Departure date and hour: ______________
* Underage: Yes or no
* Transportation: ____________
* Lodging: __________
* Estimated price of trip (ticket, parking, toll, lodging...): ________
* Email for contact: ____________________
------------------------------------------

= TODO Checklist =

== Launch communication ==
# Initiate wiki page following previous template
# Start to fill it with name, dates, places
# Submit page to the Dolibarr foundation board team to complete, feedbacks...
# Once feedbacks are enough, the responsible of communication launch communication to ask people to register to devcamp add their name into wiki page of the devcamp, providing the limit date to apply. Posting should be done onto the follwoing channels:
* Dolibarr foundation mailing list: dolibarr-association@nongnu.org
* Dolibarr developer mailing list: dolibarr-dev@nongnu.org
* Dolibarr portals (http://www.dolibarr.org in english, http://www.dolibarr.fr in french, http://www.dolibarr.es in spanish). This should also automatically push information onto facebook and twitter.
* Add event into http://www.agendadulibre.org
* Post a dedicated news onto http://www.linuxfr.org
# According the number of attendes, be sure the place you think about is the right one. Also be sure to provide at least some food, and lot's of coffee and tea. It's a well know fact, coders transform caffeine into code lines.
# Once devcamp is finished, build a page to show everybody what happened. An example can be found here: [[Compte_rendu_Hackweek_2010]].

== Sponsoring ==
Some sponsors can contribute to sponsor/fund the event.

== Example of past and next DevCamps ==
See page [[:Category:DevCamps]]

DevCamp Pau April 2015 Organization

2015-01-07T11:01:14Z

Rdoursenaud: First public anouncement

__NOINDEX__
{{TemplateAssoEn}}
[[Category:DevCamps]]

= Event =
* '''Title: Dolibarr DevCamp 2015'''
* Date: ''To be defined''
* Location: PAU, France
* Main language: French

== Organizers ==
* Main: GPC.solutions (contact@gpcsolutions.fr)
* Hosting: Technopole Hélioparc
* Lodging and Catering: ''TBD''
* Attendees information & communication: ''TBD''
* Sponsoring management: GPC.solutions / ''Dolibarr foundation?''

== Sponsors ==
* Technopole Hélioparc
* ''More to be announced later''

== Dates ==
''To be defined''
* Tentative dates: end of week 16 or 17 (april, 17 to 19 or 24 to 26)
* Registration deadline: ''TBD''

== Location ==
* Main location: Technopole Hélioparc, 2 avenue du Président Pierre Angot, 64000 PAU, France
* Capacity: ''TBD''

== Accommodation and food ==
''To be defined''

= Planning =
''This is a'' '''Draft''' ''. It will be updated as soon as we have more informations.''
== Day 1 (Friday) ==
Auditorium
* 9:00: Breakfast
* 10:00: Opening and free discussion
* 14:00: Start of general public presentations (''TBD'')
* 18:00: Apéritif and buffet supper
Atelier numérique
* 21:00: Free play / code / hangout

== Day 2 (Saturday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 19:00: Diner
* 21:00: Free play / code / hangout

== Day 3 (Sunday) ==
Atelier numérique
* 9:00: Breakfast
* 10:00: Community time (''TBD'')
* 12:00: Lunch
* 14:00: Community time (''TBD'')
* 18:00: Event end

= Call for sponsors and general public presentations =
We'd like to spend the Friday afternoon with the general public.

We'd love having volunteers to hold a booth where visitors could try the software and discuss with open minded people.

We also need people who wants to talk about the project to a general audience in a more formal way.

Finally, skilled people that could pull off live streaming and/or remote attendance would be awesome!

Feel free to submit your ideas or get in touch with the event's organizers.

= Workshop topics =
If you plan attending the event on saturday and sunday, feel free to share the topics you'd like to see covered.

= Attendees registration =
''Not opened yet''

Language and development rules

2014-12-29T14:09:21Z

Rdoursenaud: Reverted edits by Cbenke (talk) to last revision by Eldy

{{TemplateDocDevEn}}

This is some rules on language, syntax and norm we use into Dolibarr project:

= Versions =
* Dolibarr must works on:
# All OS (Windows, Linux, MACOS...)
# PHP {{PHPMinVersion}} (Must works with no need of complementary PHP module, except module to PHP module to access database).
# Mysql {{MySqlMinVersion}}

= Copyright Norms =
* All PHP files must start with a header that looks like
<source lang="php">
<?php
/* Copyright (C) YYYY John Doe <email@email.com>
*
* Licence information
*/
...
</source>
When you edit an existing file of project, you must add a Copyright line under others.

= PHP Norms =
* Dolibarr is written with PHP and supports all PHP version higher than {{PHPMinVersion}}. All files must end with extension .php

* Usage of superglobals PHP variables must use dedicated operators $_COOKIES, $_SERVER, $_ENV but use Dolibarr function GETPOST() to get content of $_GET or $_POST..
Other operators ($HTTP_SERVER_GET, ...) are now deprecated inside PHP, so they must no more be used. Like that code will works alos if option '''register_long_arrays''' is to off.
Moreover, the code must works when PHP option '''register_globals''' is off (recommended by PHP). It must works the same way that when option '''register_globals''' is on (by default on a lot of installations).

* Do not use '''PHP_SELF'''. Use instead $_SERVER["PHP_SELF"].

* When several variables must be initialized with same value, you must use several lines
<source lang="php">
$var1=1;$var2=1;$var3=1;
</source>
instead of
<source lang="php">
$var1=$var2=$var3=1;
</source>
that is slower.

* String must be rounded by simple quote and variable inside string must be out of the quote.
<source lang="php">
print 'My text show my '.$variable.' !';
</source>

* Comments must use the C syntax, ie a double anti-slash for a comment on one line and a slash-star to open a bloc for several lines
<source lang="php">
/* Bloc of comment
*
* End of bloc
*/

$monobjet = new MonObjet($db);
$result=$monobjet->fetch($idobject);

for ($i = 1 , $i < 2 ; $i++)
{
// comment on one line
print $i;
}

</source>

* Functions must return a value strictly higher than 0 if successful and strictly lower than 0 if error.

* No dead code (code never used) into Dolibarr core code (code used by external modules only must be included into external modules).

* Use "include_once" for anything with functions or class definitions in it (so *.class.php and *.lib.php files), use "include" for template-style php with files containing a mix of HTML and PHP (so *.inc.php and *.tpl.php files).

* Coding style to use is the PSR-2 (https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md) with 2 exceptions, this means:
** Files must be saved with Unix format (LF) and not Windows (CR/LF). Unif format is compatible on all OS like Unix like, Windows, Mac, but the Windows text file format is no working on some PHP under Unix.
** Smart tags PHP are not used. PHP code section must start with '''<?php'''
** But there is an exception of length of line: We accept more than 80 characters per line. 80 is really to low. In most cases, we never go over 80, but sometimes (when declaring a list of reference arrays, like into module descriptor files), it is better to have long lines instead of long page with code content that is just data declaration and does not contains any logic.
** The other exception is that we don't replace the tab with space. This makes lot of editor crazy and breaks some auto-format features.
You can use the file dev/codesniffer/ruleset.xml as rule file to control coding style with PHPCodeSniffer.

= SQL rules =

== Table structures ==

* Structure of tables.
When you create a new table, it is recommended to use the same conventions as other Dolibarr tables. This means the following fields:
- rowid integer for id
- tms timestamp that will contain date of last modification (the database manages this field automatically, no need to manage it by the code, just create the field)
- import_key that will contains the import code YYYYMMDDHHMMSS if you make mass import.
Eventualy
- datec timestamp that is the creation date
- fk_user_creat integer that is the id of user making creation
- fk_user_modif integer that is the id of user making change

Note field:
- note_private text for private comment of the object
- note_pubic text for public comment of the object
or
- note text if there is no need to have private and public

* Type of fields:
Well, to be compatible with any accuracy required by any country on amounts, and with any database syntax, we will use the following type into database:
- integer for an any of foreign key
- double(24,8) for any amount
- double(6,3) for any vat rate
- real for a quantity
- varchar for a string (also if length is 1, the type char is more and more deprecated)
- timestamp for a field date+time that is automatically updated
- datetime for a field date+time
- date for a field date

* All tables has a prefix to avoid name conflicts with other projects. In current version this prefix is fixed ans can't be modified. Its value is <tt>llx_</tt>. In a future version this value should be modified during installation process.

== Primary keys ==
The primary key of a table must be called <tt>rowid</tt>.

Some old tables does not use this rule and use a primary key called <tt>id</tt> (ie [[Table llx_c_actioncomm]]), but the reason is history and this should not happens anymore.

== Foreign keys ==
A foreign key name must start with prefix <tt>fk_</tt> followed by the table name linked (this is required to avoid duplicate names in project that are not allowed even if on different tables by some DBMS like Postgresql) then the name of child field (this is to allow to have several foreign keys on same table).

Example:
''fk_facture_fourn_fk_soc'' is a foreign key on table llx_facture_fourn for field fk_soc in this table (that link to the rowid field in another table)

Note: If you develop your own external module, it must have no foreign keys that point to Dolibarr standard tables. This will break standard dolibarr upgrades, repair, backup and restore tools and may also break standard features.

== Alternative keys ==
Sometimes, we need another unique keys than primary key. We can add in this case an alternate unique key. When we need this, we can create an alternate unique key. Such an index is called by a name that start by prefix <tt>uk_</tt> followed by an underscore, then the the table name (this is required to avoid duplicate names of unique keys that may create problems for some DBMS like Postgresql) and then another string to define the key (this is to allow to have several unique keys on same table).

Example:
''uk_societe_code_client'' is a unique key on table llx_societe on field code_client.

== Index performance ==
Some fields are often used as search or order criteria, or for joins. In such case, we need to set a performance index on field to increase performances. Such indexes are named with a prefix <tt>idx_</tt> then the table name and then the field name.

Example:
''idx_societe_user_creat'' is a performance index on table llx_societe for field user_creat

== DDL file format ==
Files that contain definition of the database structure (DDL files) must be 2 per tables:
* Each table is defined by its own file whose name is <tt>llx_''mytable''.sql</tt>
A comment will be added on each field to explain its usage.
* All foreign keys, performance indexes or other constraints will be defined into another file called <tt>llx_''mytable''.key.sql</tt>

Those files must be stored into directory '''install/mysql/tables''' for all standard files or '''mymodule/tables''' for tables provided by an external module.

Example '''file of table llx_mytable.sql''':

<source lang="sql">
-- ===========================================================================
-- Copyright (C) 2013 Author <email@author.com>
--
-- This program is free software; you can redistribute it and/or modify
-- it under the terms of the GNU General Public License as published by
-- the Free Software Foundation; either version 3 of the License, or
-- (at your option) any later version.
--
-- This program is distributed in the hope that it will be useful,
-- but WITHOUT ANY WARRANTY; without even the implied warranty of
-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-- GNU General Public License for more details.
--
-- You should have received a copy of the GNU General Public License
-- along with this program. If not, see <http://www.gnu.org/licenses/>.
-- ===========================================================================

create table llx_mytable
(
rowid integer NOT NULL AUTO_INCREMENT PRIMARY KEY,
ref varchar(30) NOT NULL, -- object reference number
entity integer DEFAULT 1 NOT NULL, -- multi company id
ref_ext varchar(255),-- reference into an external system (not used by dolibarr)
field_one integer,
field_two integer NOT NULL,
fk_field integer,
field_date datetime,
datec timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,, -- creation datetime
tms timestamp, -- update time stamp
fk_user_author integer NOT NULL, -- Author, foreign key of llx_user
fk_user_mod integer NOT NULL, -- Last updater, foreign key of llx_user
import_key varchar(14) -- Use by import process
)type=innodb;
</source>

Example '''file for keys/indexs on llx_mytable.key.sql''':

<source lang="sql">
-- ===========================================================================
-- Copyright (C) 2013 Author <email@author.com>
--
-- This program is free software; you can redistribute it and/or modify
-- it under the terms of the GNU General Public License as published by
-- the Free Software Foundation; either version 3 of the License, or
-- (at your option) any later version.
--
-- This program is distributed in the hope that it will be useful,
-- but WITHOUT ANY WARRANTY; without even the implied warranty of
-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-- GNU General Public License for more details.
--
-- You should have received a copy of the GNU General Public License
-- along with this program. If not, see <http://www.gnu.org/licenses/>.
-- ===========================================================================

ALTER TABLE llx_matable ADD UNIQUE uk_matable_field(field_one, field_two);

ALTER TABLE llx_matable ADD CONSTRAINT fk_matable_fk_field FOREIGN KEY (fk_field) REFERENCES llx_matablepere (rowid);
</source>

== SQL Coding rules ==
* Alias usage/Fields naming
When doing select, we can use alias to simplify writing/reading of requests:
<source lang="sql">
select chp1, chpxxx2 as chp2 from table2 as t1, table2 as t2 where t1.chpx = t2.chpy
</source>
However, we must not used alias for update request as they are not compatible with Mysql 3.1.

* All SELECT * are forbidden ! Any SELECT must define complete list of fields to get. This avoid confusion. Example:
<source lang="sql">
SELECT field_a, field_b, field_c FROM table_1 WHERE field_d = '$id'
</source>

* Into SQL requests, you must quote fields except fields that contains amounts that must be stored as double or real type. Quotes on numbers may results in saving a different value. For example 412.62 in an insert will be saved with value 412.61999512 into database (due to implicit conversion string to numeric) if target field has type double(24,8). Only PHP see value 412.61999512. Other tools will see 412.62 giving sensation that there is no problem. But it's PHP that hase the good vision. There is really a wrong value into database. By removing quotes on numbers, no problem occurs.

Example:
<source lang="sql">
Good: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', 412.62)
Bad: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', '412.62')
</source>

Note, problem of float numbers is same problem on all langauges and not only when inserting data into database. It occurs also with any language when you work on "real" numbers, so numbers must be, as soon as they are affected, cleaned with function price2num with second parameter defined to :
'MU' (for unit prices), 'MT' (for total prices) or 'MS' (otherwise) depending on usage of number. (see function documentation)

* Functions NOW or SYSDATE are forbidden inside SQL requests. If you must use the current date into a field, value must come from the PHP and not from the database engine. This is to avoid a better portability of code and a correct management of TimeZone.

== Mysql specificities ==
* Tables must be declared with format InnoDB.
This format support foreign keys and their restrictions, and transactions integrity is also supported. This guarantee that Dolibarr events keep all data with correct values between tables even even transaction modify different tables.

* Dolibarr must works even if Mysql option '''strict''' is active.
To activate it (recommanded when developping on Dolibarr), add the following line into the config file of your Mysql server (my.cnf or my.ini)
<source lang="ini">
sql-mode="STRICT_ALL_TABLES,ONLY_FULL_GROUP_BY,NO_ZERO_DATE"
</source>

== PostgreSQL specificities ==
Only Mysql SQL files must be maintained.
Those files are converted "on the fly" by the database Dolibarr driver.

There is an exception
The SQL "UPDATE FROM" :
Syntax MySQL :
<source lang="sql">
UPDATE table_taget as target, table_source as source SET fieldtarget=source.fieldsource
WHERE source.rowid=target.rowid;
</source>

Syntax PgSQL:
<source lang="sql">
UPDATE table_taget as target SET fieldtarget=source.fieldsource
FROM table_source as source WHERE source.rowid=target.rowid;
</source>

There is no native SQL request "update from" in dolibarr core. But in your module you should do :
<source lang="php">
if ($this->db->type=='pgsql') {
$sql="UPDATE table_taget as target SET fieldtarget=source.fieldsource
FROM table_source as source WHERE source.rowid=target.rowid";
} else {
$sql= "UPDATE table_taget as target, table_source as source SET fieldtarget=source.fieldsource
WHERE source.rowid=target.rowid";
}
</source>

= HTML norms =
== Syntax rules ==
* HTML used must be HTML compliant and not XHTML. All attributes of HTML tags must be in lower case and quoted with ".

* Links href must be absolute and use the function dol_buildpath() to get absolute path from a relative path and img tag must be build using function img_picto().
For example:
<source lang="php">
print '<a href="'.dol_buildpath('/mydir/mypage.php').'">'.img_picto('Texte alt','namepictopng','').'</a>';
</source>

* HTML tables must have columns with no forced width, except for columns that contains data we know the length. For example, a column with a picto only can be forced to with="20px".
Otherwise, we must avoid forcing the column width. Reason is that, in most cases, the browser make a better works to define column width automatically than forced values, and it works whatever is the resolution.

* Javascript/ajax code and call to javascript files into php pages must be avoided. However, if you need to include javascript code, you must add a condition on "$conf->use_javascript_ajax"
<source lang="php">
if ($conf->use_javascript_ajax) {
... // php code generating javascript here
}
</source>

* Popups windows must not be used, except for tooltips (and must have a condition as explained before).

* External scripts must be written into Perl if they can't be written into PHP. Usage of another language is not forbidden but must be argue before onto development mailing-list.

== External templating framework ? ==
There is ton of frameworks to provide a templating language of an HTML page. The best and faster is just called "PHP", and because Dolibarr already depends on PHP, there is no need for depend on a third languages.

All templating frameworks are just preprocessor, BEFORE PHP. It can't be faster than PHP alone. When we say "speed, when using cache of templating framework, is increase", it is in fact the overtime spent by the framework that is reduced by cache, not the speed of processing PHP file. We should says "any templating framework has an overload over PHP, the cache of framework, just reduce the slowing effect of using it", but not "the speed is increased, it is always increased".

Above all, having a templating system is completely possible by doing a "'''.tpl.php'''" file that dos not contains any logic code, but only HTML and echo. We get same result (but faster and easier to develop because it does not need to do all the setXXX) before calling each template. All variables (known by code that include the template) are automaticaly known into a PHP template page. No risk to forget a set, and a lot of line of codes reduced, a lot of time saved.

Also, keeping a 100% isolation between code and HTML output is interesting in only 1 situation: When teams building design is complety different than team building logic code, AND if you build not too sophisticated pages, AND with no need of too many Ajax features (this need to know how code works).
And this situation is surely not the Dolibarr future (team will often be same, Ajax will be more and more present, event if I hope not too much, and screens are more and more dependent of dynamic or contextual events, difficult to have with a template without transforming the template into a page with high level of code).

There is a ton of other reasons to not use an external templating system and all arguments to use them are the best argument to use PHP as our templating system.

= Dolibarr norms and code skeleton =

== Skeleton code ==
To standardize the code, and to speed up the development of new components in Dolibarr, you'll find 4 skeletons fully prepared in the directory '''dev/skeletons'''.

* 1 that serves as an example of the module description: '''myModule.class.php'''
* 1 that serves as an example of code for creating a new class: '''skeleton_class.class.php'''
* 1 that serves as an example of code for creating a new page: '''skeleton_page.php'''
* 1 that serves as an example of code for creating a script for executing command lines: '''skeleton_script.php'''

Use it as an example.
Note that the skeletons are also used by the PHP code generator, which is described in the development chapter of Dolibarr modules, to speed up your development.

== Dates and Timezones ==
Dolibarr is an application that is multi-user and multi-location. It's therefore necessary to store dates in the right format. To avoid problems with conversions, the following rules should be applied:

* A date into memory must always be stored with Timestamp GMT format.
* A date stored into database, is the GMT Timestamp of date submitted into the request usng the PHP server timezone. This does not apply to date update automatically by database (fields '''tms''' into database).
For exemple le 1st january 1970, 3 hour at Paris (TZ=+1) = 2 hour at Greenwitch (TZ=0) will be stored into memory with value 7200 and will be submitted into a SQL request to database with the string '19700101030000' (PHP convert into its TZ hour and databse will unconvert it using its timezone too that is same than PHP).

All select methods should translate date fields, that are with format TZ of database ('19700101030000'), into a timestamp field by calling the method db->jdate. This is to store into memory a GTM Timestamp date. All insert methods must convert, during generation of SQL request, the memory date into the string by using db->idate (you may find examples into skeleton).

* Dates that are updated automatically (field '''tms''' into database) contains a GMT Timestamp GMT of date when change is done. The select will also use the db->jdate (that use PHP server TZ) to convert read data into a GMT Timestamp into memory. So if timezone of database differs from timezone of PHP server (one of them is not correctly set), you may experience differences between creation date and update date.

* Manipulation date with PHP must be done using the Dolibarr date functions: '''dol_now(), dol_mktime(), dol_stringtotime(), dol_getdate(), dol_time_plus_duree()'''. You may also find other functions available into file '''date.lib.php'''.

== UTF8/ISO encoding ==
Dolibarr stores data in the following way:
* In database, data is stored in UTF8 or ISO. It depends on the database's pagecode therefore these options are set at creation time. In any case, Dolibarr's database driver (in lib/database) deals with it to convert from/to UTF8 at insertion and readout.
* Memory data is stored in UTF8 (PHP object instances).
* Screen displayed web pages are UTF8 (for versions prior to 2.5.1, the deprecated $character_set parameter from conf.php file defines output format).

== Float numbers, amount and calculation ==
With PHP, like other languages (Java for exemple), non integer data (float, real, double) are not reliable for calculation.
Try to make for example
<source lang="php">
print 239.2 - 229.3 - 9.9;
</source>
You wont get zero but a very small decimal number. If you get zero her, you should be able to find other examples that don't work.
Problem of float is general, so a variable that is a result of a calculation using decimal numbers must ALWAYS be cleaned using the function '''price2num()''' with the econd parameter to: 'MU', 'MT' or 'MS' depending on need (see description of function).
<source lang="php">
print price2num(239.2 - 229.3 - 9.9, 'MT');
</source>
If data manipulated is not an amount, so using MU, MT, MS has no sense, so you must use the function '''round()'''.

== Creation of tables ==
Do not create tables, on the fly, during execution by a standard user, we mean, during current usage of software.
If you create a module that use its own table not available into default Dolibarr code, take a look at tutorial [[Module Development]] that will explain you how roviding new tables with your module to have the created during module activation and not during module usage.

== Logs ==
Add logs to your code using function
<source lang="php">
dol_syslog($yourmessage, LOG_INFO|LOG_DEBUG|LOG_WARNING|LOG_ERR);
</source>

== Working directory ==
If you need to create a working directory, into your code, refer to it with
'''DOL_DATA_ROOT.'/monmodule''''

The directory can be created into your code by the following fnction:
<source lang="php">
$mymoduledir=DOL_DATA_ROOT.'/monmodule';
dol_mkdir($mymoduledir);
</source>

If you need a directory to store temporary data, this directory must be '''DOL_DATA_ROOT.'/monmodule/temp''''

= Design patterns and Object programming =

== Creation design patterns (GoF) ==
Design patterns defined by the Gang Of Four (see wikipédia on [[wikipedia:Design pattern|Design patters]]).
No usage of such patterns is required. We found some objects next to Singletons or Factory but not completely compliant with syntax, this is to be compatible with PHP 4 that is not a pure object language.

== Structure design patterns (GoF) ==
Design patterns defined by the Gang Of Four (see wikipédia on [[wikipedia:Design pattern|Design patters]]).
No usage of such patterns is required.

== Behavior design patterns (GoF) ==
Design patterns defined by the Gang Of Four (see wikipédia on [[wikipedia:Design pattern|Design patters]]).
No usage of such patterns is required.

== Design patterns of enterprise (Martin Fowler) ==

=== Patterns of code organization ===
[[wikipedia:Martin Fowler|Martin Fowler]] has identified 3 ways to organize code:
* The '''Transaction Script''' (The source code is linear for each user action).
This is the old school used by all procedural languages.
Inconvenient: Redundancy of code. Need to know the physical model of data to develop.
* The '''Domain Model'''
This notion is available with object languages. It is business process (to identify before) that are used for objects classes.
Inconvenient: Model very complex to maintain.
* The '''Table Module'''
This is a mix between 2 previous where we have only one unique class for each table of database.

-> As shown in code skeletons (see previous chapter), Dolibarr use concept of '''Table Module'''.

=== Communication between business logic - data (ORM) ===

There is 3 way to make links:

* The '''Table And Row Data Gateway'''
This is the most simple. You have one class per table and each class is a link to the table with CRUD methods (Ceate, Read, Update, Delete). A class instance is a record a the table. The class contains only code to reach lines and fields of table.

Example: This mode is used by some ORM Frameworks, like '''iBatis''' (http://ibatis.apache.org/).

* The '''Active Record'''
Same than previous, but we are allowed to add some business functions into the class, if such functions are dedicated to the table or recordng into this table.

Example: This mode is used for Dolibarr development and most PHP softwares that includes their own framework and best practices.

* The '''Data Mapper'''
Classes represent entities of the problem and not the data. So you have to double, triple ... theese classes with Mapper classes to access the data.
More "purist" on paper (closer of business), this method also has the disadvantage of being more complex in practice.

Example: This is the choice if you use the ORM Framework '''Propel''' (http://propel.phpdb.org/trac/). We find this model on heavier applications, based on this ORM among others.

-> For Dolibarr development, it is recommended to use the connection mode '''Active Record''', which offers the advantages of a model close to the business without having the complexity, without obfuscating the technique. It is in this way that the development, understanding of code and technical maintenance and / or business seems the more productive (this is however an ongoing debate between the purists and the pragmatists, debate in which nobody can really be right, because it depends on the objectives).

Translator documentation

2014-12-17T15:14:50Z

Rdoursenaud: Added link to official transifex client documentation

<keywords content="translation, documentation, translator, localize, localization, i18n, internationalization, language" />

= [[File:Language.png]] Translate Dolibarr in another language =

Dolibarr language files are already translated in several languages.
English is by default always complete. Other languages depend on contributions. This tutorial can help you to complete a translation for a language not yet available or somehow incorrect.
Dolibarr can be translated in three different ways:

# Manually using Transifex.com (that's the official and recommended method).
# Manually editing language files
# Completely automatic: autotranslator

== Manual Translation using Transifex online service (recommended) ==

Transifex is a web application that provides an online platform for translation projects. It includes teams and discussion tools, translation memory, glossary, proofreading and a lot of other features.
It is quite easy to use and all translations can be uploaded or downloaded through the web interface or using their TX client in a terminal.
Transifex is an open source project and the "community edition" can be freely downloaded and installed, but we will use the online hosted service.

===Create transifex account and choose language===
If you want to help translating Dolibarr in your own language, please refer to http://transifex.com/projects/p/dolibarr/ and see if language is already supported. If it exists (many teams are already working for the project), you can ask to join the team and start to translate right away; if there is not a team for your language, you should request a new translation team on Transifex. It can be done directly using transifex.com interface on the website.

===Using the web interface (for translators) ===
If language is already available onto page http://transifex.com/projects/p/dolibarr/, just create an account and follow instruction of transifex web site to translate files.
Note, that this web interface must not be used to translate the following languages:
* en_US
* fr_BE, nl_BE
* es_CL, es_MX, es_HN, es_XX (where XX is not ES)
* de_AT, de_CH
(this languages are still maintained using git. en_US because it is master language, the other because they are just "delta files" of another language).

=== Using TX command line client (for Dolibarr [[:Category:Yoda]] team) ===
This describe how to use Transifex from command line. However, this is reserved to Dolibarr admin users to synchronize Transifex with Dolibarr main sources.

[http://docs.transifex.com/developer/client/ Official documentation]

====TX Client configuration====
First install TX Client.
With Debian/Ubuntu/Mint:
<source lang="bash">
apt-get install python-pip
pip install transifex-client
</source>
Then you have to initialize your TX environment. This is done by running '''tx init''' into dolibarr project root directory.
<source lang="bash">
cd git/dolibarr
tx init
</source>
Accept to overwrite config file. Keep default value for Transifex instance, then enter your Transifex login and password.

After this, a .transifexrc has been created into your HOME dir and a generic config file has been created as '''.tx/config''' in project's root.
So your directory's contents will look like that:
<code><pre>
.
|-- build
|-- build.xml
|-- ChangeLog
|-- COPYING
|-- COPYRIGHT
|-- dev
|-- doc
|-- .gitignore
|-- htdocs
|-- INSTALL
|-- pom.xml
|-- quickbuild.xml
|-- README
|-- README-FR
|-- README.md
|-- robots.txt
|-- scripts
|-- test
`-- .tx
</pre></code>

The current config file can be downloaded from https://github.com/Dolibarr/dolibarr/tree/develop/.tx , put it into .tx directory, overwriting the one created by '''tx init'''

This project configuration file is used to store the project’s details and the file-to-resource mappings.

That is a sample of what the config file contains:

<source lang="ini">
[main]
host = https://www.transifex.com
lang_map = uz: uz_UZ

[dolibarr.admin]
file_filter = htdocs/langs/<lang>/admin.lang
source_file = htdocs/langs/en_US/admin.lang
source_lang = en_US
type = MOZILLAPROPERTIES
</source>

Here is an explanation of the sections and options used in the config file:

<nowiki>[main] section</nowiki>

In this section we have project-wide options, such as the default transifex host for all projects. These can be overriden by each resource, in case it is needed.

<nowiki>[dolibarr.resource]</nowiki>

source_lang: this is the source language of the resource. 
source_file: this points to the source file directly. 
file_filter: here we hold the expression used to identify translation files under the specific project. ''not mandatory'' 
trans.<lang>: this is used for translation files that don’t follow a common naming schema and the file expression cannot be used to track them. ''not mandatory'' 
host: in case the project doesn’t use the default Transifex server as specified in the [main] section, it can override it using this option. ''not mandatory'' 

====TX Client use====
Some useful information on '''tx''' commands.

'''tx status'''

Show status of translations

'''tx push'''

Used to push changes from your computer to Transifex server 
Additional options for the tx push command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to push (defaults to all)
-r <resource> - Specify the resource for which you want to push the translations (defaults to all)
-f - Push source files without checking modification times
--skip - Don't stop on errors. Useful when pushing many files concurrently.
-s - Push the source file to the server
-t - Push the translation files to the server
--no-interactive - Don't require user input when forcing a push</pre></code>

'''tx pull'''

Used to pull changes from Transifex server to your computer 
Additional options for the tx pull command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to pull (defaults to all)
-r <resource> - Specify the resource for which you want to pull the translations (defaults to all)
-a - Fetch all translation files from server (even new ones)
-s - Force the fetching of the source file (default: False)
-f - Force download of translations files
--skip - Don't stop on errors. Useful when pushing many files concurrently.
--disable-overwrite - By default Transifex will fetch new translations files and replace existing ones. Use this flag if you want to disable this feature.
--minimum_perc=VALUE - Specify the minimum acceptable percentage of a translation in order to download it.</pre></code>

'''Examples'''

To pull translation files, you can use:

<source lang="bash">
tx -d pull -l it_IT # Get italian language only
tx -d pull -a # Get all languages
</source>

To push source files, just type:

<source lang="bash">
tx -d push -t -l it_IT [-r dolibarr.file] # To push only a specific translation file
tx -d push -s # To push source file
</source>

=== Other questions on transifex process ===
This is short questions and answer yuo may also ask about transifex translation process:

1) Is the sync on a regular time interval ?

No. It is done where there is enough translation submited. It is also done on a beta branch just before creating the final release package.

2) Are all the translations synced to git, or only the reviewed translations. Do I need to review before sync is done ?

When a Sync is done, transifex files overwrites files into git, but only if there is at least on record modified for the file.
You don't have to make review before sync is done. Making review is above all to know which lines were manually reviewed and wich one were intially translated using a robot.

3) In which Dolibarr releases will translations be available ? Are transifex translations also synced to maintenance releases ?

Sync is always done on develop and/or beta.
So transifex changes appear in all version whose branch is created after the transifex change (a sync is always done before creating a new branch). Once a branch is created, then new changes into transifex will be available only for next branch. Reason of this is that transifex is not able to manage branch/versions (not yet).

== Manual Translation (not recommended) ==

To translate Dolibarr into another language, go to the langs directory and create a folder/directory named with the code language to translate (follow the existing format, for example en_US, en_GB, es_ES, de_DE, etc...). Then copy the files from an existing language directory (for example en_US/main.lang, en_GB/bills.lang), into the new language directory that you have just created.

These files have the format of key/value pairs in each line like the followings:

<source lang="ini">
Code1 = translate phrase 1
Code2 = translate phrase 2
...
Coden = translate phrase n
</source>

Translate the phrases (the value portion of the key/value pairs) on right side of the "=" as seen above, the code (the key portion) on left side of "=" should remain unchanged. It is possible to translate the files one by one, without bringing them all at once. If a file has not been translated into the new language, Dolibarr uses English.

To have a localised (translated) string into the PHP code, all you have to do is load the language file and use the method to get the translated value, like this:

<source lang="php">
$langs->load("myfile"); // or use $langs->load("myfile@mymodule") if myfile.lang is inside directory htdocs/mymodule/langs/xx_XX

print $langs->trans("CodeX")
</source>

An entry type;

<source lang="ini">
CodeX = phrase X
</source>

must be present or added to the myfile.lang file.

== Automatic Translation with autotranslator.php tool ==

* Translator OS: All
* Tool: '''autotranslator.php''' provided with Dolibarr in directory '''dev/translation'''.
This method is recommended when starting translation for a language not already initialized. If there is already a translation available but you need to add missing key or correct errors, try to use method using Transifex (see later).

To make or update all files of a language code, just run the script:
<source lang="bash">
php autotranslator.php lang_code_source lang_code_target GOOGLEAPIKEY
</source>
For example :
<source lang="bash">
php autotranslator.php en_US pt_PT GOOGLEAPIKEY
</source>
to translate into Portuguese (pt_PT) using English (en_US) files.

All non existing files will be created, all existing files will be updated.
The tool use [http://translate.google.com Google translation] service to find the translation value of a string, so a working Internet connection is required from station running the script. Also a GOOGLEAPIKEY is required and Google charges a fee for using this service (20 euros / 1 000 000 of translated chars).
Your PHP must also have permissions to write into '''htdocs/langs''' directory and must have curl functions available.

= [[File:Language.png]] Distribute or include your translation into core source =

== Into official Dolibarr sources ==
The best thing once translation is complete, is to include it in the official version of Dolibarr.

If you have completed the translation of already existing and incomplete lang files or if you have created lang files for a new language, you can:

* If the translation was done by using the Transifex system for languages other than en_US, en_GB, es_ES and ca_ES (see above), no further action is needed. Your translation will be integrated ont the next occurance of our regular synchronization with the official Git sources (at least once a month).
* If the translation was made on files directly (that should be the case for en_US, en_GB, es_ES and ca_ES languages), it is possible to integrate using the GIT system. To do this, create an account on {{TemplateUrlSCM}}, fork the project, edit the relevant files and send a Pull Request.

'' Note:'' The reference language is always complete:
* English (Lang directory lang/en_US)

All other language files are likely to be incomplete.

== As an extension ==
When you create a new language, if it is not already integrated into Dolibarr, it can still be broadcast to all other users. You can make a distribution package using the '''build/makepack-dolibarrlang.pl''' script or making a zip archive manually and posting it on dolistore.com or sending it to the developers' mailing list '''dolibarr-dev''' ({{TemplateURLMLDev}}).

New language files are immediately available in an installation as soon as the archive is unzipped in the correct directory.

= [[File:Language.png]] Translate documentation on wiki =
The wiki is written in 3 languages: English, French and Spanish.
If you want to enhance documentation on one of these languages, all you have to do is to create an account on this wiki.
Then, you can edit existing pages to correct a bad translation or translate pages waiting for translation [[:Category:Page_waiting_for_translation]].

Translator documentation

2014-12-17T15:10:07Z

Rdoursenaud: Added language map to Transifex configuration

<keywords content="translation, documentation, translator, localize, localization, i18n, internationalization, language" />

= [[File:Language.png]] Translate Dolibarr in another language =

Dolibarr language files are already translated in several languages.
English is by default always complete. Other languages depend on contributions. This tutorial can help you to complete a translation for a language not yet available or somehow incorrect.
Dolibarr can be translated in three different ways:

# Manually using Transifex.com (that's the official and recommended method).
# Manually editing language files
# Completely automatic: autotranslator

== Manual Translation using Transifex online service (recommended) ==

Transifex is a web application that provides an online platform for translation projects. It includes teams and discussion tools, translation memory, glossary, proofreading and a lot of other features.
It is quite easy to use and all translations can be uploaded or downloaded through the web interface or using their TX client in a terminal.
Transifex is an open source project and the "community edition" can be freely downloaded and installed, but we will use the online hosted service.

===Create transifex account and choose language===
If you want to help translating Dolibarr in your own language, please refer to http://transifex.com/projects/p/dolibarr/ and see if language is already supported. If it exists (many teams are already working for the project), you can ask to join the team and start to translate right away; if there is not a team for your language, you should request a new translation team on Transifex. It can be done directly using transifex.com interface on the website.

===Using the web interface (for translators) ===
If language is already available onto page http://transifex.com/projects/p/dolibarr/, just create an account and follow instruction of transifex web site to translate files.
Note, that this web interface must not be used to translate the following languages:
* en_US
* fr_BE, nl_BE
* es_CL, es_MX, es_HN, es_XX (where XX is not ES)
* de_AT, de_CH
(this languages are still maintained using git. en_US because it is master language, the other because they are just "delta files" of another language).

=== Using TX command line client (for Dolibarr [[:Category:Yoda]] team) ===
This describe how to use Transifex from command line. However, this is reserved to Dolibarr admin users to synchronize Transifex with Dolibarr main sources.

====TX Client configuration====
First install TX Client.
With Debian/Ubuntu/Mint:
<source lang="bash">
apt-get install python-pip
pip install transifex-client
</source>
Then you have to initialize your TX environment. This is done by running '''tx init''' into dolibarr project root directory.
<source lang="bash">
cd git/dolibarr
tx init
</source>
Accept to overwrite config file. Keep default value for Transifex instance, then enter your Transifex login and password.

After this, a .transifexrc has been created into your HOME dir and a generic config file has been created as '''.tx/config''' in project's root.
So your directory's contents will look like that:
<code><pre>
.
|-- build
|-- build.xml
|-- ChangeLog
|-- COPYING
|-- COPYRIGHT
|-- dev
|-- doc
|-- .gitignore
|-- htdocs
|-- INSTALL
|-- pom.xml
|-- quickbuild.xml
|-- README
|-- README-FR
|-- README.md
|-- robots.txt
|-- scripts
|-- test
`-- .tx
</pre></code>

The current config file can be downloaded from https://github.com/Dolibarr/dolibarr/tree/develop/.tx , put it into .tx directory, overwriting the one created by '''tx init'''

This project configuration file is used to store the project’s details and the file-to-resource mappings.

That is a sample of what the config file contains:

<source lang="ini">
[main]
host = https://www.transifex.com
lang_map = uz: uz_UZ

[dolibarr.admin]
file_filter = htdocs/langs/<lang>/admin.lang
source_file = htdocs/langs/en_US/admin.lang
source_lang = en_US
type = MOZILLAPROPERTIES
</source>

Here is an explanation of the sections and options used in the config file:

<nowiki>[main] section</nowiki>

In this section we have project-wide options, such as the default transifex host for all projects. These can be overriden by each resource, in case it is needed.

<nowiki>[dolibarr.resource]</nowiki>

source_lang: this is the source language of the resource. 
source_file: this points to the source file directly. 
file_filter: here we hold the expression used to identify translation files under the specific project. ''not mandatory'' 
trans.<lang>: this is used for translation files that don’t follow a common naming schema and the file expression cannot be used to track them. ''not mandatory'' 
host: in case the project doesn’t use the default Transifex server as specified in the [main] section, it can override it using this option. ''not mandatory'' 

====TX Client use====
Some useful information on '''tx''' commands.

'''tx status'''

Show status of translations

'''tx push'''

Used to push changes from your computer to Transifex server 
Additional options for the tx push command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to push (defaults to all)
-r <resource> - Specify the resource for which you want to push the translations (defaults to all)
-f - Push source files without checking modification times
--skip - Don't stop on errors. Useful when pushing many files concurrently.
-s - Push the source file to the server
-t - Push the translation files to the server
--no-interactive - Don't require user input when forcing a push</pre></code>

'''tx pull'''

Used to pull changes from Transifex server to your computer 
Additional options for the tx pull command are:
<code><pre>
-h - Shows the help screen for the command
-l <lang> - Specify which translations you want to pull (defaults to all)
-r <resource> - Specify the resource for which you want to pull the translations (defaults to all)
-a - Fetch all translation files from server (even new ones)
-s - Force the fetching of the source file (default: False)
-f - Force download of translations files
--skip - Don't stop on errors. Useful when pushing many files concurrently.
--disable-overwrite - By default Transifex will fetch new translations files and replace existing ones. Use this flag if you want to disable this feature.
--minimum_perc=VALUE - Specify the minimum acceptable percentage of a translation in order to download it.</pre></code>

'''Examples'''

To pull translation files, you can use:

<source lang="bash">
tx -d pull -l it_IT # Get italian language only
tx -d pull -a # Get all languages
</source>

To push source files, just type:

<source lang="bash">
tx -d push -t -l it_IT [-r dolibarr.file] # To push only a specific translation file
tx -d push -s # To push source file
</source>

=== Other questions on transifex process ===
This is short questions and answer yuo may also ask about transifex translation process:

1) Is the sync on a regular time interval ?

No. It is done where there is enough translation submited. It is also done on a beta branch just before creating the final release package.

2) Are all the translations synced to git, or only the reviewed translations. Do I need to review before sync is done ?

When a Sync is done, transifex files overwrites files into git, but only if there is at least on record modified for the file.
You don't have to make review before sync is done. Making review is above all to know which lines were manually reviewed and wich one were intially translated using a robot.

3) In which Dolibarr releases will translations be available ? Are transifex translations also synced to maintenance releases ?

Sync is always done on develop and/or beta.
So transifex changes appear in all version whose branch is created after the transifex change (a sync is always done before creating a new branch). Once a branch is created, then new changes into transifex will be available only for next branch. Reason of this is that transifex is not able to manage branch/versions (not yet).

== Manual Translation (not recommended) ==

To translate Dolibarr into another language, go to the langs directory and create a folder/directory named with the code language to translate (follow the existing format, for example en_US, en_GB, es_ES, de_DE, etc...). Then copy the files from an existing language directory (for example en_US/main.lang, en_GB/bills.lang), into the new language directory that you have just created.

These files have the format of key/value pairs in each line like the followings:

<source lang="ini">
Code1 = translate phrase 1
Code2 = translate phrase 2
...
Coden = translate phrase n
</source>

Translate the phrases (the value portion of the key/value pairs) on right side of the "=" as seen above, the code (the key portion) on left side of "=" should remain unchanged. It is possible to translate the files one by one, without bringing them all at once. If a file has not been translated into the new language, Dolibarr uses English.

To have a localised (translated) string into the PHP code, all you have to do is load the language file and use the method to get the translated value, like this:

<source lang="php">
$langs->load("myfile"); // or use $langs->load("myfile@mymodule") if myfile.lang is inside directory htdocs/mymodule/langs/xx_XX

print $langs->trans("CodeX")
</source>

An entry type;

<source lang="ini">
CodeX = phrase X
</source>

must be present or added to the myfile.lang file.

== Automatic Translation with autotranslator.php tool ==

* Translator OS: All
* Tool: '''autotranslator.php''' provided with Dolibarr in directory '''dev/translation'''.
This method is recommended when starting translation for a language not already initialized. If there is already a translation available but you need to add missing key or correct errors, try to use method using Transifex (see later).

To make or update all files of a language code, just run the script:
<source lang="bash">
php autotranslator.php lang_code_source lang_code_target GOOGLEAPIKEY
</source>
For example :
<source lang="bash">
php autotranslator.php en_US pt_PT GOOGLEAPIKEY
</source>
to translate into Portuguese (pt_PT) using English (en_US) files.

All non existing files will be created, all existing files will be updated.
The tool use [http://translate.google.com Google translation] service to find the translation value of a string, so a working Internet connection is required from station running the script. Also a GOOGLEAPIKEY is required and Google charges a fee for using this service (20 euros / 1 000 000 of translated chars).
Your PHP must also have permissions to write into '''htdocs/langs''' directory and must have curl functions available.

= [[File:Language.png]] Distribute or include your translation into core source =

== Into official Dolibarr sources ==
The best thing once translation is complete, is to include it in the official version of Dolibarr.

If you have completed the translation of already existing and incomplete lang files or if you have created lang files for a new language, you can:

* If the translation was done by using the Transifex system for languages other than en_US, en_GB, es_ES and ca_ES (see above), no further action is needed. Your translation will be integrated ont the next occurance of our regular synchronization with the official Git sources (at least once a month).
* If the translation was made on files directly (that should be the case for en_US, en_GB, es_ES and ca_ES languages), it is possible to integrate using the GIT system. To do this, create an account on {{TemplateUrlSCM}}, fork the project, edit the relevant files and send a Pull Request.

'' Note:'' The reference language is always complete:
* English (Lang directory lang/en_US)

All other language files are likely to be incomplete.

== As an extension ==
When you create a new language, if it is not already integrated into Dolibarr, it can still be broadcast to all other users. You can make a distribution package using the '''build/makepack-dolibarrlang.pl''' script or making a zip archive manually and posting it on dolistore.com or sending it to the developers' mailing list '''dolibarr-dev''' ({{TemplateURLMLDev}}).

New language files are immediately available in an installation as soon as the archive is unzipped in the correct directory.

= [[File:Language.png]] Translate documentation on wiki =
The wiki is written in 3 languages: English, French and Spanish.
If you want to enhance documentation on one of these languages, all you have to do is to create an account on this wiki.
Then, you can edit existing pages to correct a bad translation or translate pages waiting for translation [[:Category:Page_waiting_for_translation]].

Dependencies and external libraries

2014-10-01T12:39:16Z

Rdoursenaud: Adding extensions for libraries used by Dolibarr

{{TemplateDocDevEn}}

= Libraries embedded inside source code =

All libraries embedded into Dolibarr distribution are located inside directory '''htdocs/includes''':

{{TemplateListOfLibraries}}

All those external embedded libraries must respect the following rules:
* They must be compatible with Dolibarr license. The file '''COPYRIGHT''' inside Dolibarr root directory list all embedded libraries and their license.
* If a change is made inside original external library code, this change must be notified inside file '''devs/dolibarr_changes.txt'''. In most cases, you should not have to edit external libraries and should use them as they are provided. This is to make upgrade of libraries possible with no need to report code changes after an upgrade.

= Apache Modules =
mod_php

= PHP Extensions =
Database drivers:
{{ListOfPHPDatabaseExtensions}}

Image manipulation:
{{ListOfPHPImageExtensions}}

Encoding/Encryption:
{{ListOfPHPEncryptionExtensions}}

Webservices:
{{ListOfPHPWSExtensions}}

Other:
{{ListOfOtherPHPExtensions}}

Template:ListOfOtherPHPExtensions

2014-10-01T12:38:58Z

Rdoursenaud: Added PHPExcel deps

* for PHPExcel
** zip (handling of .xlsx, .ods and .gnumeric files)
** xml
** gd2 (optional, but required for exact column width autocalculation)