|
|
| Line 27: |
Line 27: |
| * annual heavy weights that draw in more numbers and accelerate a range of projects crossing number of topics. | | * annual heavy weights that draw in more numbers and accelerate a range of projects crossing number of topics. |
| * intense involvement from staff and community. | | * intense involvement from staff and community. |
|
| |
| ==Structure - small events==
| |
|
| |
| * many small city-level events lead to big global festival once per year
| |
| * do as many as we can Q1 and Q2 this year
| |
|
| |
| * small events -> pick 3 - 5 cities where we have good networks and ground people
| |
| * run mini-Drumbeat Festivals (need a name a good as Penguin Day)
| |
| * could be 1 day events, like a barcamp but w/ more focus and energy
| |
| * primarily local, not residential or paid travel except as below
| |
|
| |
| * CRITICAL DESIGN QUESTION:
| |
| ** are these on the general open web and participation theme (like Pengiun Day), or do we pick a sub-theme where we have local skills (e.g. privacy or web education)?
| |
|
| |
| * use these as a staging grounds for people who will run similar events in other cities
| |
| * invite people to propose other events in advance online / in wiki etc.
| |
| * give plane tickets to (top 5? top 10?) pitches / people
| |
| * these people get training day before event, plus help run event
| |
|
| |
| * write up very simple online instructions re: how to org your own event
| |
| * steal a little bit from ignite and tedx in terms of simplicity of instructions
| |
| * obviously, wiki / photo / video blog outputs also critical to replication and buzz
| |
|
| |
|
| ==Structure - big event== | | ==Structure - big event== |