From Fedora Project Wiki
m (Rename column -> Location) |
|||
| Line 30: | Line 30: | ||
<!-- See the [[How to organize a FAD]] list for additional planning guidance. --> | <!-- See the [[How to organize a FAD]] list for additional planning guidance. --> | ||
# Identify potential key participants ([[User:overholt]], [ | # Identify potential key participants ([[User:overholt]], [[User:mef]], [[User:mbooth]], [[User:dbhole]], [[User:akurtakov]]) | ||
# Solicit FAD participants (for java experts, send mail to [https://admin.fedoraproject.org/mailman/listinfo/java-devel java-devel], for packaging experts, send mail to [https://admin.fedoraproject.org/mailman/listinfo/packaging packaging] | # Solicit FAD participants (for java experts, send mail to [https://admin.fedoraproject.org/mailman/listinfo/java-devel java-devel], for packaging experts, send mail to [https://admin.fedoraproject.org/mailman/listinfo/packaging packaging] | ||
# Choose a event date that best fits with key participants | # Choose a event date that best fits with key participants | ||
Revision as of 15:07, 16 March 2010
This is the main page for the AutoQA Packaging Activity Day, which is a FAD focused on identifying and packaging remaining build dependencies for 
gwtgwt package is a build dependency for Autotest.
Purpose
The primary purpose for the event is gather Fedora packaging and java experts to help ...
- Identify all remaining unpackaged build dependencies
- Package unpackaged build dependencies
- Convert existing JPackages to packages acceptable for Fedora
In addition, we will attempt to complete the following secondary goals as time allows:
- Start package submission and review according to Package Review Process
- Update existing
gwt
Detailed Work Items
For a detailed list of gwt package dependencies, see User:Jlaska/gwt.
Attendees
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 | Location | Thu | Fri | Sat | Sun | Core Tasks |
|---|---|---|---|---|---|---|
| jlaska | Raleigh, NC | X | X | Quality Assurance + automation |
Pre-FAD Planning
- Identify potential key participants (User:overholt, User:mef, User:mbooth, User:dbhole, User:akurtakov)
- Solicit FAD participants (for java experts, send mail to java-devel, for packaging experts, send mail to packaging
- Choose a event date that best fits with key participants
- Select a venue based on participants and date
- Figure out how much this will cost
Schedule
| Time (EDT) | Details |
|---|---|
| Thursday, 2010-MM-DD | |
| Friday, 2010-MM-DD | |
| 1000 | Sessions start |
| 1800 | Wrap up/depart for dinner (possible late-night hacking?) |
| Saturday, 2010-MM-DD | |
| 1000 | Sessions start |
| 1800 | Wrap up/depart for dinner |
| Sunday, 2010-MM-DD | |
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 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