Paris Code Sprint 2016 : XP - Revision history

Neteler: /* Food and drink */ +cat

2016-05-18T07:29:57Z

Food and drink: +cat

2016-03-15T18:11:28Z

Communication

2016-03-15T18:08:45Z

Food and drink

2016-03-15T18:08:29Z

2016-03-14T18:28:34Z

Communication

2016-03-14T18:27:30Z

Communication

2016-03-14T18:21:49Z

Event dynamic

2016-03-14T18:21:15Z

Event dynamic

2016-03-14T18:21:04Z

Event dynamic

2016-03-14T18:19:13Z

Event dynamic

← Older revision		Revision as of 07:29, 18 May 2016
Line 58:		Line 58:
	- Open bar on evening time is appreciated (what a surprise).		- Open bar on evening time is appreciated (what a surprise).

−	- D1 meal trays (on lunch time) ~~were~~'nt such a good idea (even if practical)	+	- D1 meal trays (on lunch time) weren't such a good idea (even if practical)
		+
		+
		+	[[Category:Code Sprints]]
		+	[[Category:C Tribe Code Sprint]]

@@ Line 16: / Line 16: @@
 == Communication ==
-- Using only TOSPrint ML is not enough
+- Using only TOSPrint ML is clearly not enough (some/few attendees never even heard about it)
 * OSGeo discuss mailing list is a must (and also ML from projects wanted to been reached)
-* Tweeter (and if possible with a dedicated account for the event)
+* Using far more Tweeter (and if possible with a dedicated account for the event)
 - #TOSPrint should have been replaced by something like #CodeSprint #OSGeo (who reminds that TO refers to Toronto ?)
-- When you speak about money, far more people listen. And somehow it was also a way to promote this event (through funding stuff).
+- When you speak about money, discovered than far more people listen. And somehow it was also a way to promote this event (through funding stuff).
 - Use one mail time to time with several points stacked, increase chances to be read.
 - A nice event Logo was such an help to communicate
 == Event dynamic ==

@@ Line 50: / Line 50: @@
 == Food and drink ==
-- Quality and variety of food and drink was really targeted. To be noticed that attendees noticed it.
+- Quality and variety of food and drink were really targeted. To be noticed that attendees noticed it.
 - For a next edition keep in mind that ~10% of attendees are vegetarians.

@@ Line 4: / Line 4: @@
 == Organization ==
 - Attendees expected that D1 morning breakfast would be already available. And it wasn’t.
@@ Line 57: / Line 55: @@
 - Open bar on evening time is appreciated (what a surprise).

@@ Line 19: / Line 19: @@
 - Using only TOSPrint ML is not enough
-* OSGeo discuss mailing list
+* OSGeo discuss mailing list is a must (and also ML from projects wanted to been reached)
 * Tweeter (and if possible with a dedicated account for the event)
 - #TOSPrint should have been replaced by something like #CodeSprint #OSGeo (who reminds that TO refers to Toronto ?)

← Older revision		Revision as of 18:27, 14 March 2016
Line 28:		Line 28:

	- Use one mail time to time with several points stacked, increase chances to be read.		- Use one mail time to time with several points stacked, increase chances to be read.
		+
		+	- A nice event Logo was such an help to communicate

	== Event dynamic ==		== Event dynamic ==

@@ Line 47: / Line 47: @@
 - Evening places must allow to communicate easily in small groups.
-- Quite impressed about D0 participation, about half the sprinters were already there...
+- Quite impressed about D0 evening participation, about half the sprinters were already there... Welcoming event has to been kept...
 == Food and drink ==

← Older revision		Revision as of 18:21, 14 March 2016
Line 46:		Line 46:

	- Evening places must allow to communicate easily in small groups.		- Evening places must allow to communicate easily in small groups.
		+
		+	- Quite impress about D0 participation, about half the sprinters were already there...

	== Food and drink ==		== Food and drink ==

@@ Line 33: / Line 33: @@
 - We avoid every time we could to interrupt the whole sprint at once (for speechs, announces and so on…). Sponsors could have a kakemono, but no dedicated time for a speech. No D1 welcome speech, nor ending one on D4…
-- Forget any kind of evening event not strictly related to code and projects, nobody care.
+- Forget any kind of evening event not strictly related to code and projects, nobody care (for similar reasons "break ideas" were useless).
 - D2 evening is a good timing to let everyone talk about what he do. It let time enough to anyone to really get in.