- Loading...
- No images or files uploaded yet.
|
|
PubCamp 101
Hosted by Andy Carvin, Jonathon, Zach and Peter
PubCamp 101 from John Proffitt on Vimeo.
Public Media Camp Field Guide available
Everything associated is and must be licensed under CC.
Charter Document available online with the 10 basic rules: 1) it's all about strengthened public media through ongoing collaboration with the public. 2) There is no audience, only participants. 3) All presentations/sessions are on the record. 4) Any materials must be CC. 5) Check in must happen 6) If you lead a session you must speak up during intros 7) Law of Two Feet 8) Encourage team building and work doing 9) Post notes to wiki or blog 10) Soft-boiled rule.
Who can organize? Must be initiated by a Public Media station. Get these people to help develop it: * Public Media Initiator * Social Media Maven * The Promoter * The Geek * The Camp Counselor
Try and keep organizers to 4-5 so you don't have as hard of a time keeping meetings, etc. Try and get half from outside the station.
Who participates? *Public Media Staff *Tech Groups *Organizers and Activists *Citizen Journalists (they're good for shooting sessions, etc.) *Minority/Underserved Groups *Community Orgs/Schools (local hosts with a venue is great)
How to Garden the event using registration: 1) Notify/Save the Date * Figure out who is responding to this * Adjust based on that 2) Break out tickets between staffers, supporters, technologists 3) Sponsors are welcome and get them but there must be independence from product promotion, etc. These camps are not commercials. Keep sponsorship small to keep brands from trying to take ownership of the camp. Don't create tiers to help keep sponsorship spread out. Don't worry about getting lots of supplies for camps because it is more important to get people together to talk then it is to make it a big atmosphere. --- 30-40 people would be great for local pub camps. 4) Pub Camps are not outcome oriented, they are innovation and open format oriented. Create a blank canvas. Define your name/date/tag/logo and then build those into your tech: *blog for conversation *wiki for planning and repository *eventbrite for ticketing (there's a cost associated with this) *slideshare session content (you can create playlists) *google groups for community *twitter for logistics and alerts Example: PublicMediaCamp NYC or PublicMediaCamp WOSU be as local as possible with your naming convention. #PubCampMiss Tie it back to #pubcamp so tweet: just launched #pubcampNYC and want to invite you all at #pubcamp
Unconference should be a one day event.
Make a local version of the logo and you can reuse the pubcamp logo with fireball. It is important to pay homage to the camps that came before your's which is why the current logo was designed the way it was. The recommendation was not to use a year iteration.
What if you don't want to use the logo? Well you need to keep the lockup of the fireball and people. Make sure you carry the spirit of this but you can mash it up with something else.
Make sure to reshare anything you create.
Become an editor of publicmediacamp.org so that you can spread the word about your event and keep your resources available to everyone.
Create a new wiki page under wiki.publicmediacamp.org which is based on a PBWiki backend. *create an account *name the page based on your camp name e.g. PublicMediaCampMississippi *put this page in a folder "Local Camps" *choose the local camp template *follow the text in the template to create your initial page *don't forget to SAVE
Use google group to find user help when building pages
Use google forms and embed them into the wiki.
Remember the session programming happens "live" at the event so proposed sessions translate (or don't) at the day of the event.
Plenty of other information about PubCamp logistics, etc available in the pubcampguide.
One issue is banning powerpoint. Consider some other ways of presenting. Try and use locations that the chairs are not fixed. Take a look at using the "fishbowl" format.
post your notes to the wiki... |
Comments (0)
You don't have permission to comment on this page.