From Fedora Project Wiki

m (Updated fad table)
m (Updated content)
Line 1: Line 1:
This is the main page for the '''AutoQA Packaging Activity Day''', which is a [[FAD]] focused on identifying and packaging remaining build dependencies for <code>[[image:Echo-package-16px.png]][http://jlaska.fedorapeople.org/autoqa/gwt/gwt-2.0.0-0.2.1.fc12.src.rpm gwt]</code>.  The <code>gwt</code> package is a build dependency for [[Autotest]].
+
This is the main page for the '''[[AutoQA]] Packaging Activity Day''', which is a [[FAD]] focused on identifying and packaging remaining build dependencies for <code>[[image:Echo-package-16px.png]][http://jlaska.fedorapeople.org/autoqa/gwt/gwt-2.0.0-0.2.1.fc12.src.rpm gwt]</code>.  The <code>gwt</code> package is a build dependency for [[Autotest]].
  
 
== Purpose ==
 
== Purpose ==
The '''primary''' purpose for the event is gather Fedora packaging and java experts to ...
+
The '''primary''' purpose for the event is gather Fedora packaging and java experts to help ...
 
# Identify all remaining unpackaged build dependencies
 
# Identify all remaining unpackaged build dependencies
 
# Package [[User:Jlaska/gwt#Unpackaged_Dependencies|unpackaged build dependencies]]
 
# Package [[User:Jlaska/gwt#Unpackaged_Dependencies|unpackaged build dependencies]]
Line 8: Line 8:
  
 
In addition, we will attempt to complete the following '''secondary''' goals as time allows:
 
In addition, we will attempt to complete the following '''secondary''' goals as time allows:
# Submit as many new packages as possible for [[Package_Review_Process|review]]
+
# Start package submission and review according to [[Package Review Process]]
# Review and approve as many submitted packages as possible
 
 
# Update existing {{package|gwt}} and {{package|autotest}} packages as needed
 
# Update existing {{package|gwt}} and {{package|autotest}} packages as needed
  
 
== Detailed Work Items ==
 
== Detailed Work Items ==
* See [[FAD_Fedora_Talk_2009_game_plan]]
 
  
== Final Attendees ==
+
For a detailed list of ''gwt'' package dependencies, see [[User:Jlaska/gwt]].
 +
 
 +
== Attendees ==
  
 
{{admon/note | Travel days | Travel days are Thursday and Sunday.  On-site participants are leaving early and no on-site hacking will take place on Sunday.}}
 
{{admon/note | Travel days | Travel days are Thursday and Sunday.  On-site participants are leaving early and no on-site hacking will take place on Sunday.}}
Line 26: Line 26:
 
|}
 
|}
  
== Planning Prerequisites ==
+
== Pre-FAD Planning ==
 +
 
 +
<!-- See the [[How to organize a FAD]] list for additional planning guidance. -->
  
See the [[How to organize a FAD]] list; you can keep your to-do list here.
+
# Identify potential key participants
 +
#* [[User:overholt]]
 +
#* [mailto:mefoster@gmail.com Mary Ellen Foster]
 +
#* Mat Booth
 +
#* [[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]
 +
# Select a venue based on participants
 +
# Choose a weekend that best fits with key participants
 +
# Figure out how much this will cost
  
* 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] )
+
== Schedule ==
* Select a venue based on participants
 
* Figure out how much this will cost
 
  
== Plan ==
+
{|
# '''Location:''' TDB
+
! Time (EDT) !! Details
# '''Date:'''  TDB
+
|-
# '''Schedule''' TDB
+
! colspan=2 | Thursday, 2010-MM-DD
#* Participants arrive at THIS_TIME_AND_DATE
+
|-
#* Schedule item
+
| ||
#* Schedule item
+
|-
#* Schedule item
+
! colspan=2 | Friday, 2010-MM-DD
#* Participants leave at THIS_TIME_AND_DATE
+
|-
# Important skills (one or more)
+
| 1000 || Sessions start
#* Fedora package sponsor
+
|-
#* [[Packaging:Guidelines|Packaging Guidelines]]
+
| 1800 || Wrap up/depart for dinner (possible late-night hacking?)
#* [[Java]]
+
|-
# Personnel (people who might fit the bill)
+
! colspan=2 | Saturday, 2010-MM-DD
#* Name (location, role) '''Confirmed? (Y/N)'''
+
|-
#* Name (location, role) '''Confirmed? (Y/N)'''
+
| 1000 || Sessions start
#* Name (location, role) '''Confirmed? (Y/N)'''
+
|-
#* ''others?''
+
| 1800 || Wrap up/depart for dinner
# Other considerations
+
|-
#* Contributor V can offer a living room for evening social gatherings.
+
! colspan=2 | Sunday, 2010-MM-DD
#* 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 ==
 
== Logistics ==

Revision as of 21:35, 11 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 help ...

  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. Start package submission and review according to Package Review Process
  2. Update existing Package-x-generic-16.pnggwt and Package-x-generic-16.pngautotest packages as needed

Detailed Work Items

For a detailed list of gwt package dependencies, see User:Jlaska/gwt.

Attendees

Note.png
Travel days
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
jlaska X X Quality Assurance + automation

Pre-FAD Planning

  1. Identify potential key participants
  2. Solicit FAD participants (for java experts, send mail to java-devel, for packaging experts, send mail to packaging
  3. Select a venue based on participants
  4. Choose a weekend that best fits with key participants
  5. 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
  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