<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.creativecommons.org/index.php?action=history&amp;feed=atom&amp;title=Global_Melt%2FCommunication_Outreach</id>
		<title>Global Melt/Communication Outreach - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.creativecommons.org/index.php?action=history&amp;feed=atom&amp;title=Global_Melt%2FCommunication_Outreach"/>
		<link rel="alternate" type="text/html" href="https://wiki.creativecommons.org/index.php?title=Global_Melt/Communication_Outreach&amp;action=history"/>
		<updated>2026-05-13T12:28:49Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://wiki.creativecommons.org/index.php?title=Global_Melt/Communication_Outreach&amp;diff=48114&amp;oldid=prev</id>
		<title>Siebrand: notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.creativecommons.org/index.php?title=Global_Melt/Communication_Outreach&amp;diff=48114&amp;oldid=prev"/>
				<updated>2011-03-28T15:19:46Z</updated>
		
		<summary type="html">&lt;p&gt;notes&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Create LinkedIn group&lt;br /&gt;
----&lt;br /&gt;
Scopes:&lt;br /&gt;
* global&lt;br /&gt;
* community&lt;br /&gt;
* individual&lt;br /&gt;
&lt;br /&gt;
What's in it for the different scopes?&lt;br /&gt;
&lt;br /&gt;
At different events I noticed seeing the same people, and it was hard to pull new people in. Decided to go further, experimenting with unusual names for events.&lt;br /&gt;
Not using organisation names. Let's come and talk about HTML 5. Related to the mission, but not necessarily connected to the company. People were interested,&lt;br /&gt;
and new faces showed up. This event has one of the best attendences of events organised in Barcelona.&lt;br /&gt;
&lt;br /&gt;
Motivator for non-community members: learn about something new.&lt;br /&gt;
&lt;br /&gt;
Drumbeat is a Mozilla initiative, movement. Connect people with idaes and creating open tools and improve participation and make the web better.&lt;br /&gt;
&lt;br /&gt;
How do you decide what is interesting and relevant to your mission? How to select the crowd you want to attract and then attract them?&lt;br /&gt;
&lt;br /&gt;
KDE: has big forum website. Many users and discussions between users. Challenge: involve more users, or get more contributors or promotors? &lt;br /&gt;
&lt;br /&gt;
Goal: attract new users.&lt;br /&gt;
&lt;br /&gt;
Goal: attract new developers.&lt;br /&gt;
&lt;br /&gt;
Goal: involve existing users.&lt;br /&gt;
Same event as below.&lt;br /&gt;
&lt;br /&gt;
Goal: attract new contributors.&lt;br /&gt;
Combine mini-exhibition with existing contributors. Attracted new contributors through non-technical communities. Promotion: flyers distributed by volunteers in public place.&lt;br /&gt;
Media attention generated through networks of exiting volunteers.&lt;br /&gt;
&lt;br /&gt;
Prototyping. Used wp10 as an opportunity for outreach.&lt;br /&gt;
&lt;br /&gt;
Building your partners: Identified possible needs -&amp;gt; available strategies -&amp;gt; available networks -&amp;gt; potential partners&lt;br /&gt;
&lt;br /&gt;
What's in it for me? -&amp;gt; stories. Identify people in your organisation that have the skills to tell/find stories, and use them setting up and framing your events.&lt;br /&gt;
How do you maintain relationships if your travelling circus goes to another town next year?&lt;br /&gt;
Follow-up, follow through, &lt;br /&gt;
Contacts with sponsors&lt;br /&gt;
Doing a few things really well is better than doing a lot of things half.&lt;br /&gt;
Think about derivative works.&lt;br /&gt;
Which people need to be talking to each other before the event in order to make it (more) succesful&lt;br /&gt;
Evaluate after event, document the results/stories, update your best practices&lt;br /&gt;
Agile conference planning&lt;br /&gt;
&lt;br /&gt;
How do you keep track of how far it spread and how to identify blind spots? By analysing feedback forms and updating best practices and checklists.&lt;br /&gt;
How do you increase the percentage of attendees that provide feedback? Not discussed.&lt;br /&gt;
Takeaways. How do they contribute to outreach after the event? Have you thought about what you want to achieve with swag? Consider how it could provoke action!&lt;br /&gt;
Think about who you are going to create the swag for. Examples: Google handing out Android phone. Not being done in cheap swag as far as we know!!!&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
* global, community, individual&lt;br /&gt;
* Travelling circus vs garden growing&lt;br /&gt;
* Building your partners: Identified possible needs -&amp;gt; available strategies -&amp;gt; available networks -&amp;gt; potential partners. Travelling circus vs. growing garden.&lt;br /&gt;
* Get story tellers in contact with your event planners. This will create more attractive events.&lt;br /&gt;
* Let documentation not be an afterthought. Create it and update it!&lt;br /&gt;
* Takeaways: purpose an audience&lt;br /&gt;
* Collect feedback in every stage and act on it.&lt;br /&gt;
* Swag should provoke action!&lt;/div&gt;</summary>
		<author><name>Siebrand</name></author>	</entry>

	</feed>