Line 1:
Line 1:
+
__NOINDEX__
{{TemplateAssoEn}}
{{TemplateAssoEn}}
−
[[Category:Foundation]]
+
[[Category:DevCamps]]
−
This page will resume typical action to organise a Dev'Camp.
+
+
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: ___________
+
*Main language used: _______ (french, english ?)
+
+
==Organizers==
+
Define name of organizers and managers (may be the same guys):
+
+
*Location manager: _____________
+
*Communication manager: _____________
+
*Sponsor manager (not mandatory): _____________
−
= Why =
+
==Dates==
−
== What is a Dev'Camp ==
+
Event dates and duration must be defined (one day, two days, three…): _________
−
Most of the time a Dev'Camp is a meeting between all kind of contributors around a specfics technologies to provide training, remind best practice, excahnge non formal inforamtion, improve massively a product.
+
Limit date for registration: _________
−
Commonly a Dev'Camps is on a short time range, like a week-end or a week during manisfestation.
−
== Who can go to a Dev'Camp ==
+
==Location==
−
All kind of contributors (developpers,documentation writers) can go to a dev'camp. But a leader have to be designated to schedule the programms.
−
Expert members will indicate and communicate about the technologies and can help beginner.
−
== What kind of topic is in Dev'Camp ==
+
*Be sure the location where you want to organize is ok regarding security, mobility and insurance.
−
* Training
+
*Following data must be defined:
−
* Special feature to build (may be the goal of a Dev'Camp)
+
**Location for food: ________________________ (provide name of room or address for lunch. Better with link to openstreetmap)
−
* Update project documentation
+
**Location for bedrooms: ____________________ (provide address of sleeping rooms or nearest hotels. Better with link to openstreetmap)
+
**chairs: _____________
+
**tables: _____________
+
**video projector: _____________
−
= Organization =
+
==Planning suggestion==
−
To start orgnization of a devcamp, first thing to do is to create a wiki page with answers of several questions.
−
To save time, you can copy the template used for: [[HackWeek_2010_Organisation]]
−
== Organizers ==
+
*Define a suggestion of Planning
−
Define name of organizators and responsibles (may be the same guy):
−
* Responsible of location: _____________
−
* Responsible for food: ____________
−
* Responsible of communication: _____________
−
* Responsible of sponsor (not mandatory): _____________
−
== Define dates ==
+
=Organization live=
−
Dates and duration of event must be defined (one day, two days, three...).
+
Once your draft page with all information you know are filled, you can submit it to the Dolibarr foundation: contact@dolibarr.org.
−
But also limit date for subsriptions.
+
You can send also the quotes your received from hotels, for rooms and foods.
−
== Find a place ==
+
The foundation will exhange with you on the basis of this informations.
−
* Be sure the place where you want to organize is ok regarding security, mobility and insurance.
−
* Following data must be defined:
−
** Location for food: ________________________
−
** Location for bedrooms: ____________________
−
** chairs: _____________
−
** tables: _____________
−
** video projector: _____________
−
== Suggestion of plan ==
+
The Dolibarr foundation will:
−
* Define a suggestion of Plan
−
== Launch communication ==
+
*pay the credit note for booking hotel or restaurant
−
* Once decision to start a devcamp is ok, launc communication to ask people to register to devcamp add their name into wiki page of the devcamp.
+
*make the communication to ask registration
−
* Helping by a mailling list or community web site, launch the communication. 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 cafenine into code line.
+
*manage and receive the registration to the events
−
* Include map of location
+
*give you the final list of names of participant
−
* Once devcamp is finished, build a page to show everybody what happened. An example can be found here: [[Compte_rendu_Hackweek_2010]].
−
== Participants ==
+
==Sponsoring==
−
Add an area into the wiki page to allow every possible participant to enter its date preferences (if several suggestions were done) and how to register.
+
Some sponsors can contribute to sponsor/fund the event if you find some.
−
== Sponsoring ==
+
==Example of past and next DevCamps==
−
Some sponsors can contributing to found the event.
+
See page [[:Category:DevCamps]]
+
[[Category:Development]]
+
[[Category:Foundation]]