From Fedora Project Wiki

m (Minor update)
m (Updated planning todo's)
Line 19: Line 19:
 
See the [[How to organize a FAD]] list; you can keep your to-do list here.
 
See the [[How to organize a FAD]] list; you can keep your to-do list here.
  
* <strike>Completed work item</strike>
+
* 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] )
* Work out budget
+
* Select a venue based on participants
* Decide on Dates and Location
+
* Figure out how much this will cost
* Arrange Facilities
 
* List Resources
 
* Be Somewhat Structured
 
* Arrange Lodging
 
* Arrange Refreshments
 
* Arrange a Social Event
 
* Another action item
 
* Another action item
 
* Another action item
 
  
 
== Plan ==
 
== Plan ==

Revision as of 21:36, 5 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 Echo-package-16px.pnggwt. The gwt package is a build dependency for Autotest.

Purpose

The primary purpose for the event is gather Fedora packaging and java experts to ...

  1. Identify all remaining unpackaged build dependencies
  2. Package unpackaged build dependencies
  3. Convert existing JPackages to packages acceptable for Fedora

In addition, we will attempt to complete the following secondary goals as time allows:

  1. Submit as many new packages as possible for review
  2. Review and approve as many submitted packages as possible
  3. Update existing Package-x-generic-16.pnggwt and {{package|autotest} packages as needed

Detailed Work Items & Final Attendees

Planning Prerequisites

See the How to organize a FAD list; you can keep your to-do list here.

  • Solicit FAD participants (for java experts, send mail to java-devel, for packaging experts, send mail to packaging )
  • Select a venue based on participants
  • Figure out how much this will cost

Plan

  1. Location:
  2. Date:
  3. Schedule
    • Participants arrive at THIS_TIME_AND_DATE
    • Schedule item
    • Schedule item
    • Schedule item
    • Participants leave at THIS_TIME_AND_DATE
  4. Important skills (one or more)
    • skill
    • skill
    • skill
  5. 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?
  6. 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 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
  1. Travel: $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
  2. Housing: $B for hotel, etc. needed to have attendees sleep during the FAD
    • link to hotel room booking website, if applicable
  3. Space: $C for renting space to hack in, if applicable
    • address and travel details for the space
  4. Supplies: $D for anything else you may need
    • item
    • item
    • item

Total budget: $A+B+C+D