From Fedora Project Wiki

No edit summary
No edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Community Architecture Meeting :: Monday 2008-08-04 =
== Roll call ==
== Roll call ==
Present: [[MaxSpevack]], [[GregDeKoenigsberg]], [[HarishPillay]], [[KarstenWade]], [[PaulWFrields]]
Max, Greg, Harish, Karsten, Paul
 
Absent: [[JackAboutboul]] (traveling to LWCE SF)


== Ambassadors ==
== Ambassadors ==
Line 18: Line 14:
== Q3 Budget ==
== Q3 Budget ==


Insanely tight.  No buffer for overrun, like Q2. Unless we change our own attitudes, we will go over budget.  And then there will be consequences.
Insanely tight.  No buffer for overrun, like Q2.
 
* https://fedoraproject.org/wiki/CommunityArchitecture/Expenses
* https://fedoraproject.org/wiki/Ambassadors/SteeringCommittee/Budget


== Vacation ==
== Vacation ==
* Max PTO.  Out starting Tue. Aug. 5.  Returns Wed. Aug. 13.
* Max PTO.  Out starting Tue. Aug. 5.  Returns Wed. Aug. 13.
* No CommArch meeting next week.
* No CommArch meeting next week.
[[Category:Community Architecture meetings]]

Latest revision as of 02:55, 12 January 2011

Roll call

Max, Greg, Harish, Karsten, Paul

Ambassadors

  • Confusion on FAMSCo list about why #fedora-ambassadors was started, when #fedora-mktg previously served as a home for both.
  • Max posits that that Fedora Ambassadors is one of the tactical arms of the larger Fedora Marketing strategic group.

Q2 Budget

I am going on vacation. When I get back, I would like to see every single person who handles CommArch money have their expense reports DONE and FILED for Q2, and I would like to have a list of expense report numbers and dollar amounts that I can plug into our budget.

It is a FACT at this point that we will be over budget. I really don't want to get back from my vacation and have to nag everyone about expense reports with the end of the quarter on the horizon. Help me.

Q3 Budget

Insanely tight. No buffer for overrun, like Q2.

Vacation

  • Max PTO. Out starting Tue. Aug. 5. Returns Wed. Aug. 13.
  • No CommArch meeting next week.