From Fedora Project Wiki

(massive cleanup)
Line 1: Line 1:
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 ==
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.
=== Meetings ===
In #fudcon-planning.
* 1700-1800 UTC (noon-1pm EST) on Mondays
* 2100-2200 UTC (4-5pm EST) on Thursdays (our old FUDCon organizers
meeting time)
There are 6 planning meetings: March 11, 14, 18, 21, 25 and 28.
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-11/fudcon-planning.2010-01-11-17.02.html 2010-01-11]
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-09/fudcon-planning.2010-01-09-06.59.html 2010-01-09]


== Schedule ==
== Schedule ==
Line 35: Line 57:
Afternoon -- Unscheduled, so that we have flexibility for final wrap-up activities.
Afternoon -- Unscheduled, so that we have flexibility for final wrap-up activities.


== Status ==
== Attendees ==
 
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.
 
=== Meetings ===
 
In #fudcon-planning.
 
* 1700-1800 UTC (noon-1pm EST) on Mondays
* 2100-2200 UTC (4-5pm EST) on Thursdays (our old FUDCon organizers
meeting time)
 
There are 6 planning meetings: March 11, 14, 18, 21, 25 and 28.
 
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-11/fudcon-planning.2010-01-11-17.02.html 2010-01-11]
* [http://meetbot.fedoraproject.org/fudcon-planning/2010-01-09/fudcon-planning.2010-01-09-06.59.html 2010-01-09]
 
== Purpose ==
 
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.
 
== Goals ==
 
=== Primary ===
 
# Timeline for planning future FUDCons
## 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
# 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 ===
 
# 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
 
== Interested Attendees ==
 
=== A note on remote participation ===
 
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.
 
=== Initial interest table ===


{|
{|
! # !! FAS Name &<br/>Full Name !! Hotel !! Option 1 !! Option 2 !! Comment !! Location
! # !! FAS Name &<br/>Full Name !! in-person or remote?
|-
|-
| 1 || [[User:mchua|Mel Chua]] || or couchsurf || in-person || in-person || possibly driving, if there's carpool interest || Boston MA
| 1 || [[User:mchua|Mel Chua]] || in-person
|-
|-
| 2 || [[User:StevenParrish|Steven Parrish]] || N/A || in-person || in-person || || Raleigh
| 2 || [[User:StevenParrish|Steven Parrish]] || in-person
|-
|-
| 3 || [[User:Jstanley|Jon Stanley]] || yes, or something || in-person || in-person || (note that this conflicts with my birthday and I'll be expecting a big party! :) )|| NYC
| 3 || [[User:Jstanley|Jon Stanley]] || in-person
|-
|-
| 4 || [[User:ke4qqq|David Nalley]] || preferably || in-person || in-person || || Raleigh
| 4 || [[User:ke4qqq|David Nalley]] || in-person
|-
|-
| 5 || [[User:ynemoy|Yaakov M. Nemoy]] || N/A || conflicts with Fosdem || remote || air fare runs in the 900 USD range, in-person is not a likely possibility, hoping for good online interaction, fedora talk might be an option ||
| 5 || [[User:ynemoy|Yaakov M. Nemoy]] || remote
|-
|-
| 6 || [[MaxSpevack]] || no || conflicts with FOSDEM || in-person || || Raleigh
| 6 || [[MaxSpevack|Max Spevack]] || in-person
|-
|-
| 7 || [[User:Herlo|Clint Savage]] || likely, yes || in-person || in-person || my flight is currently $250 round trip, which seems feasible.  I'm highly interested in participating || Salt Lake City, UT
| 7 || [[User:Herlo|Clint Savage]] || in-person
|-
|-
| 8 || [[User:CTyler|Chris Tyler]] || yes (if in person) || in-person (or remote) || in-person (or remote) || || Toronto
| 8 || [[User:Ctyler|Chris Tyler]] || in-person
|-
|-
| 9 || [[User:threethrity|Justin O'Brien]] || I would need a hotel || I would love to be in-person || remote would be ok too || doesn't expect anything since I'm new || ??
| 9 || [[User:Threethirty|Justin O'Brien]] || ???
|-
|-
|10 || [[User:Pfrields|Paul W. Frields]] || yes || in-person || in-person || Driving to event || Fredericksburg, VA
|10 || [[User:Pfrields|Paul W. Frields]] || in-person
|-
|-
|11 || [[User:Ausil|Dennis Gilmore]] || yes || in-person || in-person ||  || Washington, IL
|11 || [[User:Ausil|Dennis Gilmore]] || in-person
|-
|-
| n+1 || [[User:username|realname]] || need a hotel? || in-person - remote || in person - remote  || notes || location
|12 || Andrew Ross || ???
|-
|13 || Thanh Ha || ???
|-
|-
|}
|}


== By location ==
=== A note on remote participation ===


=== In person ===
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.
 
==== Raleigh local ====
 
* David Nalley - packaging/deployment ninja
* Max Spevack - old hand at FUDCon planning, budget ninja
* Steven Parrish - organized the user track for the last FUDCon in Toronto - ninja in training
 
==== Out of town ====
 
* Mel Chua (BOS) - organizing FAD, link to remotees
* Jon Stanley (NYC) - makes-things-into-generalizable-procedures ninja
* Chris Tyler (YYZ) - co-organized the last FUDCon in Toronto
* Clint Savage (SLC) - FUDCon live media streaming ninja
* Paul Frields (DC) - co-organized the last FUDCon in Toronto
* Dennis Gilmore (PIA) - involved in FUDCons in NA, and LATAM, strong understanding of APAC, infrastructure person
* Someone from video streaming project (maybe) - to lead the setup, training, documentation, packaging, etc. of the video setup in person
 
=== Remote ===
 
* Yaakov Nemoy - FUDCon Live organizer
* Someone from FUDCon India team
* Someone from FUDCon LATAM team
 
=== Either in person or remote ===
 
* Justin O'Brien
* Someone from video streaming project (maybe)
* Someone from RIT (there is interest in hosting a future FUDCon at this location)


== Planning Prerequisites ==
== TODO ==


See the [[How to organize a FAD]] list; you can keep your to-do list here.
* Mel -- get the attendee list finalized by January 17th, and any remaining travel purchased.
* 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.
* 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.
* Mel -- Figure out what the actual plan for remote participation is.
* ??? -- Sort out transporation.
* Max & Mel -- file expense reports.


* <strike>Completed work item</strike>
== Logistics & budget ==
* Work out budget
* Decide on Dates and Location
* Arrange Facilities
* List Resources
* Be Somewhat Structured
* Arrange Lodging
* Arrange Refreshments
* Arrange a Social Event
* Negotiate airline discount
* Verify network infrastructure exists and is up to the task
* Another action item


 
=== Transportation ===
 
== Logistics ==
 
=== Transport ===


As we get closer to the date, details will go here (airport pickups, rental cars, etc).
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).
* [[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).
=== Food ===
As we get closer to the date, details will go here.
== Budget ==


=== Travel ===
=== Travel ===
Line 206: Line 134:
|}
|}


=== Housing ===
=== Lodging ===


Hotel rooms in Raleigh can be had for $60/night (or less) for a double. We'll book rooms as a group, so don't make your reservations yet.
Hotel rooms in Raleigh can be had for $60/night (or less) for a double. We'll book rooms as a group, so don't make your reservations yet.
Line 224: Line 152:
|}
|}


=== Probably need to purchase ===
=== Total budget so far ===
 
* Original budget -- $3,000
* Travel commitments -- $796
* Lodging commitments -- $540
* Remaining funds -- $1,664


...but not budgeted yet
== Purpose and goals ==


* Jon Stanley's housing
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.
* Chris Tyler's flight and housing
* Filming people: flight and housing


=== Other items ===
=== Primary goals ===


* Would like to be able to buy everyone dinner at least one night of the FAD, depending on where we eat, maybe $25 x number-of-participants? (Lunch at Ole Time would be substantially less than this, for a ridiculous amount of great food.)
# Timeline for planning future FUDCons
* Space - $0, using RH office
## 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)
* Supplies - do we need anything?
## A list of FUDCons targeted for planning from now through March 2011
* Others?
# 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
# 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.'''


=== Total budget so far ===
=== Secondary goals ===  


<pre>
# A scaleable event registration and session scheduling solution (software - the Primary item is non-software.)
$3000.00 original budget
# A repository of FUDCon templates and materials (letters, posters, etc) with instructions for customization
-$796.00 travel
# A FUDCon effectiveness feedback survey that can be used to chart our improvement over time
-$420.00 housing
----------------
$1784.00 remaining to date
</pre>


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

Revision as of 22:27, 13 January 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).

Status

Discussion and coordination are happening on the fudcon-planning list, but this wiki page is the canonical reference to the status of this event's planning.

Meetings

In #fudcon-planning.

  • 1700-1800 UTC (noon-1pm EST) on Mondays
  • 2100-2200 UTC (4-5pm EST) on Thursdays (our old FUDCon organizers

meeting time)

There are 6 planning meetings: March 11, 14, 18, 21, 25 and 28.

The agenda for each, until further notice, will be:

  1. proposal/budget approval
  2. FAD agenda-setting and logistics arrangement
  3. prepwork to gear up for things specified in #2 and funded by #1.

Schedule

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.

Friday January 29 - Sunday January 31

We will be meeting in the Augusta National conference room on the 5th floor of 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.

Friday January 29

9:30 AM -- Start.

1:00 PM -- Lunch will be delivered.

Proposed social event -- Avatar on the IMAX 3-D screen.

Saturday January 30

9:30 AM -- Start.

1:00 PM -- Lunch will be delivered.

Proposed social event -- TBD.

Sunday January 31

9:30 AM -- Start.

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

Afternoon -- Unscheduled, so that we have flexibility for final wrap-up activities.

Attendees

# FAS Name &
Full Name
in-person or remote?
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
6 Max Spevack in-person
7 Clint Savage in-person
8 Chris Tyler in-person
9 Justin O'Brien ???
10 Paul W. Frields in-person
11 Dennis Gilmore in-person
12 Andrew Ross ???
13 Thanh Ha ???

A note on remote participation

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

  • Mel -- get the attendee list finalized by January 17th, and any remaining travel purchased.
  • 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.
  • 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.
  • Mel -- Figure out what the actual plan for remote participation is.
  • ??? -- Sort out transporation.
  • Max & Mel -- file expense reports.

Logistics & budget

Transportation

As we get closer to the date, details will go here (airport pickups, rental cars, etc).

  • 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

Contributor Carrier Depart Arrive Depart Arrive Cost Status
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 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 Purchased
Paul Frields The FPL-mobile Thursday Thursday Sunday Sunday $50 for gas APPROVED
Andrew Ross ? Friday early morning Friday late morning Sunday evening Sunday evening ~$900 pending approval
Thanh Ha ? Friday early morning Friday late morning Sunday evening Sunday evening ~$900 pending approval
Name Carrier Travel to FAD, departure Travel to FAD, arrival Travel from FAD, departure Travel from FAD, arrival Ticket cost
Total to date: $796.00

Lodging

Hotel rooms in Raleigh can be had for $60/night (or less) for a double. We'll book rooms as a group, so don't make your reservations yet.

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 $180 pending
Mel Chua Dennis Gilmore Thursday (Mel arriving early, Dennis arriving late) Dennis - Sunday, Mel - Sunday or Monday 4 $240 pending
Andrew Ross Thanh Ha Friday Sunday 2 $120 pending
Roommate 1 Roommate 2 Check-in Check-out Nights Cost Status
Total to date: $540

Total budget so far

  • Original budget -- $3,000
  • Travel commitments -- $796
  • Lodging commitments -- $540
  • Remaining funds -- $1,664

Purpose and goals

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.

Primary goals

  1. Timeline for planning future FUDCons
    1. 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)
    2. A list of FUDCons targeted for planning from now through March 2011
  2. A revised and expanded edition of https://fedoraproject.org/wiki/FUDCon/Organization prepared for the organizers of the next FUDCon in the planning queue
    1. 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.)
    2. Define who is needed from RH and the community (who as in what groups, infrastructure, QA, FE, etc. ) to make a successful event
    3. 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)
    4. 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.
    5. HOWTO on User Track sessions for FUDCon
  3. 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

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