Creative Commons - User contributions [en]

Global Melt/Sparklez

2011-06-20T17:29:10Z

Asaf: /* Known Deployments */

=Sparklez=
== initial notes ==

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

== 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.

'''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)

==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)

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

Global Melt/Sparklez

2011-06-20T17:28:34Z

Asaf: /* Known Deployments */

=Sparklez=
== initial notes ==

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

== 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.

'''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)

==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)

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

Global Melt/Sparklez

2011-04-03T20:29:26Z

Asaf: /* Known Deployments */ adding explicit invitation

=Sparklez=
== initial notes ==

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

== 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.

'''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)

==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)

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

User:Asaf

2011-04-01T18:49:28Z

Asaf: Basics

My name is Asaf Bartov. I work for the Wikimedia Foundation in the Global Development team. Among other things, I am in charge of the Foundation's grants program.

I have participated in [[Global Melt]] 2011 in Berlin.

I am reachable via e-mail: asaf AT wikimedia DOT org

Global Melt/Sparklez

2011-04-01T18:49:04Z

Asaf: /* Sparklez */ known deployments

=Sparklez=
== initial notes ==

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

== 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.

'''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)

==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)

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

Global Melt/Sparklez

2011-04-01T18:45:50Z

Asaf: /* Sparklez */ sample e-mail