From Fedora Project Wiki
| Line 33: | Line 33: | ||
=== Schedule === | === Schedule === | ||
{| | |||
! colspan=2 | Thursday, 2009-10-22 | |||
|- | |||
! Time (EDT) !! Details | |||
|} | |||
== Planning Prerequisites == | == Planning Prerequisites == | ||
Revision as of 08:37, 20 May 2016
Purpose
- Our purpose is to... complete with the following primary goals:
- Develop a strategy/plan for user and contributor growth in APAC
- Budget planning for APAC (per country as well as the whole region) events/activities in FY2018 (March 2017 - February 2018)
- In addition, we will attempt to complete the following secondary goals as time allows:
- Feedback/comments from APAC Ambassadors
Impact
The completion of these goals will create the following positive change within the project:
- outcome
- outcome
- outcome
These outcomes connect with the following Fedora Community Objectives by explain connection here.
Detailed Work Items & Final Attendees
Participants
Travel days
Travel days are Thursday and Sunday. On-site participants are leaving early and no on-site hacking will take place on Sunday.
Travel days are Thursday and Sunday. On-site participants are leaving early and no on-site hacking will take place on Sunday.
| Name | Remote? | Fri | Sat | Sun | Core Tasks |
|---|
Schedule
| Thursday, 2009-10-22 | |
|---|---|
| Time (EDT) | Details |
Planning Prerequisites
- Completed work item
- Registration of participation in person
- Work out budget
Decide on Dates and Location- Arrange Facilities
- List Resources
- Arrange Lodging
- Arrange Refreshments
- Arrange a Social Event
Plan
- Location:
- Date:
- Schedule
- Participants arrive at THIS_TIME_AND_DATE
- Schedule item
- Schedule item
- Schedule item
- Participants leave at THIS_TIME_AND_DATE
- Important skills (one or more)
- skill
- skill
- skill
- Personnel (people who might fit the bill)
- Name (location, role) Confirmed? (Y/N)
- Name (location, role) Confirmed? (Y/N)
- Name (location, role) Confirmed? (Y/N)
- others?
- Other considerations
- Contributor V can offer a living room for evening social gatherings.
- Contributor W has a car and is willing to do airport pick-ups.
- Contributor X needs as much advance notice as possible.
- Contributor Y has a schedule that is better on Fridays than on Tuesdays, and prefers weekend times after 4:28 AM.
- Contributor Z is allergic to peanuts.
Logistics
Snacks/Beverages: Details go here.
Lunch: Details go here.
Dinner: Details go here.
Budget
If you want funding from Red Hat, ask the OSAS team. If you can find other ways to fund your FAD, that's great too!
| Contributor | Dept | Arrv | Dept | Arrv | Cost |
|---|---|---|---|---|---|
| Name | Travel to FAD, departure | Travel to FAD, arrival | Travel from FAD, departure | Travel from FAD, arrival | Ticket cost |
| Name | Travel to FAD, departure | Travel to FAD, arrival | Travel from FAD, departure | Travel from FAD, arrival | Ticket cost |
| Name | Travel to FAD, departure | Travel to FAD, arrival | Travel from FAD, departure | Travel from FAD, arrival | Ticket cost |
- Travel: $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
- Housing: $B for hotel, etc. needed to have attendees sleep during the FAD
- link to hotel room booking website, if applicable
- Space: $C for renting space to hack in, if applicable
- address and travel details for the space
- Supplies: $D for anything else you may need
- item
- item
- item
Total budget: $A+B+C+D