From Fedora Project Wiki

m (added header)
 
(131 intermediate revisions by 13 users not shown)
Line 1: Line 1:
{{header|events}}
This is the main page for the 2010 Events FAD, which is a [[FAD]] focused on tools, infrastructure, and materials for Fedora events, with a focus on [[FUDCon|FUDCons]] (though much of the work will likely be reusable for [[FAD|FADs]] themselves).
This is the main page for the 2010 Events FAD, which is a [[FAD]] focused on tools, infrastructure, and materials for Fedora events, with a focus on [[FUDCon|FUDCons]] (though much of the work will likely be reusable for [[FAD|FADs]] themselves).


== Status ==
== Remaining TODOs ==


Discussion and coordination are happening on the [https://admin.fedoraproject.org/mailman/listinfo/fudcon-planning fudcon-planning] list, but this wiki page is the canonical reference to the status of this event's planning.
* Max -- pay for everything hotel-related.
* Mel -- finalize transportation plan back to the airport.
* Max & Mel -- file expense reports.


=== Meetings ===
== Pages we've worked on ==


In #fudcon-planning.
These pages need to have redirects made, be categorized, linked to each other, etc.


* 1700-1800 UTC (noon-1pm EST) on Mondays
* [[FUDCon]]
* 2100-2200 UTC (4-5pm EST) on Thursdays (our old FUDCon organizers
* [[FAD]]
meeting time)
* [[Premier Fedora Events]]
* [[FUDCon Planning FAD]]
* [[FUDCon organization process]] which needs to have [[FUDCon design]] and [[FUDCon:Organization]] content merged into it.
* [[FUDCon bid process]] - which [[FUDCon_and_FAD_locations]] need to be merged into.
* [[Sponsoring_event_attendees]] needs to be linked to from [[Events]] and from somewhere in [[FAMSCO]].
* [[Audio Video Kit]]
* [[FUDCon:Santiago 2010]] (as test of the above)
* [[FUDCon Live]] and [[FUDCon Live organization process]]


There are 6 planning meetings: March 11, 14, 18, 21, 25 and 28.
=== To finish this section ===
 
Ensure all docs and wiki pages linked or referred to from (in order of priority):
# <s>[http://lists.fedoraproject.org/pipermail/fudcon-planning/2010-January/000528.html Max's email]</s> (done)
# the [[Events_FAD_2010]] page
# the entire weekend's IRC logs
## [http://meetbot.fedoraproject.org/fad/2010-01-29/ Friday, #fad]
## [http://meetbot.fedoraproject.org/fedora-fad/2010-01-29/ Friday, #fedora-fad]
## [http://meetbot.fedoraproject.org/freeseer/2010-01-29/ Friday, #freeseer]
## [http://meetbot.fedoraproject.org/fad/2010-01-30/ Saturday, #fad]
## [http://meetbot.fedoraproject.org/fedora-fad/2010-01-30/ Saturday, #fedora-fad]
## [http://meetbot.fedoraproject.org/freeseer/2010-01-30/ Saturday, #freeseer]
## [http://meetbot.fedoraproject.org/fad/2010-01-31/ Sunday, #fad]
## [http://meetbot.fedoraproject.org/fedora-fad/2010-01-31/ Sunday, #fedora-fad]
## [http://meetbot.fedoraproject.org/freeseer/2010-01-31/ Sunday, #freeseer]
## [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-31/ Sunday, #fudcon-planning]
...are (in order of priority)
# status updated (with an admon note)
# properly categorized
# link to each other where appropriate
# have consistent, up-to-date content (If you can't update a page in less than 15 minutes, give it to Jon (jds2001) to put on the "FAD Followup" list.)
The end deliverable here is a link to a wiki category page that lists all the pages that we worked on this weekend.


The agenda for each, until further notice, will be:
# proposal/budget approval
# FAD agenda-setting and logistics arrangement
# prepwork to gear up for things specified in #2 and funded by #1.


* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-20/fudcon-planning.2010-01-20-20.40.html 2010-01-20 belated weekly planning meeting, logistics budget wrapup]
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-15/fudcon-planning.2010-01-15-02.36.html 2010-01-15 freeseer tech discussion]
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-11/fudcon-planning.2010-01-11-17.02.html 2010-01-11 planning meeting 2]
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-09/fudcon-planning.2010-01-09-06.59.html 2010-01-09 planning meeting 1]


== Schedule ==
== Schedule ==
Line 29: Line 53:
=== Thursday January 28 ===
=== Thursday January 28 ===


Most folks will be arriving on this day.  Nothing formal scheduled, though we'll make sure that people have the opportunity to coordinate arrival times and travel to the hotel.
People arrived, a bit of pre-hacking. Some blog posts, below.
 
* [http://marilyn.frields.org:8080/~paul/wordpress/?p=2985 Paul Frields: "Road dogging, no. 14."]
* [http://sexysexypenguins.com/2010/01/28/events-fad-day-0/ Clint Savage: "Events Fedora Activity Day: Day 0"]
* [http://blog.melchua.com/2010/01/29/events-fad-day-1/ Mel Chua: "Events FAD: Day -1"] (Clearly Clint and I start counting on different days.)
 
=== Friday January 29 ===
 
'''IRC logs available:'''
 
* [http://meetbot.fedoraproject.org/fedora-fad/2010-01-29/fedora-fad.2010-01-29-14.31.html #fedora-fad (FUDCon 2.0 track)]
* [http://meetbot.fedoraproject.org/fad/2010-01-29/fad.2010-01-29-14.31.log.html #fad (initial brainstorming, then FUDCon Live track)]
* [http://meetbot.fedoraproject.org/freeseer/2010-01-29/freeseer.2010-01-29-15.47.html #freeseer (Freeseer hacking as part of FUDCon Live track)]
 
'''Blog posts:'''
 
* [http://blog.melchua.com/2010/01/30/events-fad-day-0/ Mel Chua: "Events FAD: Day 0"]
* [http://blog.jds2001.org/random_thoughts/2010/01/fedora-events-fad---days-0-1.html Jon Stanley: "Fedora Events FAD - Days 0-1"]
* [http://spevack.livejournal.com/97742.html Max Spevack: "fedora activity day -- events -- day 1"]
9:30 AM -- StartShort opening talk by Max to make sure everyone knows what's going on from a logistics point of view, remind folks of the goals for the weekend, and documentation/publicity of our FAD.  Make sure that remote participation is up and running properly. '''Update:''' Make plans in case of inclement weather.
 
'''Schedule:'''
 
10:00 AM - 1:00 PM -- Break up into our two tracks.
 
10:30 AM - AVBox track begins hacking in #freeseer. FUDCon 2.0 track is iterating on [[FUDCon#FUDCon_calendar]].


=== Friday January 29 - Sunday January 31 ===
1:00 PM - 2:00 PM -- Lunch will be delivered.  Sub sandwiches from Jimmy John's, chips & drinks from Daddy Shadowman.


We will be meeting in the Augusta National conference room on the 5th floor of [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=900+main+campus+drive,+raleigh+nc,+27606&sll=35.781022,-78.68052&sspn=0.015632,0.027595&ie=UTF8&hq=&hnear=900+Main+Campus+Dr,+Raleigh,+Wake,+North+Carolina+27606&ll=35.775364,-78.67743&spn=0.007817,0.013797&z=16&iwloc=r4 Red Hat's Venture III building].  Since you need badge access, we should all meet in the lobby of the building at 9:30 AM each day.
2:00 PM - 6:00 PM -- Break up into our two tracks.


==== Friday January 29 ====
5:00 PM -- Hard stop for Max, who has to run an errand that can't be avoided before the social event.


9:30 AM -- Start.
6:00 PM -- Hard stop for everyone else, so that we can clean up and make it to our social event on time.


1:00 PM -- Lunch will be delivered.
7:10 PM -- [http://www.imaxraleigh.org/showtimes/ Avatar on the IMAX 3-D screen].  See [[Events FAD 2010#Avatar|below]].


7:10 PM -- [http://www.imaxraleigh.org/showtimes/ Avatar on the IMAX 3-D screen].
=== Saturday January 30 ===


==== Saturday January 30 ====
Original plans were scrapped in favor of continuing to work from the hotel, due to the (one-inch) "blizzard" that hit Raleigh Friday night.


9:30 AM -- Start.
=== Sunday January 31 ===


1:00 PM -- Lunch will be delivered.
Snow-in-Raleigh adventures continued, and we worked from the hotel for the last day as well.


Proposed social event -- Any ideas???
=== Post-Sunday reflections ===


==== Sunday January 31 ====
* [http://spevack.livejournal.com/98945.html Max Spevack, mentioning the FAD's results while thinking about FUDCon in EMEA at FOSDEM]
* [http://marilyn.frields.org:8080/~paul/wordpress/?p=2991 Paul Frields: "Events FAD 2010"]
* [http://spevack.livejournal.com/97809.html Max Spevack: "the future of fudcons"]
* [http://sexysexypenguins.com/2010/02/01/fedora-activity-days-1-3-a-frank-aka-francis-the-fedora-pwnie-report/ Clint Savage: "Fedora Activity Days 1-3 – A ‘Frank (aka Francis) the Fedora pwnie’ report"]


9:30 AM -- Start.
== Tracks ==


1:00 PM -- Lunch will be figured out, depending how many people are still at the FAD.
=== Track #1 -- FUDCon 2.0 ===


Afternoon -- Unscheduled, so that we have flexibility for final wrap-up activities.
Primary owner: Max
 
==== Overall goals ====
 
Refresh the entire "Premier Fedora Events" idea in our community.  Break it down to first principles and build it back up, eventually refining processes, decision-making, and ownership.  Then put this into practice as we plan 2010.
 
==== Friday ====
 
''Basically a design thinking day.''  We'll start with an introduction to the design thinking process.
 
Here is an initial set of ideas, to seed the session:
* At its core, what is FUDCon?  What purpose is it meant to have?
* If we were starting with the FUDCon idea right now, what are the goals that FUDCons should have?  Both from the regional and annual perspective, as well as from the user or developer perspective.  How do we decide what constitutes a good FUDCon?  Does the formula need to be the same everywhere?
* How do FADs interact with the FUDCon idea?  Are we properly incentivizing people to hold them?  What needs to be changed?
* Are there any big holes or things not being achieved within Fedora that the FUDCon/FAD model could be modified to solve?
* Generalized annual FUDCon cycle/calendar with FUDCons and Important Regional FADs and suggested times for them.
* Expand that generalized list out into the next 18 months, or so.
* What do we do with the following pages?
** https://fedoraproject.org/wiki/FUDCon:Organization
** https://fedoraproject.org/wiki/How_to_organize_a_FAD
** https://fedoraproject.org/wiki/FUDCon_and_FAD_locations
* BarCamp -- have we outgrown it, or did we Do It Wrong in Toronto?  How do we scale event registration and sessions scheduling?  Is a set of wiki pages for a FUDCon still ok?
* What is the ownership model for FUDCons and/or FADs?  Who is needed?  When does it need a stamp of approval to call itself a FUDCon or a FAD?  What is the RACI?
* How do we encourage people to do the "due diligence" and set up an informal sort of "bid process" around possible locations for FUDCons and FADs?  What sorts of facilities are the minimum required?
* How do we break down budget for a FUDCon or a FAD, and what does the sponsorship process look like?
* User versus Developer.
* Possible expansion to be more family friendly?
* A repository of FUDCon templates and materials (letters, posters, etc) with instructions for customization.
* FUDCon survey that can be used to chart our improvement over time.
 
==== Saturday ====
 
See [http://lists.fedoraproject.org/pipermail/fudcon-planning/2010-January/000528.html Max's summary email of progress from Saturday evening].
 
=====Action Items for Saturday=====
# Generic calendar FUDcons and Ambasador FAD with regional breakdowns
# 2010 instances communication
# [[FUDcon_bid_process | Bid process]] incorporating old locations wiki page
# Define [[Events_FAD_2010_Action_Items | things]] that received good feedback and should be constant
# List [[Events_FAD_2010_Action_Items | suggestions ]] for improvement that we need to act on
# HOWTO + Organization Page
# Clear attendee sponsorship process
 
===== Documents to draft =====
 
Here are the list of documents that we are teaming up to write and make available.
* Bid process and bid content -- '''Max, David'''
** This document will fix:
*** Less reliance on CommArch -- community ownership
*** Regional planned events by regional folks
*** Better local involvement
*** Establish approval process for FUDCon occurrence
** This document might fix:
*** Budget process
*** Food details
*** Location (south in winter, north in summer)
*** Whether to attach to other major events
* HOWTO run a FUDCon -- '''Chris, Mel'''
** This document will fix:
*** Ownership model -- RACI
*** Budget process
*** Repository of materials needed
*** Have clear deliverables for a FUDCon event
** This document might fix:
*** More social interaction
*** Encouraging new contributors to join
*** Providing a forum where people can ask "By the way" questions
*** Better on-ramping -- promoting connection to the community
*** Does not kill anyone
* Clear attendee sponsorship process doc -- '''Paul, Steven -- DONE! Refer to [[Sponsoring event attendees]]'''
** This document will fix:
*** Better budget/sponsorship process and tools
 
==== Sunday ====
 
''Basically a testing and putting-into-practice day.''
 
Testers of Saturday's work (in #fudcon-planning)
* 9:00 AM - 11:00 aM: FUDCon LATAM (Rodrigo Padula)
 
=== Track #2 -- FUDCon Live ===
 
Primary owner: Clint / Yaakov
 
==== Overall goals ====
 
# -- Define use cases for freeseer with regard to Fedora (and other community) events.
# -- Build freeseer software to meet top 2 or 3 use cases, beyond it's current capability.
# -- Get freeseer packaged into Fedora, including any gstreamer stuff that needs to happen.
# -- Get equipment purchased, tested, documented, etc.
# -- Create and test the participation and usage documentation, so that folks can run a FUDCon/FAD Live!
# -- Review the survey results and decide what we can do to make FUDCon/FAD Live a better experience
## Decide what our goals are
## Decide on the results we should see on the following survey
## Identify changes and the expected results
## After the next event or two, see if we've made improvement
# -- Document whatever is needed for worldwide replication, and any roadmap needed for future improvement.
 
==== Friday ====
 
The who's-working-on-freeseer-when schedule is available [http://wiki.github.com/fosslc/freeseer/jan-2010-freeseer-sprint-schedule on the freeseer wiki].
 
* As much of 1 and 2 as possible.
* Determine current state of 4 and where we need to get.
* Get any needed parts for 1 and 2.
* Discuss 5.
 
==== Saturday ====
 
* Accomplish the remainder of 2.
* Testing and progress of 1 with new versions of 2.
* Discuss 5 if not already done.
* Begin 3.
 
==== Sunday ====
 
* Finish 3.
* Discuss 6 if not already done.
* 7.
 
Wrap up the [[FUDCon Live]] page.


== Attendees ==
== Attendees ==


{|
{|
! # !! FAS Name &<br/>Full Name !! in-person or remote?
! # !! FAS Name &<br/>Full Name !! in-person or remote? !! remote attendance
|-
|-
| 1 || [[User:mchua|Mel Chua]] || in-person
| 1 || [[User:mchua|Mel Chua]] || in-person
Line 72: Line 244:
| 4 || [[User:ke4qqq|David Nalley]] || in-person
| 4 || [[User:ke4qqq|David Nalley]] || in-person
|-
|-
| 5 || [[User:ynemoy|Yaakov M. Nemoy]] || remote
| 5 || [[User:ynemoy|Yaakov M. Nemoy]] || remote || I don't think i can make it for most of friday except the first hour
|-
|-
| 6 || [[MaxSpevack|Max Spevack]] || in-person
| 6 || [[MaxSpevack|Max Spevack]] || in-person
Line 89: Line 261:
|-
|-
|13 || Thanh Ha || remote
|13 || Thanh Ha || remote
|-
|14 || [[User:Inode0|John Rose]] || remote
|-
|15 || [[User:Rodrigop|Rodrigo Padula]] || remote
|-
|-
|}
|}


=== A note on remote participation ===
=== A note on remote participation ===
<big><big><big>[http://meetbot.fedoraproject.org/fedora-fad/2010-01-29/fedora-fad.2010-01-29-14.31.log.txt Live log]</big></big></big>


This FAD is specifically designed to be a combined in-person/online event, echoing the FUDCon/FUDCon Live arrangement in real FUDCons so we can more effectively test the deliverables we are producing. Remote participation is ''crucial'' to the success of this FAD.
This FAD is specifically designed to be a combined in-person/online event, echoing the FUDCon/FUDCon Live arrangement in real FUDCons so we can more effectively test the deliverables we are producing. Remote participation is ''crucial'' to the success of this FAD.


== TODO ==
There is no prep needed for remote participation: just show up on IRC. Anything else we need to do at that point, we'll figure out at that point.
 
Remote participation will be coordinated over IRC. The main channel for the FAD will be #fad, with freeseer hacking happening in #freeseer.


* Mel -- get the attendee list finalized by January 17th, and any remaining travel purchased.
* 9:30am on Friday: kickoff in-person and on #fad
* Mel -- find out the subset of attendees who need a hotel room, and ask them to pair up with roommates.  Max's credit card can/will pay the bills.
* 10:30am on Friday: freeseer hacking kickoff in #freeseer
* Max -- sort out meals and social activities.
 
* In a planning meeting -- break the goals list down into sessions and slot those sessions into the different days that are available, and the collaboration tools that we're going to use and the specific deliverables that we want to achieve.
Further updates on remote participation will happen both in-channel and on the fudcon-planning mailing list. Generally speaking, we will be in #fad during the day when we are working on FAD things; please pop in and say hi and we'll help you get started.
* Mel -- Figure out what the actual plan for remote participation is.
* ??? -- Sort out transporation.
* Max & Mel -- file expense reports.


== Logistics & budget ==
== Logistics & budget ==


=== Transportation ===


As we get closer to the date, details will go here (airport pickups, rental cars, etc).
* [[User:Mchua|Mel Chua]] is driving from RDU to BOS after the FAD and can drop people off along the way back (I am arriving a week early, so I can't take people on the way down).


=== Travel ===
=== Travel ===
Line 125: Line 298:
| [[User:Jstanley]] || AA || AA 4423, JFK-RDU 01/28/2010 7:30EST || 01/28/2010 09:30EST || AA 4537, RDU-JFK 01/31/2010 06:05PM || 01/31/2010 7:55PM EST || $164.40 || [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-09/fudcon-planning.2010-01-09-06.59.html Purchased]
| [[User:Jstanley]] || AA || AA 4423, JFK-RDU 01/28/2010 7:30EST || 01/28/2010 09:30EST || AA 4537, RDU-JFK 01/31/2010 06:05PM || 01/31/2010 7:55PM EST || $164.40 || [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-09/fudcon-planning.2010-01-09-06.59.html Purchased]
|-
|-
| [[User:Ausil|Dennis Gilmore]] || AA || AA 4268, PIA-ORD 01/28/2010 10:00 CST || AA 454, ORD-RDU  01/28/2010 5:20 pm EST || AA 2091, RDU-ORD 01/31/2010 06:05PM EST || AA 4368 ORD-PIA 01/31/2010 10:25PM CST || $290.80 || [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-09/fudcon-planning.2010-01-09-06.59.html Purchased]
| [[User:Ausil|Dennis Gilmore]] || AA || AA 4157, PIA-ORD 01/28/2010 5:55 PM CST || AA 3881, ORD-RDU  01/28/2010 10:40 pm EST || AA 2091, RDU-ORD 01/31/2010 06:05PM EST || AA 4368 ORD-PIA 01/31/2010 10:25PM CST || $290.80 || [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-09/fudcon-planning.2010-01-09-06.59.html Purchased]
|-
|-
| [[User:Pfrields|Paul Frields]] || The FPL-mobile || Thursday || Thursday || Sunday || Sunday || $50 for gas || [http://lists.fedoraproject.org/pipermail/fudcon-planning/2010-January/000454.html APPROVED]
| [[User:Pfrields|Paul Frields]] || The FPL-mobile || Thursday || Thursday || Sunday || Sunday || $47.75 for gas || [http://lists.fedoraproject.org/pipermail/fudcon-planning/2010-January/000454.html Reimbursed]
|-
|-
| [[User:Ctyler|Chris Tyler]] || Delta ||Delta 6498 YYZ-JFK 11:50am || Delta 5482 JFK-RDU 4:35pm || Delta 6580 RDU-JFK 5:00pm || Delta 6763 JFK-YYZ 10:00pm || $489.70 || [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-14/fudcon-planning.2010-01-14-21.04.html PURCHASED]
| [[User:Ctyler|Chris Tyler]] || Delta ||Delta 6498 YYZ-JFK 11:50am || Delta 5482 JFK-RDU 4:35pm || Delta 6580 RDU-JFK 5:00pm || Delta 6763 JFK-YYZ 10:00pm || $489.70 || [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-14/fudcon-planning.2010-01-14-21.04.html PURCHASED]
|-
|-
| David Nalley || Nalley-mobile || Thursday || Thursday || Sunday || Sunday || $50 for gas || [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-20/fudcon-planning.2010-01-20-20.40.html APPROVED]
| David Nalley || Nalley-mobile || Thursday || Thursday || Sunday || Sunday || $37.15 for gas || [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-20/fudcon-planning.2010-01-20-20.40.html Reimbursed]
|-
|-
| People traveling by plane, returning to RDU airport || Supershuttle || || || || || $100 || budgeted
| || || || || || '''Total to date:'''|| $1320.60 ||
| || || || || || '''Total to date:'''|| $1435.70 ||
|-
|-
| Name || Carrier || Travel to FAD, departure || Travel to FAD, arrival || Travel from FAD, departure || Travel from FAD, arrival || Ticket cost ||  
| Name || Carrier || Travel to FAD, departure || Travel to FAD, arrival || Travel from FAD, departure || Travel from FAD, arrival || Ticket cost ||  
Line 142: Line 314:
=== Lodging ===
=== Lodging ===


We will be staying at:
We stayed at:


  Best Western Cary Inn And Extended Stay
  Best Western Cary Inn And Extended Stay
Line 153: Line 325:
! Roommate 1 !! Roommate 2 !! Check-in !! Check-out !! Nights !! Cost !! Status
! Roommate 1 !! Roommate 2 !! Check-in !! Check-out !! Nights !! Cost !! Status
|-
|-
| [[User:Herlo|Clint Savage]] || [[User:Pfrields|Paul W. Frields]] || Thu 2010-01-28 || Sun 2010-01-31 || 3 || see below || booked
| [[User:Herlo|Clint Savage]] || [[User:Pfrields|Paul W. Frields]] || Thu 2010-01-28 || Sun 2010-01-31 || 3 || see below || paid
|-
|-
| [[User:Mchua|Mel Chua]] || [[User:Ausil|Dennis Gilmore]] || Thursday|| Sunday || 3 || see below || approved
| Jon Stanley || [[User:Ausil|Dennis Gilmore]] || Thursday|| Sunday || 3 || see below || paid
|-
|-
| Chris Tyler || David Nalley || Thursday || Sunday || 3 || see below || booked
| Chris Tyler || David Nalley || Thursday || Sunday || 3 || see below || paid
|-
|-
| Jon Stanley || Roommate 2 || Thursday || Sunday || 3 || see below || booked
| Mel Chua || || Thursday || Sunday || 3 || $832.28 total for all 4 rooms || paid
|-
| Conference room || || Saturday || Sunday || 2 || $192.40 || paid
|-
|-
| Roommate 1 || Roommate 2 || Check-in || Check-out || Nights || Cost || Status
| Roommate 1 || Roommate 2 || Check-in || Check-out || Nights || Cost || Status
|-
|-
| || || || '''Total to date:''' || 12 || $659.88||  
| || || || '''Total to date:''' || 12 || $1024.68||  
|}
|}


=== Equipment ===
=== Equipment budget ===


What we don't spend on travel, we'll spend on getting equipment to start making this an option for Events Kits.
What we didn't spend on travel, we'll spend on getting equipment to start making this an option for Events Kits.
 
Equipment we looked at:


* http://www.google.com/products?q=vga2usb and http://www.google.com/products?hl=en&q=sennheiser%20ew100g2 and  
* http://www.google.com/products?q=vga2usb and http://www.google.com/products?hl=en&q=sennheiser%20ew100g2 and  
Line 176: Line 352:
* http://www.epiphan.com/products/frame-grabbers/vga2usb/
* http://www.epiphan.com/products/frame-grabbers/vga2usb/


=== Total budget so far ===
 
{|
! Item !! Price
|-
| [http://www.epiphan.com/products/frame-grabbers/vga2usb/ vga2usb] || $319.90 (with shipping - you can [https://www.fedex.com/Tracking?tracknumbers=013248410312427&action=track&clienttype=fsm&language=english&cntry_code=ca track our package here].)
|-
| [http://www.amazon.com/Canon-ZR80-MiniDV-Camcorder-Optical/dp/B0001ANT9S/ref=sr_1_2?ie=UTF8&s=photo&qid=1264454062&sr=1-2 minidv camcorder] || $186.49
|-
| '''Total to date:''' || $506.39
|}
 
=== Total budget ===


* Original budget -- $3,000
* Original budget -- $3,000
* Travel commitments -- $1335.70
* Travel commitments -- $1320.60
* Lodging -- $659.88
* Lodging/Space -- $1024.68
* Remaining funds -- $1002.42
* Equipment -- $506.39
 
'''Total cost: $2851.67 ($148.33 under budget)'''


== Purpose and goals ==
== Equipment ==


A FUDCon whose planning starts after March 2011 should be able to be executed without planning assistance from CommArch/Fedora Engineering beyond the initial approval of the FUDCon, the writing of checks, and participating as ordinary attendees/volunteers.
If you're bringing toys - by which we mean "A/V equipment" - to play with during this FAD, list it here so we know what we've got to play with.


=== Primary goals ===
{|
! What is it? !! What is it for? !! Who is bringing it?
|-
| Zoom H2 || High-quality USB microphone/mp3-to-SD card audio recorder || [[User:Mchua|Mel Chua]]
|-
| MiniDV camcorder || +cable, can be used for live IEEE-1394 source || [[User:Pfrields|Paul W. Frields]]
|-
| Alesis 1202 VLZ mixer || mixer on hand if needed || [[User:Pfrields|Paul W. Frields]]
|-
| Miscellaneous microphones || hi-quality handheld dynamic, one large condenser || [[User:Pfrields|Paul W. Frields]]
|-
| Various cables || The band box o' doom, mostly 1/4" and XLR || [[User:Pfrields|Paul W. Frields]]
|-
| Alesis 4-Channel Mixer (2) || Mixing audio  || [[User:Herlo|Clint Savage]]
|-
| logitech 720p usb webcam || capturing video  || [[User:Ausil|Dennis Gilmore]]
|-
| v4l-compatible webcam w/ mic || Capturing video || [[User:Ctyler|Chris Tyler]]
|-
| What is it? || What is it for? || Who is bringing it?
|}


# Timeline for planning future FUDCons
== Avatar ==
## An annual cycle/calendar of which regional FUDCon happens during which quarter (i.e. NA FUDCon in Q3, LATAM FUDCon in Q4, or whatever the arrangement ends up being)
## A list of FUDCons targeted for planning from now through March 2011
# A revised and expanded edition of https://fedoraproject.org/wiki/FUDCon/Organization prepared for the organizers of the next FUDCon in the planning queue
## Consider the "we broke Barcamp" bug from FUDCon Toronto - how do we scale up with registration and session scheduling? (non-software - the Secondary item is software.)
## Define who is needed from RH and the community (who as in what groups, infrastructure, QA, FE, etc. ) to make a successful event
## Create a location bid process, including a minimum standard for the type of facility needed to host the event. (ie. number and size of rooms, A/V, location in regards to food & transportation)
## A clearly defined sponsorship timeline, publication process, and selection process for assigning travel funding to community members who need it, and an accounting system to support it.
## HOWTO on User Track sessions for FUDCon
### Possible expansion to be more family-friendly?
# A recording / remote participation solution (FUDCon Live) '''This is the major project/piece of development work that will be undertaken during the FAD; development may not be complete, but a usable solution should be out, with a roadmap for future improvement.'''


=== Secondary goals ===  
<s>We have the ability to get a discount on pre-ordered concessions.  You can get a small box of popcorn and your choice of Coke, Diet Coke, Sprite, Orange Fanta, Dr Pepper, Powerade or bottled water.  It comes as a combo pack, so you have to get both the popcorn and the drink, but you can give it away to someone else if you don't want something.  Note what you would like below:</s>
 
Our requests have been emailed in.  Max is waiting for confirmation -- worst case, we'll buy stuff when we get there.
 
* Max -- popcorn & coke
* Jon -- popcorn & coke
* Chris -- popcorn & Dr Pepper (2nd choice Coke)
* Clint -- popcorn, raisinettes & Dr Pepper (Coke is a good alternative)
* Mel -- popcorn and orange fanta
* Dennis -- popcorn(no butter) sprite with cherry and vanilla syrup
* Paul -- popcorn and water
* Steven -- popcorn & coke
* David -- popcorn & coke
* Colby -- popcorn, raisinettes, and coke
 
== Planning meetings ==
 
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-25/fudcon-planning.2010-01-25-17.06.html 2010-01-25]
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-20/fudcon-planning.2010-01-20-20.40.html 2010-01-20 belated weekly planning meeting, logistics budget wrapup]
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-15/fudcon-planning.2010-01-15-02.36.html 2010-01-15 freeseer tech discussion]
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-11/fudcon-planning.2010-01-11-17.02.html 2010-01-11 planning meeting 2]
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-09/fudcon-planning.2010-01-09-06.59.html 2010-01-09 planning meeting 1]


# A scaleable event registration and session scheduling solution (software - the Primary item is non-software.)
# A repository of FUDCon templates and materials (letters, posters, etc) with instructions for customization
# A FUDCon effectiveness feedback survey that can be used to chart our improvement over time


[[Category:Events]] [[Category:FAD]] [[Category:FUDCon]] [[Category:Events 2010]]
[[Category:Events]] [[Category:FAD]] [[Category:FUDCon]] [[Category:Events 2010]]

Latest revision as of 07:57, 19 August 2010

This is the main page for the 2010 Events FAD, which is a FAD focused on tools, infrastructure, and materials for Fedora events, with a focus on FUDCons (though much of the work will likely be reusable for FADs themselves).

Remaining TODOs

  • Max -- pay for everything hotel-related.
  • Mel -- finalize transportation plan back to the airport.
  • Max & Mel -- file expense reports.

Pages we've worked on

These pages need to have redirects made, be categorized, linked to each other, etc.

To finish this section

Ensure all docs and wiki pages linked or referred to from (in order of priority):

  1. Max's email (done)
  2. the Events_FAD_2010 page
  3. the entire weekend's IRC logs
    1. Friday, #fad
    2. Friday, #fedora-fad
    3. Friday, #freeseer
    4. Saturday, #fad
    5. Saturday, #fedora-fad
    6. Saturday, #freeseer
    7. Sunday, #fad
    8. Sunday, #fedora-fad
    9. Sunday, #freeseer
    10. Sunday, #fudcon-planning

...are (in order of priority)

  1. status updated (with an admon note)
  2. properly categorized
  3. link to each other where appropriate
  4. have consistent, up-to-date content (If you can't update a page in less than 15 minutes, give it to Jon (jds2001) to put on the "FAD Followup" list.)

The end deliverable here is a link to a wiki category page that lists all the pages that we worked on this weekend.


Schedule

Thursday January 28

People arrived, a bit of pre-hacking. Some blog posts, below.

Friday January 29

IRC logs available:

Blog posts:

9:30 AM -- Start. Short opening talk by Max to make sure everyone knows what's going on from a logistics point of view, remind folks of the goals for the weekend, and documentation/publicity of our FAD. Make sure that remote participation is up and running properly. Update: Make plans in case of inclement weather.

Schedule:

10:00 AM - 1:00 PM -- Break up into our two tracks.

10:30 AM - AVBox track begins hacking in #freeseer. FUDCon 2.0 track is iterating on FUDCon#FUDCon_calendar.

1:00 PM - 2:00 PM -- Lunch will be delivered. Sub sandwiches from Jimmy John's, chips & drinks from Daddy Shadowman.

2:00 PM - 6:00 PM -- Break up into our two tracks.

5:00 PM -- Hard stop for Max, who has to run an errand that can't be avoided before the social event.

6:00 PM -- Hard stop for everyone else, so that we can clean up and make it to our social event on time.

7:10 PM -- Avatar on the IMAX 3-D screen. See below.

Saturday January 30

Original plans were scrapped in favor of continuing to work from the hotel, due to the (one-inch) "blizzard" that hit Raleigh Friday night.

Sunday January 31

Snow-in-Raleigh adventures continued, and we worked from the hotel for the last day as well.

Post-Sunday reflections

Tracks

Track #1 -- FUDCon 2.0

Primary owner: Max

Overall goals

Refresh the entire "Premier Fedora Events" idea in our community. Break it down to first principles and build it back up, eventually refining processes, decision-making, and ownership. Then put this into practice as we plan 2010.

Friday

Basically a design thinking day. We'll start with an introduction to the design thinking process.

Here is an initial set of ideas, to seed the session:

  • At its core, what is FUDCon? What purpose is it meant to have?
  • If we were starting with the FUDCon idea right now, what are the goals that FUDCons should have? Both from the regional and annual perspective, as well as from the user or developer perspective. How do we decide what constitutes a good FUDCon? Does the formula need to be the same everywhere?
  • How do FADs interact with the FUDCon idea? Are we properly incentivizing people to hold them? What needs to be changed?
  • Are there any big holes or things not being achieved within Fedora that the FUDCon/FAD model could be modified to solve?
  • Generalized annual FUDCon cycle/calendar with FUDCons and Important Regional FADs and suggested times for them.
  • Expand that generalized list out into the next 18 months, or so.
  • What do we do with the following pages?
  • BarCamp -- have we outgrown it, or did we Do It Wrong in Toronto? How do we scale event registration and sessions scheduling? Is a set of wiki pages for a FUDCon still ok?
  • What is the ownership model for FUDCons and/or FADs? Who is needed? When does it need a stamp of approval to call itself a FUDCon or a FAD? What is the RACI?
  • How do we encourage people to do the "due diligence" and set up an informal sort of "bid process" around possible locations for FUDCons and FADs? What sorts of facilities are the minimum required?
  • How do we break down budget for a FUDCon or a FAD, and what does the sponsorship process look like?
  • User versus Developer.
  • Possible expansion to be more family friendly?
  • A repository of FUDCon templates and materials (letters, posters, etc) with instructions for customization.
  • FUDCon survey that can be used to chart our improvement over time.

Saturday

See Max's summary email of progress from Saturday evening.

Action Items for Saturday
  1. Generic calendar FUDcons and Ambasador FAD with regional breakdowns
  2. 2010 instances communication
  3. Bid process incorporating old locations wiki page
  4. Define things that received good feedback and should be constant
  5. List suggestions for improvement that we need to act on
  6. HOWTO + Organization Page
  7. Clear attendee sponsorship process
Documents to draft

Here are the list of documents that we are teaming up to write and make available.

  • Bid process and bid content -- Max, David
    • This document will fix:
      • Less reliance on CommArch -- community ownership
      • Regional planned events by regional folks
      • Better local involvement
      • Establish approval process for FUDCon occurrence
    • This document might fix:
      • Budget process
      • Food details
      • Location (south in winter, north in summer)
      • Whether to attach to other major events
  • HOWTO run a FUDCon -- Chris, Mel
    • This document will fix:
      • Ownership model -- RACI
      • Budget process
      • Repository of materials needed
      • Have clear deliverables for a FUDCon event
    • This document might fix:
      • More social interaction
      • Encouraging new contributors to join
      • Providing a forum where people can ask "By the way" questions
      • Better on-ramping -- promoting connection to the community
      • Does not kill anyone
  • Clear attendee sponsorship process doc -- Paul, Steven -- DONE! Refer to Sponsoring event attendees
    • This document will fix:
      • Better budget/sponsorship process and tools

Sunday

Basically a testing and putting-into-practice day.

Testers of Saturday's work (in #fudcon-planning)

  • 9:00 AM - 11:00 aM: FUDCon LATAM (Rodrigo Padula)

Track #2 -- FUDCon Live

Primary owner: Clint / Yaakov

Overall goals

  1. -- Define use cases for freeseer with regard to Fedora (and other community) events.
  2. -- Build freeseer software to meet top 2 or 3 use cases, beyond it's current capability.
  3. -- Get freeseer packaged into Fedora, including any gstreamer stuff that needs to happen.
  4. -- Get equipment purchased, tested, documented, etc.
  5. -- Create and test the participation and usage documentation, so that folks can run a FUDCon/FAD Live!
  6. -- Review the survey results and decide what we can do to make FUDCon/FAD Live a better experience
    1. Decide what our goals are
    2. Decide on the results we should see on the following survey
    3. Identify changes and the expected results
    4. After the next event or two, see if we've made improvement
  7. -- Document whatever is needed for worldwide replication, and any roadmap needed for future improvement.

Friday

The who's-working-on-freeseer-when schedule is available on the freeseer wiki.

  • As much of 1 and 2 as possible.
  • Determine current state of 4 and where we need to get.
  • Get any needed parts for 1 and 2.
  • Discuss 5.

Saturday

  • Accomplish the remainder of 2.
  • Testing and progress of 1 with new versions of 2.
  • Discuss 5 if not already done.
  • Begin 3.

Sunday

  • Finish 3.
  • Discuss 6 if not already done.
  • 7.

Wrap up the FUDCon Live page.

Attendees

# FAS Name &
Full Name
in-person or remote? remote attendance
1 Mel Chua in-person
2 Steven Parrish in-person
3 Jon Stanley in-person
4 David Nalley in-person
5 Yaakov M. Nemoy remote I don't think i can make it for most of friday except the first hour
6 Max Spevack in-person
7 Clint Savage in-person
8 Chris Tyler in-person
9 Justin O'Brien remote
10 Paul W. Frields in-person
11 Dennis Gilmore in-person
12 Andrew Ross remote
13 Thanh Ha remote
14 John Rose remote
15 Rodrigo Padula remote

A note on remote participation

Live log

This FAD is specifically designed to be a combined in-person/online event, echoing the FUDCon/FUDCon Live arrangement in real FUDCons so we can more effectively test the deliverables we are producing. Remote participation is crucial to the success of this FAD.

There is no prep needed for remote participation: just show up on IRC. Anything else we need to do at that point, we'll figure out at that point.

Remote participation will be coordinated over IRC. The main channel for the FAD will be #fad, with freeseer hacking happening in #freeseer.

  • 9:30am on Friday: kickoff in-person and on #fad
  • 10:30am on Friday: freeseer hacking kickoff in #freeseer

Further updates on remote participation will happen both in-channel and on the fudcon-planning mailing list. Generally speaking, we will be in #fad during the day when we are working on FAD things; please pop in and say hi and we'll help you get started.

Logistics & budget

Travel

Contributor Carrier Depart Arrive Depart Arrive Cost Status
Mel Chua The Melmobile Will be in town from 1/24 for other business 1/24 Sunday Sunday $0 no action needed, just noting here
Clint Savage Delta 01/28/2010 1:50pm MST 01/28/2010 9:45pm EST 01/31/2010 6:00pm EST 01/31/2010 11:41pm MST $290.80 Purchased
User:Jstanley AA AA 4423, JFK-RDU 01/28/2010 7:30EST 01/28/2010 09:30EST AA 4537, RDU-JFK 01/31/2010 06:05PM 01/31/2010 7:55PM EST $164.40 Purchased
Dennis Gilmore AA AA 4157, PIA-ORD 01/28/2010 5:55 PM CST AA 3881, ORD-RDU 01/28/2010 10:40 pm EST AA 2091, RDU-ORD 01/31/2010 06:05PM EST AA 4368 ORD-PIA 01/31/2010 10:25PM CST $290.80 Purchased
Paul Frields The FPL-mobile Thursday Thursday Sunday Sunday $47.75 for gas Reimbursed
Chris Tyler Delta Delta 6498 YYZ-JFK 11:50am Delta 5482 JFK-RDU 4:35pm Delta 6580 RDU-JFK 5:00pm Delta 6763 JFK-YYZ 10:00pm $489.70 PURCHASED
David Nalley Nalley-mobile Thursday Thursday Sunday Sunday $37.15 for gas Reimbursed
Total to date: $1320.60
Name Carrier Travel to FAD, departure Travel to FAD, arrival Travel from FAD, departure Travel from FAD, arrival Ticket cost

Lodging

We stayed at:

Best Western Cary Inn And Extended Stay
1722 Walnut Street
Cary, NC 27511 US

Four nonsmoking double rooms with microfridges have been booked, see roommate pairings below.

Roommate 1 Roommate 2 Check-in Check-out Nights Cost Status
Clint Savage Paul W. Frields Thu 2010-01-28 Sun 2010-01-31 3 see below paid
Jon Stanley Dennis Gilmore Thursday Sunday 3 see below paid
Chris Tyler David Nalley Thursday Sunday 3 see below paid
Mel Chua Thursday Sunday 3 $832.28 total for all 4 rooms paid
Conference room Saturday Sunday 2 $192.40 paid
Roommate 1 Roommate 2 Check-in Check-out Nights Cost Status
Total to date: 12 $1024.68

Equipment budget

What we didn't spend on travel, we'll spend on getting equipment to start making this an option for Events Kits.

Equipment we looked at:


Item Price
vga2usb $319.90 (with shipping - you can track our package here.)
minidv camcorder $186.49
Total to date: $506.39

Total budget

  • Original budget -- $3,000
  • Travel commitments -- $1320.60
  • Lodging/Space -- $1024.68
  • Equipment -- $506.39

Total cost: $2851.67 ($148.33 under budget)

Equipment

If you're bringing toys - by which we mean "A/V equipment" - to play with during this FAD, list it here so we know what we've got to play with.

What is it? What is it for? Who is bringing it?
Zoom H2 High-quality USB microphone/mp3-to-SD card audio recorder Mel Chua
MiniDV camcorder +cable, can be used for live IEEE-1394 source Paul W. Frields
Alesis 1202 VLZ mixer mixer on hand if needed Paul W. Frields
Miscellaneous microphones hi-quality handheld dynamic, one large condenser Paul W. Frields
Various cables The band box o' doom, mostly 1/4" and XLR Paul W. Frields
Alesis 4-Channel Mixer (2) Mixing audio Clint Savage
logitech 720p usb webcam capturing video Dennis Gilmore
v4l-compatible webcam w/ mic Capturing video Chris Tyler
What is it? What is it for? Who is bringing it?

Avatar

We have the ability to get a discount on pre-ordered concessions. You can get a small box of popcorn and your choice of Coke, Diet Coke, Sprite, Orange Fanta, Dr Pepper, Powerade or bottled water. It comes as a combo pack, so you have to get both the popcorn and the drink, but you can give it away to someone else if you don't want something. Note what you would like below:

Our requests have been emailed in. Max is waiting for confirmation -- worst case, we'll buy stuff when we get there.

  • Max -- popcorn & coke
  • Jon -- popcorn & coke
  • Chris -- popcorn & Dr Pepper (2nd choice Coke)
  • Clint -- popcorn, raisinettes & Dr Pepper (Coke is a good alternative)
  • Mel -- popcorn and orange fanta
  • Dennis -- popcorn(no butter) sprite with cherry and vanilla syrup
  • Paul -- popcorn and water
  • Steven -- popcorn & coke
  • David -- popcorn & coke
  • Colby -- popcorn, raisinettes, and coke

Planning meetings