Global Melt/Sparklez - Revision history

Asaf: /* Known Deployments */

2011-06-20T17:29:10Z

Known Deployments

← Older revision		Revision as of 17:29, 20 June 2011
Line 43:		Line 43:

	==Known Deployments==		==Known Deployments==
	# Global Melt 2011, Berlin (v1)		# Global Melt 2011, Berlin (v1) -- reminders sent!
	# KDE Calligra Sprint, April 2011, Berlin (v1)		# KDE Calligra Sprint, April 2011, Berlin (v1)
	# Create Your Own 2011, May 30-31 2011, Berlin [www.cyo2011.com]		# Create Your Own 2011, May 30-31 2011, Berlin [www.cyo2011.com] (v1)
	# Libre Graphics Meeting, May 2011		# Libre Graphics Meeting, May 2011 (V1)
	# (your upcoming event?)		# (your upcoming event?)

Asaf: /* Known Deployments */

2011-06-20T17:28:34Z

Known Deployments

← Older revision		Revision as of 17:28, 20 June 2011
Line 45:		Line 45:
	# Global Melt 2011, Berlin (v1)		# Global Melt 2011, Berlin (v1)
	# KDE Calligra Sprint, April 2011, Berlin (v1)		# KDE Calligra Sprint, April 2011, Berlin (v1)
	# Create Your Own 2011, May 30-31, Berlin [www.cyo2011.com]		# Create Your Own 2011, May 30-31 2011, Berlin [www.cyo2011.com]
			# Libre Graphics Meeting, May 2011
	# (your upcoming event?)		# (your upcoming event?)

Asaf: /* Known Deployments */ adding explicit invitation

2011-04-03T20:29:26Z

Known Deployments: adding explicit invitation

← Older revision		Revision as of 20:29, 3 April 2011
Line 46:		Line 46:
	# KDE Calligra Sprint, April 2011, Berlin (v1)		# KDE Calligra Sprint, April 2011, Berlin (v1)
	# Create Your Own 2011, May 30-31, Berlin [www.cyo2011.com]		# Create Your Own 2011, May 30-31, Berlin [www.cyo2011.com]
			# (your upcoming event?)

Nadia EL-Imam: /* Known Deployments */

2011-04-03T08:39:44Z

Known Deployments

← Older revision		Revision as of 08:39, 3 April 2011
Line 45:		Line 45:
	# Global Melt 2011, Berlin (v1)		# Global Melt 2011, Berlin (v1)
	# KDE Calligra Sprint, April 2011, Berlin (v1)		# KDE Calligra Sprint, April 2011, Berlin (v1)
	# ~~(your upcoming event?)~~		# Create Your Own 2011, May 30-31, Berlin [www.cyo2011.com]

Asaf: /* Sparklez */ known deployments

2011-04-01T18:49:04Z

Sparklez: known deployments

← Older revision		Revision as of 18:49, 1 April 2011
Line 41:		Line 41:

	(Sparkle was invented and first implemented in Global Melt Berlin 2011)		(Sparkle was invented and first implemented in Global Melt Berlin 2011)

			==Known Deployments==
			# Global Melt 2011, Berlin (v1)
			# KDE Calligra Sprint, April 2011, Berlin (v1)
			# (your upcoming event?)

Asaf: /* Sparklez */ sample e-mail

2011-04-01T18:45:50Z

Sparklez: sample e-mail

← Older revision		Revision as of 18:45, 1 April 2011
Line 19:		Line 19:

	(hat tip to Charlie for articulating the above)		(hat tip to Charlie for articulating the above)

			==Sample Sparkle E-mail from Organizers==
			Hi, <name>.

			This is a one-time reminder you have asked to receive: Back in <month and year>, you participated in <event> at <location>, where the organizers committed to help you make the most of the “Sparklez” you had with other participants during the event. <x months> have passed and we’re sending all Sparklers a mutual reminder of your Sparkcontacts and the conversation context you provided during the event.

			Below is a list of Sparklez you are part of. Please note that you don’t HAVE to act on any of them, and that none of your contact information (not even your e-mail) was shared with anyone apart from us. For your convenience, we offer some action buttons beside each Sparkle:

			* SNOOZE would make our system send you another reminder about the Sparkle in ONE MONTH.
			* SHARE would let you report progress already made on the Sparkle – the organizers will share a concise report of cool things that happened or are happening as a result of Sparkles generated at the event.
			* CONNECT will ask you for your contact information and an optional personal message. Once submitted we’ll deliver it to the person you Sparkled with - Let the ideas flow! You will also be offered to SNOOZE the Sparkle to give you time to act on your Sparkle.
			* FORGET would make our system close the Sparkle and never mention it again. This is what you should pick if you don’t remember making a Sparkle with that person and are not interested in getting in touch with them.
			So here are your Sparklez:

			# Sparkled with <name> [and <name>] about <context/topic> -- [SNOOZE] [SHARE] [CONNECT] [FORGET]
			# Sparkled with <name> [and <name>] about <context/topic> -- [SNOOZE] [SHARE] [CONNECT] [FORGET]

			Have fun, and make cool things happen!

			-- From the organizers of <event>

			(Sparkle was invented and first implemented in Global Melt Berlin 2011)

Metasj: /* initial notes */

2011-03-29T18:26:46Z

initial notes

← Older revision		Revision as of 18:26, 29 March 2011
Line 1:		Line 1:
	=Sparklez=		=Sparklez=
	==initial notes ==		== initial notes ==

	<big>[http://www.flickr.com/photos/pipstar/sets/72157626379423306/with/5571329486/ added on Flickr]</big>		<big>[http://www.flickr.com/photos/pipstar/sets/72157626379423306/with/5571329486/ added on Flickr]</big>


	later notes --		== later notes ==

	'''Purpose''' -- finding the best ways... to cherish sparks that happen between people @ live events.		'''Purpose''' -- finding the best ways... to cherish sparks that happen between people @ live events.

Metasj: /* initial notes added on Flickr */

2011-03-29T15:18:54Z

initial notes added on Flickr

← Older revision		Revision as of 15:18, 29 March 2011
Line 1:		Line 1:
	=Sparklez=		=Sparklez=
	==initial notes added on Flickr==		==initial notes ==

			<big>[http://www.flickr.com/photos/pipstar/sets/72157626379423306/with/5571329486/ added on Flickr]</big>

	~~[http://www.flickr.com/photos/pipstar/sets/72157626379423306/with/5571329486/ Sparklez notes]~~

	later notes --		later notes --

Metasj: /* initial notes added on Flickr */

2011-03-29T15:18:31Z

initial notes added on Flickr

← Older revision		Revision as of 15:18, 29 March 2011
Line 15:		Line 15:
	: At events without a [fill register?] need -- participanst willing to put emails addresses and sparklez on a wall poster.		: At events without a [fill register?] need -- participanst willing to put emails addresses and sparklez on a wall poster.

	'''~~Principe~~''' - Creating a system /more/ work intensive than the xisting setup (biz cards, pens, emmory) does not cherish the sparks, so does not meet our purpose.		'''Principle''' - Creating a system /more/ work intensive than the xisting setup (biz cards, pens, emmory) does not cherish the sparks, so does not meet our purpose.

			(hat tip to Charlie for articulating the above)

Metasj: /* Sparklez */

2011-03-29T15:18:07Z

Sparklez

← Older revision		Revision as of 15:18, 29 March 2011
Line 3:		Line 3:

	[http://www.flickr.com/photos/pipstar/sets/72157626379423306/with/5571329486/ Sparklez notes]		[http://www.flickr.com/photos/pipstar/sets/72157626379423306/with/5571329486/ Sparklez notes]

			later notes --

			'''Purpose''' -- finding the best ways... to cherish sparks that happen between people @ live events.

			'''First hunch''' -- Organisr commits to follow up, when aprticipants hand in 2 email addresses and a 1-line spark description.

			'''Simplest unit?''' - An event organizer just exlpanis what a sparkle is, and provides a big sheet of paper on which they are tracked.

			'''Lightest system?''' Needs: willing event organiser / sparklez admin to oversee the follow-up (using followup.cc, et al).
			: At events without a [fill register?] need -- participanst willing to put emails addresses and sparklez on a wall poster.

			'''Principe''' - Creating a system /more/ work intensive than the xisting setup (biz cards, pens, emmory) does not cherish the sparks, so does not meet our purpose.