Dolibarr ERP CRM Wiki - User contributions [en]

DevCamp Angoulême novembre 2025

2025-10-02T13:27:41Z

O.tourvieille: /* Organization draft */

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

This page lists typical actions needed to organize 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

==Title==

*Event Name of: DevCamp winter 2025
*Main language used : French

==Organizers==
Define name of organizers and managers (may be the same guys):

*Location manager: Progiseize (Olivier)
*Communication manager: _____________
*Sponsor manager (not mandatory): _____________

==Dates==
Event dates and duration : 27/11/25 till 30/11/25

Limit date for registration: _________

==Location==

**Location for food: 1 Bd Berthelot, 16006 Angoulême
**Location for bedrooms : Hôtel Européen 1 Pl. Gérard Pérot, 16000 Angoulême ; Hôtel du Palais 4 Pl. Francis Louvel, 16000 Angoulême
**chairs: 60
**tables: 40
**video projector: 1

==Planning suggestion==

*Define a suggestion of Planning

=Organization live=
Once your draft page with all information you know are filled, you can submit it to the Dolibarr foundation: contact@dolibarr.org.
You can send also the quotes your received from hotels, for rooms and foods.

The foundation will exhange with you on the basis of this informations.

The Dolibarr foundation will:

*pay the credit note for booking hotel or restaurant
*make the communication to ask registration
*manage and receive the registration to the events
*give you the final list of names of participant

==Sponsoring==
Some sponsors can contribute to sponsor/fund the event if you find some.

==Example of past and next DevCamps==
See page [[:Category:DevCamps]]
[[Category:Development]]
[[Category:Foundation]]

DevCamp Angoulême novembre 2025

2025-10-02T13:25:53Z

O.tourvieille: Lieux (hôtels et salle)

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

This page lists typical actions needed to organize 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 draft=
To start a devcamp organization, first thing to do is to create a wiki page with answers to several questions. The name of this wiki page must start with "Draft:Name_Of_Event".
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==

*Event Name of: DevCamp winter 2025
*Main language used : French

==Organizers==
Define name of organizers and managers (may be the same guys):

*Location manager: Progiseize (Olivier)
*Communication manager: _____________
*Sponsor manager (not mandatory): _____________

==Dates==
Event dates and duration : 27/11/25 till 30/11/25

Limit date for registration: _________

==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: 1 Bd Berthelot, 16006 Angoulême
**Location for bedrooms : Hôtel Européen 1 Pl. Gérard Pérot, 16000 Angoulême ; Hôtel du Palais 4 Pl. Francis Louvel, 16000 Angoulême
**chairs: 60
**tables: 40
**video projector: 1

==Planning suggestion==

*Define a suggestion of Planning

=Organization live=
Once your draft page with all information you know are filled, you can submit it to the Dolibarr foundation: contact@dolibarr.org.
You can send also the quotes your received from hotels, for rooms and foods.

The foundation will exhange with you on the basis of this informations.

The Dolibarr foundation will:

*pay the credit note for booking hotel or restaurant
*make the communication to ask registration
*manage and receive the registration to the events
*give you the final list of names of participant

==Sponsoring==
Some sponsors can contribute to sponsor/fund the event if you find some.

==Example of past and next DevCamps==
See page [[:Category:DevCamps]]
[[Category:Development]]
[[Category:Foundation]]

DevCamp Angoulême novembre 2025

2025-04-02T19:34:25Z

O.tourvieille: /* Organization draft */

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

This page lists typical actions needed to organize 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 draft=
To start a devcamp organization, first thing to do is to create a wiki page with answers to several questions. The name of this wiki page must start with "Draft:Name_Of_Event".
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==

*Event Name of: DevCamp winter 2025
*Main language used : French

==Organizers==
Define name of organizers and managers (may be the same guys):

*Location manager: Progiseize (Olivier)
*Communication manager: _____________
*Sponsor manager (not mandatory): _____________

==Dates==
Event dates and duration : 27/11/25 till 30/11/25
Limit date for registration: _________

==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

=Organization live=
Once your draft page with all information you know are filled, you can submit it to the Dolibarr foundation: contact@dolibarr.org.
You can send also the quotes your received from hotels, for rooms and foods.

The foundation will exhange with you on the basis of this informations.

The Dolibarr foundation will:

*pay the credit note for booking hotel or restaurant
*make the communication to ask registration
*manage and receive the registration to the events
*give you the final list of names of participant

==Sponsoring==
Some sponsors can contribute to sponsor/fund the event if you find some.

==Example of past and next DevCamps==
See page [[:Category:DevCamps]]
[[Category:Development]]
[[Category:Foundation]]

DevCamps Angouleme 2025

2025-04-01T12:59:45Z

O.tourvieille: O.tourvieille moved page DevCamps Angouleme 2025 to DevCamp Angoulême novembre 2025

#REDIRECT [[DevCamp Angoulême novembre 2025]]

DevCamp Angoulême novembre 2025

2025-04-01T12:59:45Z

O.tourvieille: O.tourvieille moved page DevCamps Angouleme 2025 to DevCamp Angoulême novembre 2025

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

This page lists typical actions needed to organize 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 draft=
To start a devcamp organization, first thing to do is to create a wiki page with answers to several questions. The name of this wiki page must start with "Draft:Name_Of_Event".
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: DevCamp winter 2025
*Main language used: French (french, english ?)

==Organizers==
Define name of organizers and managers (may be the same guys):

*Location manager: Progiseize (Olivier)
*Food manager: ____________
*Communication manager: _____________
*Sponsor manager (not mandatory): _____________

==Dates==
Event dates and duration must be defined (one day, two days, three…): 27/11/25 till 30/11/25
Limit date for registration: _________

==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

=Organization live=
Once your draft page with all information you know are filled, you can submit it to the Dolibarr foundation: contact@dolibarr.org.
You can send also the quotes your received from hotels, for rooms and foods.

The foundation will exhange with you on the basis of this informations.

The Dolibarr foundation will:

*pay the credit note for booking hotel or restaurant
*make the communication to ask registration
*manage and receive the registration to the events
*give you the final list of names of participant

==Sponsoring==
Some sponsors can contribute to sponsor/fund the event if you find some.

==Example of past and next DevCamps==
See page [[:Category:DevCamps]]
[[Category:Development]]
[[Category:Foundation]]

DevCamp Angoulême novembre 2025

2025-04-01T12:54:19Z

O.tourvieille: Dates et début d'orga

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

This page lists typical actions needed to organize 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 draft=
To start a devcamp organization, first thing to do is to create a wiki page with answers to several questions. The name of this wiki page must start with "Draft:Name_Of_Event".
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: DevCamp winter 2025
*Main language used: French (french, english ?)

==Organizers==
Define name of organizers and managers (may be the same guys):

*Location manager: Progiseize (Olivier)
*Food manager: ____________
*Communication manager: _____________
*Sponsor manager (not mandatory): _____________

==Dates==
Event dates and duration must be defined (one day, two days, three…): 27/11/25 till 30/11/25
Limit date for registration: _________

==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

=Organization live=
Once your draft page with all information you know are filled, you can submit it to the Dolibarr foundation: contact@dolibarr.org.
You can send also the quotes your received from hotels, for rooms and foods.

The foundation will exhange with you on the basis of this informations.

The Dolibarr foundation will:

*pay the credit note for booking hotel or restaurant
*make the communication to ask registration
*manage and receive the registration to the events
*give you the final list of names of participant

==Sponsoring==
Some sponsors can contribute to sponsor/fund the event if you find some.

==Example of past and next DevCamps==
See page [[:Category:DevCamps]]
[[Category:Development]]
[[Category:Foundation]]

DevCamp Angoulême novembre 2025

2025-01-23T12:58:04Z

O.tourvieille: Création de la page

This page lists typical actions needed to organize a DevCamp. You can also use it as a template to start organization of a particular devcamp.

 

==Sommaire==

*[[DevCamps Organization#Why|1Why]]
**[[DevCamps Organization#What%20is%20a%20DevCamp|1.1What is a DevCamp]]
**[[DevCamps Organization#Who%20can%20come%20to%20a%20DevCamp|1.2Who can come to a DevCamp]]
**[[DevCamps Organization#What%20kind%20topic%20at%20DevCamp|1.3What kind topic at DevCamp]]
*[[DevCamps Organization#Organization%20draft|2Organization draft]]
**[[DevCamps Organization#Title|2.1Title]]
**[[DevCamps Organization#Organizers|2.2Organizers]]
**[[DevCamps Organization#Dates|2.3Dates]]
**[[DevCamps Organization#Location|2.4Location]]
**[[DevCamps Organization#Planning%20suggestion|2.5Planning suggestion]]
*[[DevCamps Organization#Organization%20live|3Organization live]]
**[[DevCamps Organization#Sponsoring|3.1Sponsoring]]
**[[DevCamps Organization#Example%20of%20past%20and%20next%20DevCamps|3.2Example of past and next DevCamps]]

==Why[<nowiki/>[[DevCamps Organization&veaction=edit&section=1|modifier]] | [[DevCamps Organization&section=1&veaction=editsource|modifier le wikicode]]]==

===What is a DevCamp[<nowiki/>[[DevCamps Organization&veaction=edit&section=2|modifier]] | [[DevCamps Organization&section=2&veaction=editsource|modifier le wikicode]]]===
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[<nowiki/>[[DevCamps Organization&veaction=edit&section=3|modifier]] | [[DevCamps Organization&section=3&veaction=editsource|modifier le wikicode]]]===
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[<nowiki/>[[DevCamps Organization&veaction=edit&section=4|modifier]] | [[DevCamps Organization&section=4&veaction=editsource|modifier le wikicode]]]===

*Training
*Special feature to build (may be the goal of a DevCamp)
*Update project documentation

==Organization draft[<nowiki/>[[DevCamps Organization&veaction=edit&section=5|modifier]] | [[DevCamps Organization&section=5&veaction=editsource|modifier le wikicode]]]==
To start a devcamp organization, first thing to do is to create a wiki page with answers to several questions. The name of this wiki page must start with "Draft:Name_Of_Event". 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[<nowiki/>[[DevCamps Organization&veaction=edit&section=6|modifier]] | [[DevCamps Organization&section=6&veaction=editsource|modifier le wikicode]]]===
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[<nowiki/>[[DevCamps Organization&veaction=edit&section=7|modifier]] | [[DevCamps Organization&section=7&veaction=editsource|modifier le wikicode]]]===
Define name of organizers and managers (may be the same guys):

*Location manager: _____________
*Food manager: ____________
*Communication manager: _____________
*Sponsor manager (not mandatory): _____________

===Dates[<nowiki/>[[DevCamps Organization&veaction=edit&section=8|modifier]] | [[DevCamps Organization&section=8&veaction=editsource|modifier le wikicode]]]===
Event dates and duration must be defined (one day, two days, three…): _________ Limit date for registration: _________

===Location[<nowiki/>[[DevCamps Organization&veaction=edit&section=9|modifier]] | [[DevCamps Organization&section=9&veaction=editsource|modifier le wikicode]]]===

*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[<nowiki/>[[DevCamps Organization&veaction=edit&section=10|modifier]] | [[DevCamps Organization&section=10&veaction=editsource|modifier le wikicode]]]===

*Define a suggestion of Planning

==Organization live[<nowiki/>[[DevCamps Organization&veaction=edit&section=11|modifier]] | [[DevCamps Organization&section=11&veaction=editsource|modifier le wikicode]]]==
Once your draft page with all information you know are filled, you can submit it to the Dolibarr foundation: contact@dolibarr.org. You can send also the quotes your received from hotels, for rooms and foods.

The foundation will exhange with you on the basis of this informations.

The Dolibarr foundation will:

*pay the credit note for booking hotel or restaurant
*make the communication to ask registration
*manage and receive the registration to the events
*give you the final list of names of participant

===Sponsoring[<nowiki/>[[DevCamps Organization&veaction=edit&section=12|modifier]] | [[DevCamps Organization&section=12&veaction=editsource|modifier le wikicode]]]===
Some sponsors can contribute to sponsor/fund the event if you find some.

===Example of past and next DevCamps[<nowiki/>[[DevCamps Organization&veaction=edit&section=13|modifier]] | [[DevCamps Organization&section=13&veaction=editsource|modifier le wikicode]]]===
See page [[:Category:DevCamps|Category:DevCamps]]

GIFF - Facture de situation 2022

2023-01-06T13:45:16Z

O.tourvieille: /* Outils de travail : */

===Présentation du sujet pour ce GIF :===
Amélioration des factures de situation

Détail du problème actuel des factures de situations. Exemple d'une prestation de service proposée (devis) à 2500€ HT. Cette prestation sera faite en 3 fois, chaque étape donne lieux à une facture de situation notées S1, S2 et S3.

*S1 : 25% réalisé, facture de 625€ HT, TVA collectée 125€
*S2 : progression totale de 50%, donc facture de 625€ HT, TVA collectée 125€
*S3 : progression totale de 100%, donc facture de 1250€ HT, TVA collectée 250€
*Total de la TVA collectée = 500€

L'implémentation actuelle (version dolibarr 16.0.3) se présente comme ceci:

*Affichage OK dans le détail des factures (voir capture "Situation S3")
*Affichage OK sur les listes des factures et affichage des totaux corrects
*Mais erreur lors du calcul de la TVA (voir les 2 captures suivantes) : Total TVA collectée : 875€

<gallery widths="240" heights="240">
File:Facture de situation - S3 - Liste des situations.png|Situation S3 : Affiche correctement l'historique des factures et les montants respectifs.
File:Situation - Erreur de calcul de TVA.png|Le calcul de la TVA ne marche plus avec les factures de situations
File:Détail du calcul de TVA erroné.png|Détail du calcul de TVA erroné
</gallery>

===Outils de travail :===

*Forum : https://www.dolibarr.fr/forum/t/gif-facture-de-situation/41868
*Wiki : à remplir
*Plateforme de financement : à remplir
*Intervenants et rôles : à remplir
*Choix du porteur de projet pour les outils : [https://github.com/users/progiseize/projects/1 Projet Github]
*Channel sur Discord : à remplir

===Etapes prévues pour ce POC===

====Etape 0 - Définition du modèle de données====
-Ajout des données dans la table de lignes

====Etape 1 - Fonction migration des données dans le nouveau modèle de données====
-Migration des données

-Génération du pdf sur la base des nouvelles données

 

===Consignes===
Le nouveau code devra être conditionné par getDolGlobalInt('INVOICE_USE_SITUATION') == 2 (on conserve la valeur 1 utilisé pour l'ancien mode de fonctionnement).
 
[[Category:Groupement d'Intérêt Fonctionnel]]

DevCamp Nantes 2022

2022-11-27T00:13:02Z

O.tourvieille: /* Compte rendu : GIF - Groupement d'Intérêt Fonctionnel */

==Compte rendu : GIF - Groupement d'Intérêt Fonctionnel==
Les personnes présentes : Eoxia, Evarisk, InfraS, Cap-Rel, Inovea, Pragma-tech,Code42, Progiseize...

Le principe serait de permettre à différents intervenants de se regrouper autour d'un axe de développement fonctionnel. Les étapes pourraient être :

*Etape 1 : Choix du module et définition des fonctions attendues
*Etape 2 : Création du projet sur le [https://github.com/orgs/Dolibarr/projects Github de l'association]
*Etape 3 : Montant de la participation minimum au projet par personne/organisation et rôles (financeur ou intervenant)
*Etape 4 : Définition du Partenaire qui porte le projet
**Définition du rythme de travail
**Définition des réunions de validation
**Définition des paiements
*Etape 5 : Définition des besoins d'experts externe
*Etape 6 : Définition du ROI attendu basé sur les ventes en ligne sur le Dolistore
*Etape 7 : Définition des étapes d'intégration dans le cœur de Dolibarr

Les risques identifiés

*Abandon du projet par le Preferred Partner
*Dépassement du temps prévu sur le projet
*Manque d'interlocuteur fonctionnel
*Points bloquants dans le core de Dolibarr pour la réalisation du module

 
==Compte rendu : Dolistore==
Les personnes présentes : NS Info, Inovea Conseil, AB1 Consulting, Atoo-net, Takepos, ...

Ce groupe avait pour but d'échanger sur les attentes et problématiques concernant le Dolistore et ses usages.

 

*Pour les acheteurs
**La recherche est trop fastidieuse pour trouver un module acheter précédemment. Un va-et-vient intempestif entre la liste des commandes et les produits la composant qui se trouve en bas du listing.

 

*Pour les éditeurs
**Lors de la distribution gratuite de module, celui-ci est directement téléchargeable sans authentification. Ce système natif de Prestashop ne permet pas à l'éditeur de suivre la popularité de son module.
**Afin de faciliter la gestion de son espace revendeur, une API d'échange serait appréciée pour traiter les commandes recues, gérer la mise à jour des zip de module et de la fiche module.
**La gestion des remboursements est parfois trop rapide envers le client qui ne permet pas à l'éditeur d'assurer sa procédure de SAV, des dérives d'usage pourrait être exploitées.
**Paypal se positionne en juge pour décider unilatéralement de rembourser l'acheteur: une recherche sur le comportement de Paypal concernant les produits dématérialisés.
**La constatation de plus en plus importante, de modules qui n'apportent pas de nouvelle fonctionnalité par rapport à d'autre module existant et pourrait entraver les conditions d'usage de la plate-forme.

DevCamp Nancy 2018 Organization

2018-01-19T15:28:18Z

O.tourvieille: /* Validate registration */

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

= Event =
'''Dolibarr Spring DevCamp 2018'''

First Dolibarr Devcamp in Nancy is planned.

The DevCamp is a meeting where developers meets each other to speak (and develop a little bit) about Dolibarr ERP CRM. We are speaking about What's new, best practice. Participating to the devcamp means you are and want to be evolved in Dolibarr project and knows the Dolibarr developers rules. It also means you are ready to speak during 2 days and 2 dates (see planning) with a dozen of other geeks. Talks done by project leader will be published on social networks.
This year, to avoid people subscribing and not coming, we are requesting to pay a 50 euros subscription. Number of places is limited to 20.

We hope to publish the main talks on social network like periscope or facebook live or youtube (to be defined)

== Dates ==
March 2018, 9-10-11

== Location ==
[HOTEL MERCURE NANCY CENTRE GARE],11 Rue Raymond Poincare
54000 NANCY - FRANCE
GPS :N 48° 41' 26.20'' E 6° 10' 28.51''

== How to come ==

* TrainStation : Nancy Centre - the hotel is 100m from the train station - Opposite the train station, Place Thiers exit
Shuttle to Lorraine TGV train station and Metz Nancy Airport nearby.
* Car: From Paris or Strasbourg: take the A4 motorways - From Brussels, Luxembourg and Dijon: take the A31 motorway. Head toward "centre ville" and then "gare SNCF"

== Main languages ==
* French / English

== Organizers ==
* Main: INOVEA CONSEIL (info@inovea-conseil.com) - TIARIS (jean.heimburger@tiaris.info)
* Hosting: INOVEA CONSEIL (info@inovea-conseil.com)
* Lodging and Catering: INOVEA CONSEIL (info@inovea-conseil.com)

== Lodging and catering ==
Meals and bedrooms will be provided during the devcamp by the Mercure hotel.

== Food ==
We will have a cocktail on Friday evening before dinner to welcome you in Nancy!

= Planning =

== Day 1 (Friday) ==
* 14:00 - Welcome - Presentation - Networking
* 18:00 - Presentation Dolibarr 7
* 20:00 - Dinner
* 21:00 - Bug tracking and closing issues

== Day 2 (Saturday) ==
* 8:00 - 12:00 - Bug tracking and closing issues
* 12:00 - Lunch
* 14:00 - 16:00 : Community tools presentation
* 17:00 : Dolibarr Foundation assembly
* 20:00 - Dinner
* Night : Dolibarr Hacking

== Day 3 (Sunday) ==
* 8:00 - 12:00 - Bug tracking and closing issues

= Topics and issues to work on =
''Open for suggestions and volunteers''
* Bugfix contest
* Tools for foundation
* Roadmap ?

= Attendees registration =
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 or ask organisators '''.

* Lastname Firstname: CASTELLANO Claude
* Age:
* Coming from (town, country): Le Vigan (gard)
* Arrival date and hour: vendredi matin
* Departure date and hour: dimanche soir ou lundi matin
* Transportation (Train/Bus/Car/Plane): non décidé
* Food (Special diet, allergies, vegetarian, none…):
* Accommodation (Common booked hotel/self…): Mercure ou self, suivant le cas. Quelle est la date limite de réservation des chambres d'hotel?
* Book hotel for me (yes/no):à préciser ultérieurement
* Contact email:claude@cigaleaventure.com

= Validate registration =

'''To validate your registration, you must make a bank transfer of 50 € per person'''

Banque: CAISSE D'EPARGNE
Code banque: 14505
Code guichet: 00001
Numéro de compte: 08000207968
Clé: 70

Domiciliation: Agence Olivet
107, rue Jules-Marie Simon
45160 OLIVET
FRANCE
Nom du propriétaire du compte: Association Dolibarr
Code IBAN: FR76 1450 5000 0108 0002 0796 870
Code BIC/SWIFT: CEPAFRPP450

------------------------------------------

[[File:Nicolas_Zabouri.png‎|40px]]
* Lastname Firstname: [[Inovea Conseil | Nicolas ZABOURI]]
* Age: 35
* Coming from (town, country): Essegney (88), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 14:00
* Transportation (Train/Bus/Car/Plane): Car
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Mercure
* Book hotel for me (yes/no): yes
* Contact email: info@inovea-conseil.com

[[File:Jean_Heimburger.png‎|40px]]
* Lastname Firstname: [[Jean_Heimburger | Heimburger Jean ]]
* Age: 57
* Coming from (town, country): Walscheid (57), France
* Arrival date and hour: Friday 12:00
* Departure date and hour: Sunday 16:00
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Mercure
* Book hotel for me (yes/no): yes
* Contact email: jean.heimburger@tiaris.info

[[File:Laurent_Destailleur‎.png|40px]]
* Lastname Firstname: [[Laurent Destailleur|Laurent Destailleur]]
* Age: 45
* Coming from (town, country): Pessac (33), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): To be defined
* Book hotel for me (yes/no): yes
* Contact email: eldy@destailleur.fr

[[File:Philippe.GRAND.jpg|40px]]
* Lastname Firstname: [[Philippe Grand|Philippe Grand]]
* Age: unknown
* Coming from (town, country): Olivet (45), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): To be defined
* Book hotel for me (yes/no): no
* Contact email: philippe.grand@atoo-net.com

[[File:Maxime_Kohlhaas.png|40px]]
* Firstname Lastname:[[Maxime Kohlhaas]]
* Age: 30
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: To be defined
* Departure date and hour: To be defined
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…):Hotel Mercure
* Book hotel for me (yes/no): yes
* Contact email: maxime@atm-consulting.fr

[[File:Florian Henry.png|40px]]
* Lastname Firstname: [[Florian Henry]]
* Age: 37
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: No
* Departure date and hour: No
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Hotel Mercure
* Book hotel for me (yes/no): yes
* Email for contact: florian.henry@atm-consulting.fr

[[File:Alexis Algoud.png|40px]]
* Lastname Firstname: [[Alexis Algoud]]
* Age: 37
* Coming from (town, country): Valence (26000), France
* Arrival date and hour: No
* Departure date and hour: No
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): Hotel Mercure
* Book hotel for me (yes/no): yes
* Email for contact: alexis@atm-consulting.fr

[[File:.png|40px]]
* Lastname Firstname: [[Anthony Damhet]]
* Age: 33
* Coming from (town, country): Angoulême (16000), France
* Arrival date and hour: No
* Departure date and hour: No
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): self
* Book hotel for me (yes/no): no
* Email for contact: anthony.damhet@gmail.com

[[File:.png|40px]]
* Lastname Firstname: [[Olivier Tourvieille]]
* Age: 49
* Coming from (town, country): Angoulême (16000), France
* Arrival date and hour: No
* Departure date and hour: No
* Transportation (Train/Bus/Car/Plane): Train
* Food (Special diet, allergies, vegetarian…): None
* Accommodation (Common booked hotel/self…): self
* Book hotel for me (yes/no): no
* Email for contact: o.tourvieille@gmail.com