m (→Plan) |
|||
Line 2: | Line 2: | ||
== Purpose == | == Purpose == | ||
* https://fedorahosted.org/design-team/ clean up, close all tickets that are not needed, do which are needed | |||
organize a way how we keep it clean in the future | |||
* organize a way how we keep track of https://fedorahosted.org/design-team/ | |||
beginners tasks? | |||
how shall we do recurring badges? | |||
can we list beginner tasks on easyfix? | |||
* how to organize release design in future | |||
jreznik wants to see tickets for the release tasks - who and how do this? | |||
what do without codenames define a system for ourself or bringing a new codename system again | |||
* reorgainzation of design teams fp.o account | |||
* how to come to regularly meetings again, to keep track of all things | |||
* status of art board, glitter gallery, nuancier | |||
* adapt the wiki pages for new decided things | |||
* restarting of bounties | |||
== Potential Attendees == | == Potential Attendees == |
Revision as of 14:05, 19 August 2014
This is the main page for the 2014 Design Team FAD, which is a FAD focused on working on a roadmap for the Fedora Design Team over the next year or two.
Purpose
- https://fedorahosted.org/design-team/ clean up, close all tickets that are not needed, do which are needed
organize a way how we keep it clean in the future
- organize a way how we keep track of https://fedorahosted.org/design-team/
beginners tasks? how shall we do recurring badges? can we list beginner tasks on easyfix?
- how to organize release design in future
jreznik wants to see tickets for the release tasks - who and how do this? what do without codenames define a system for ourself or bringing a new codename system again
- reorgainzation of design teams fp.o account
- how to come to regularly meetings again, to keep track of all things
- status of art board, glitter gallery, nuancier
- adapt the wiki pages for new decided things
- restarting of bounties
Potential Attendees
Let's use this table to track who is interested in attending, whether or not they need travel, and what times they are available or not. Please note if you would like to attend/participate remotely as well. (just put 'remote' in the travel or local line).
Contributor | Travel? or Local? | Possible times? |
---|---|---|
Ralph | would have to fly (USA) | Anytime May or June works. |
Kevin | local | Anytime after first week in may works. |
Mathieu | would have to fly (France) | Not available in May, early June could work. |
Tim | local-ish, ~70 miles | Anytime in May or June Works |
Mike | local-ish, ~70 miles | Anytime in May, After the 15th June |
Luke | local | Anytime in May. Anytime in June except for 6-9th and the 21st. |
Dennis | Fly (USA) | Anytime in May after 12th, June is okay. |
Ricky | Fly (USA) | Any time in June works for me. |
Ken | local | June |
You! | fly, drive, local? | Anytime except May 29th-June 2nd. |
Detailed Work Items & Final Attendees
- Will need folks from releng, qa, infrastructure and possibly packagers there.
Planning Prerequisites
See the How to organize a FAD list; you can keep your to-do list here.
- Completed work item
- Work out budget
- Decide on Dates and Location
- Arrange Facilities
- List Resources
- Be Somewhat Structured
- Arrange Lodging
- Arrange Refreshments
- Arrange a Social Event
Plan
- Location: Red Hat's Westford Office at 314 Littleton Road, Westford Massachusetts USA
- Date: January 2015 sometime
- 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)
- pTBD
- Personnel (people who might fit the bill)
- gnokii Confirmed? (Y/N)
- mizmo (local, taskotron author) Confirmed? (Y/N)
- ryanlerch (local, taskotron author) Confirmed? (Y/N)
- Name (location, role) Confirmed? (Y/N)
- others?
- Other considerations
- ...
- Potential social events
- ...
- Getting around
- ...
Logistics
Snacks/Beverages: Details go here.
Lunch: Details go here.
Dinner: Details go here.
Budget
If you want funding from Red Hat, ask the Community Architecture (old page) -- (new page) team. If you can find other ways to fund your FAD, that's great too!
Contributor | Dept | Arrv | Dept | Arrv | Cost |
---|---|---|---|---|---|
Mathieu | May 31st, 11:00AM, CDG | May 31st, 5:57PM, DEN | June 5th, 10:05AM, DEN | June 6th, 6:55AM, CDG | $963.39 |
Ralph | June 1st, 9:45AM, ROC | June 1st, 1:54PM, DEN | June 5th, 3:45PM, DEN | June 5th, 11:18PM, ROC | $309.00 |
Ricky | June 1st, 6:00AM, CAK | June 1st, 9:35AM, DEN | June 5th, 3:07PM, DEN | June 5th, 10:02PM, CAK | $435.00 |
Dennis | June 1st, 6:45PM, PIA | June 1st, 10:55PM, DEN | June 5th, 1:15PM, DEN | June 5th, 9:55PM, PIA | $475.00 |
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
- Ralph, approximately $400
- Dennis, approximately $200
- Mathieu, approximately $1200
- Ricky, approximately $350
- Total: $2150
- Housing: $B for hotel, etc. needed to have attendees sleep during the FAD
- Hotel booking site: http://www.laquintadenvercentral.com/
- Hotel is $110 a night and is a 20 minutes walk from where we will be hacking. If everyone comes, 6 people will need lodging. We could get 2 rooms with 2 people in each and the 5th and 6th could crash on Luke's couch. If fewer come, we could do with just 1 room.
- Total cost: $110 * 3 nights * 2 rooms = $660
- Space: $C for renting space to hack in, if applicable
- We will be hacking at Luke's apartment building, at no cost to the FAD.
- Supplies: $D for anything else you may need
- Nothing stands out. Just money for food. $25 per day * 8 people * 4 days = $800
Total budget: $3610