From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 17: | Line 17: | ||
** [http://commarch.usersys.redhat.com/wiki/Outage December outage] (link to internal-to-RH wiki) | ** [http://commarch.usersys.redhat.com/wiki/Outage December outage] (link to internal-to-RH wiki) | ||
** What's everyone's last day for the year? | ** What's everyone's last day for the year? | ||
** [http://commarch.usersys.redhat.com/wiki/Contact | ** [http://commarch.usersys.redhat.com/wiki/Contact Update team contact info] (link to internal-to-RH wiki) | ||
== Deliverables before vacation == | == Deliverables before vacation == | ||
Line 28: | Line 28: | ||
* FOSDEM 2010 sorted out. | * FOSDEM 2010 sorted out. | ||
* FUDCon LATAM & EMEA planning properly started. | * FUDCon LATAM & EMEA planning properly started. | ||
* Go through your RT tickets and triage/update. | |||
=== Greg === | === Greg === | ||
Line 34: | Line 35: | ||
* The followup meeting about opening RH curriculum with whomever Greg said he needed it with. We want a green light that we can make solid plans on. | * The followup meeting about opening RH curriculum with whomever Greg said he needed it with. We want a green light that we can make solid plans on. | ||
* Big Ideas Fest trip report. | * Big Ideas Fest trip report. | ||
* Go through your RT tickets and triage/update. | |||
=== Karsten === | === Karsten === | ||
Line 39: | Line 41: | ||
* Report on the SPICE situation and our plans to improve/fix both this and the general case. | * Report on the SPICE situation and our plans to improve/fix both this and the general case. | ||
* TOSW going-forward plan to start executing in January. | * TOSW going-forward plan to start executing in January. | ||
* Go through your RT tickets and triage/update. | |||
=== Mel === | === Mel === | ||
Line 44: | Line 47: | ||
* Every expense report for FUDCon Toronto filed and approved. | * Every expense report for FUDCon Toronto filed and approved. | ||
* Fedora Scholarship 2010 in good shape. | * Fedora Scholarship 2010 in good shape. | ||
* Go through your RT tickets and triage/update. | |||
[[Category:Community Architecture meetings]] | [[Category:Community Architecture meetings]] |
Revision as of 22:55, 13 December 2009
Dial-in details
https://fedoraproject.org/wiki/Category:Community_Architecture_meetings
Roll call
Max,
Agenda
- Tiemann
- Deliverables before vacation (see below)
- Upcoming sprints (link to internal-to-RH wiki)
- Proposal for December 15th sprint time
- General stuff
- Key 2010/FY11 travel (link to internal-to-RH wiki)
- December outage (link to internal-to-RH wiki)
- What's everyone's last day for the year?
- Update team contact info (link to internal-to-RH wiki)
Deliverables before vacation
Listed by primary owner. Don't be afraid to ask for help.
Max
- FY11 budget.
- Dashboard presentation and 2-hour mrc year-end-meeting.
- FOSDEM 2010 sorted out.
- FUDCon LATAM & EMEA planning properly started.
- Go through your RT tickets and triage/update.
Greg
- Cloud plan including bstevens communication that we can begin to execute immediately after vacation and share with mrc.
- An aggressive roadmap for the completion of a rough draft of the textbook. We need to have a sense of what it's going to take (time and manpower and who) in order to not have this project be vaporware.
- The followup meeting about opening RH curriculum with whomever Greg said he needed it with. We want a green light that we can make solid plans on.
- Big Ideas Fest trip report.
- Go through your RT tickets and triage/update.
Karsten
- Karsten's research work in a pretty finalized state that can be shared w/ key folks.
- Report on the SPICE situation and our plans to improve/fix both this and the general case.
- TOSW going-forward plan to start executing in January.
- Go through your RT tickets and triage/update.
Mel
- POSSE's future organization, planning, branding, etc. The stuff we spoke about on Friday night of FUDCon in the hotel room.
- Every expense report for FUDCon Toronto filed and approved.
- Fedora Scholarship 2010 in good shape.
- Go through your RT tickets and triage/update.