What this page is for
This is a guide for organizing FUDCon Live for a FUDCon. It is meant to be read by the organizers of FUDCon Live - in other words, they're "developer instructions." if you're an attendee at an event that has a FUDCon Live, you want to read the "user instructions" at FUDCon Live.
This page should detail what things in an event need to be documented, and to what level, latency, and amount of participation they need to be documented with. It should also walk you through a process for making sure all those things get documented for an event.
The remainder of this page is a DRAFT. We're working on it in gobby now. Mel Chua 16:54, 31 January 2010 (UTC)
What does a FUDCon Live document?
When applying FUDCon Live to a FUDCon, the following sessions should be covered:
| Session | Live streaming to remotees | Live participation by remotees | Files available afterwards |
|---|---|---|---|
| Barcamp kickoff and schedule creation | Yes, high-quality | Optional | On the FUDCon schedule page |
| State of Fedora address | Yes, high-quality | Yes, IRC projected on the wall | On the FUDCon schedule page, and (edited) on Fedora Insight afterwards |
| Barcamp sessions | Yes, whatever quality is available | Yes, IRC projected on the wall | On the FUDCon schedule page |
| Hackfests | Optional | Only mandatory if you want remote participation (which we strongly suggest) | On the FUDCon schedule page |
| Other interviews/filming on the side | Optional | Optional | High-quality video edited and made available on Fedora Insight afterwards |
This page should detail what things in an event need to be documented, and to what level, latency, and amount of participation they need to be documented with.
Process
Equipment
- Aside from the projector present for presentations, a second cheap portable projector to put up on a side wall is helpful so people can follow the IRC discussion
- A camera and microphone to record the presentation
- An onsite gobby server for local fast access to gobby
- Contact #fedora-admin to arrange for an outgoing tunnel to a Fedora Infrastructure colo server to get outside access
- An onsite coccinella server for local fast access
- Contact #fedora-admin to arrange for an outgoing tunnel to a Fedora Infrastructure colo server to get outside access
- A spare laptop or two in case someone needs it for transcribing (probably not necessary)
- For the one organising, bring your laptop and make sure you're connected to all the channels, by proxy if needed
- You will want to make sure you have a complete backup of the logs in case anything goes wrong
- Clint Savage or his clone to do a good job on the A/V work
- A proxy for streaming audio and video on Fedora Infrastructure so bandwidth isn't clogged hosting those streams
- A prepared livecd or usb with the programs needed to do the necessary tasks