Changes

no edit summary
Line 3: Line 3:  
This page will resume typical action to organise a Dev'Camp.
 
This page will resume typical action to organise a Dev'Camp.
   −
= What is a Dev'Camp =
+
= Why =
 +
== What is a Dev'Camp ==
 +
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.
 +
Commonly a Dev'Camps is on a short time range, like a week-end or a week during manisfestation.
   −
  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.
+
== Who can go to a Dev'Camp ==
  Commonly a Dev'Camps is on a short time range, like a week-end or a week during manisfestation.
+
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.
   −
= Who can go to a Dev'Camp =
+
== What kind of topic is in Dev'Camp ==
  All kind of contributors (developpers,documentation writers) can go to a dev'camp. But a leader have to be designated to schedule the programms.
+
* Training
  Expert members will indicate and communicate about the technologies and can help beginner.
+
* Special feature to build (may be the goal of a Dev'Camp)
 +
* Update project documentation
   −
= What kind of topic is in Dev'Camp =
+
= Organization =
  - Training
+
To start orgnization of a devcamp, first thing to do is to create a wiki page with answers of several questions.
  - Special feature to build (may be the goal of a Dev'Camp)
+
Template to use is: [[HackWeek_2010_Organisation]]
  - Update project documentation
     −
= Find a place =
+
== Responsible ==
  Be sure the place where you want to organize is ok regarding security, mobility and insurance.
+
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): _____________
   −
= Launch communication =
+
== Define dates ==
  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.
+
Dates and duration of event must be defined (one day, two days, three...).
 +
But also limit date for subsriptions.
   −
= Sponsoring =
+
== Find a place ==
  Some sponsors can contributing to found the event.  
+
* Be sure the place where you want to organize is ok regarding security, mobility and insurance.
 +
* Following data must be defined:
 +
** Location
 +
** chairs
 +
** tables
 +
** video projector
   −
= Dolibarr Dev'Camp =
+
== Launch communication ==
  A dev'Camp was organised in 2010.
+
* 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.
 +
* 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.
 +
* Include map of location
 +
* Once devcamp is finished, build a page to show everybody what happened. An example can be found here: [[Compte_rendu_Hackweek_2010]].
 +
 
 +
== Participants ==
 +
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.
 +
 
 +
== Sponsoring ==
 +
Some sponsors can contributing to found the event.