Help me help you keep track of more meetings
December 5th, 2007 | Published in Work | 4 Comments
Each week we’re going to be publishing a list of upcoming public Mozilla project meetings in the about:mozilla newsletter. I need your help in ensuring we have a comprehensive and up-to-date list.
What follows is what I currently have, but I’m almost certain it’s incomplete. If you know of other public (as in “anyone can call in”) weekly meetings or events that should be on this list, please leave a comment here. This includes all Mozilla projects and departments, and shouldn’t be restricted to just Firefox and Gecko.
Note! If you haven’t signed up for the newsletter yet, you can do so at the about:mozilla newsletter sign-up form!
Monday
- 9:00a Pacific – Mobile
- 10:00a Pacific – SUMO (support.mozilla.org)
- 1:00p Pacific – Project Status
Tuesday
- 11:00a Pacific – Firefox/Gecko
- All day – Bug Day!
Wednesday
- 9:30a Pacific – Mac Gecko
- 9:30a Pacific – Performance SWAT team
- 10:00a Pacific – Performance/Leaks
- 11:00a Pacific – Mozilla 2
Thursday
none
Friday
- All Day – Test Day
December 5th, 2007 at 3:13 pm (#)
Can’t we just have those meetings in a Google Calendar and pull from there, like the Mozilla Developer’s Calendar?
http://www.google.com/calendar/embed?src=pdighgf028nmbjbrno8oed8vsg%40group.calendar.google.com
That would make it really easy for people with various calendar apps to stay up to date.
December 5th, 2007 at 3:13 pm (#)
Can’t we just have those meetings in a Google Calendar and pull from there, like the Mozilla Developer’s Calendar?
http://www.google.com/calendar/embed?src=pdighg...
That would make it really easy for people with various calendar apps to stay up to date.
December 11th, 2007 at 6:29 pm (#)
I think we’re renaming the “Performance SWAT” meeting to “Performance Infrastructure” since it’ll be more about setting up machines and the like, rather than discussing code. This is being discussed as we speak.
December 11th, 2007 at 6:29 pm (#)
I think we’re renaming the “Performance SWAT” meeting to “Performance Infrastructure” since it’ll be more about setting up machines and the like, rather than discussing code. This is being discussed as we speak.