Mailing List |
How To Host Your Own Mozilla Meeting
Mozilla Community Day takes place on the last day of the O'Reilly Open Source Conference in the Conference facilities, and is designed to complement the presentations of the Mozilla Track. Those who attend the Conference will have had 2 days of presentations from experts about where we are and how to use the Mozilla code. During Community Day, we'll move the focus to look at what people are doing with Mozilla, how we work together and where we ought to be going. We'll shift the format as well, moving to discussion, brainstorming, Q&A and getting to know each other.
During Mozilla Community Day we'll think about the project as a whole, plan for the future, spend some time looking at the cool things people are doing with Mozilla, and dream up wild plans of what comes next. We've organized some anchor points to give the day structure and a core set of content. The anchor points are listed as "Definite" below. We'll also make adjustments real-time as we learn what people want. Some thoughts on possible adjustments are also listed below.
Mozilla Community Day is open to all interested parties, whether or not you're attending the O'Reilly Open Source Conference. If you are attending the Conference, participation in Mozilla Community Day is included with your registration, so just come by. The session schedule matches that of the rest of the O'Reilly Conference. Registration for attendees who are not attending the conference is $100 and includes breakfast and break food. This fee does not entitle you to attend other Conference sessions. Also, please note that the cost of lunch is not included in either the O'Reilly conference registration or the Community Day Registration.
To register for the mozilla.org Community Day, go to the O'Reilly onsite registration, located in the Exhibit Hall, starting at 7:00am on Friday, July 27th. Breakfast begins at 7:00am in the tent. So we can get an idea of how many people will be attending, please also email your name and email address to email@example.com.
I. 10:45-11:15 Opening Session A. Definite: Plan for the day B. Possible: Introductions II. 11:15-12:15 Session A. Definite: Mozilla 1.0 and Beyond: API "freezes", versioning and compatibility. B. Possible: Mozilla 1.0 and Beyond: features and other aspects. III. 12:15-1:45 Informal BOF Lunches and Bazaar (All Conference/Community Day attendees are on their own for lunch Friday; lunch is not provided with either registration) A. Definitely available BOFs Technical discussion (shaver, or mang) Community QA, milestone planning and releases, questions about firstname.lastname@example.org (Asa) Management of the Mozilla Project; licensing, marketing or "pr" (Mitchell) B. Possible Additional or replacement BOFs can be added depending on interest. IV. Bazaar A. Definite: room open and available for mingling, impromptu demos, etc. V. 1:45-3:15 Session A. Definite: Community QA, Phase II: where is Mozilla Community QA headed and what new activities might it take on? B. Definite: Commercial Forum: discussion of issues particularly pertinent to commercial teams building Mozilla based product. C. Possible: technical Help session, V. 3:15-3:45 Show and Tell. VI. 3:45-4:45 Session A. Definite: mozilla.org: today and beyond: Where we are and where should we be going? Who can help and how? B. Possible: Non-commercial forum: issues particularly pertinent to those using Mozilla in non-commercial projects C. Possible: web standards evangelism D. Possible: technical help session VII. 4:45-5:15 Closing Session A. Definite: What we learned; Next steps