From Fedora Project Wiki

No edit summary
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Dial-in details ==
https://fedoraproject.org/wiki/Category:Community_Architecture_meetings
== Roll call ==
== Roll call ==


Max,
Max, Greg, Karsten, Mel, Tiemann


== Agenda ==
== Agenda ==
Line 17: Line 13:
** [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 update team contact info] (link to internal-to-RH wiki)
** [http://commarch.usersys.redhat.com/wiki/Contact Update team contact info] (link to internal-to-RH wiki)


== Deliverables before vacation ==
== Deliverables before vacation ==
Line 24: Line 20:


=== Max ===
=== Max ===
* FY11 budget.
* FY11 budget v2.
* Dashboard presentation and 2-hour mrc year-end-meeting.
* Dashboard presentation and 2-hour mrc year-end-meeting.
* 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 ===
* Cloud plan including bstevens communication that we can begin to execute immediately after vacation and share with mrc.
* 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.
* 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.
** I'd really just suggest a FLOSSmanuals writing sprint. They plan and organize (they do it very, very well), we fund (same level as a FAD), maybe even try to get it done over winter break if various professors can be brought together. (Summer may be more realistic, though.) [[User:Mchua|Mel Chua]] 04:20, 14 December 2009 (UTC)
* 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.
* <s>Big Ideas Fest trip report.</s>
* Go through your RT tickets and triage/update.


=== Karsten ===
=== Karsten ===
Line 38: Line 38:
* 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 ===
* POSSE's future organization, planning, branding, etc.  The stuff we spoke about on Friday night of FUDCon in the hotel room.
* 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.
** Deadline (I'm thinking Feb) and process posted for planning this summer's POSSEs, so we know the scope of things we have to manage right now
* Fedora Scholarship 2010 in good shape.
* Wrap up FUDCon Toronto
** <s>Every expense report for FUDCon Toronto filed and approved.</s>
** <s>FUDCon FAD scheduled with reg open to roll additional followup into generic Events infrastructure</s>
* <s>Fedora Scholarship 2010 open and accepting applicants</s>
* <s>Go through your RT tickets and triage/update.</s>


[[Category:Community Architecture meetings]]
[[Category:Community Architecture meetings]]

Latest revision as of 03:40, 12 January 2011

Roll call

Max, Greg, Karsten, Mel, Tiemann

Agenda

Deliverables before vacation

Listed by primary owner. Don't be afraid to ask for help.

Max

  • FY11 budget v2.
  • 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.
    • I'd really just suggest a FLOSSmanuals writing sprint. They plan and organize (they do it very, very well), we fund (same level as a FAD), maybe even try to get it done over winter break if various professors can be brought together. (Summer may be more realistic, though.) Mel Chua 04:20, 14 December 2009 (UTC)
  • 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.
    • Deadline (I'm thinking Feb) and process posted for planning this summer's POSSEs, so we know the scope of things we have to manage right now
  • Wrap up FUDCon Toronto
    • Every expense report for FUDCon Toronto filed and approved.
    • FUDCon FAD scheduled with reg open to roll additional followup into generic Events infrastructure
  • Fedora Scholarship 2010 open and accepting applicants
  • Go through your RT tickets and triage/update.