28,936
edits
Changes
→Launch communication
Line 70:
Line 70:
# Start to fille it with name, dates, places
# Start to fille it with name, dates, places
# Submit page to the Dolibarr foundation board team to complete, feedbacks...
# 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, poviding the limit date to apply.
+# 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, poviding 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 cafenine into code line.
# 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.
# Once devcamp is finished, build a page to show everybody what happened. An example can be found here: [[Compte_rendu_Hackweek_2010]].
# Once devcamp is finished, build a page to show everybody what happened. An example can be found here: [[Compte_rendu_Hackweek_2010]].