Confirm
455
edits
Changes
no edit summary
== Backstory ==
Once upon a time, Netscape/AOL used to host informal gatherings of Mozilla developers for day-long miniconferences. People would talk about what they were working on, get help with problems, put faces to IRC nicks, and debate the various potential futures of the project.
These "developer days" were good.
And now they're back.
== When and Where ==
The first pair of modern-era Developer Days will be held the last week of March, 2007. Specifically:
West Coast: Sunday, March 25, 2007, Mozilla Corporation HQ, Mountain View, CA.
East Coast: Friday, March 30, 2007, Location TBD, Boston, MA.
== But that's really far from Europe/Asia/Africa/New Zealand/South America/Antarctica! ==
Hard to argue with that! The only thing harder than finding good vegan food in rural Texas is choosing physical locations for Mozilla-related events. We're starting with these two spots because they will make logistics easier, and restarting this fine tradition has enough complexity and sufficient unknowns as it is.
These are the first, not the last. We don't know how often we'll have them, but it'll sure be more frequently than every 5 years, and we'd like to do them several times a year. The format may well need to be different to make sense in other places, but we'll figure that out as we get closer to those. (Many Europeans will be having something <i>suspiciously like</i> a Developer Day at FOSDEM at the end of February, and there was recently a Developer Day held by Mozilla Japan in Tokyo, so things aren't as North American-centricly dire as they might appear.)
== These Developer Days are... ==
* for <b>active Mozilla developers</b>;
* loosely structured and very much attendee-guided in terms of format and topic;
* limited in size, which means that, quite possibly, not everyone who wants to come will be able to fit (see above, though, about these not being the last);
* entirely appropriate for grabbing a few people and holing up in a room to hack out a fix or extension;
* entirely appropriate for presenting works in progress, especially as they may affect other developers;
* going to be recorded/broadcast/minuted as best we're able;
* going to be a lot of fun, if we have any say in the matter.
== These Developer Days are not... ==
* aimed at people who want to learn about Mozilla development (those sorts of folks are welcome in the project and community, and helping them get up to speed is certainly worth some investment, but that's not what <b>this</b>
* a place to advertise your company's product or project, though if you are an <b>active Mozilla developer</b> you can certainly come and join discussion of things that are relevant to your product or project;
* fully-funded endeavours, so we won't be able to pay for travel for everyone who might like to attend (even subject to the limited spaces mention above); we may be able to help with travel expenses for an <i>extremely</i> limited number of people, if there are key developers who have no other way of arranging such things;
* set in stone, though we would prefer to make changes based on experience with these first two rather than debate potentialities before-hand; please try to keep your suggestions concrete, focused, and respectful of the fact that many different people will have different goals in their attendance, and may not consider your Obviously Most Important thing to be as important to them!
Once upon a time, Netscape/AOL used to host informal gatherings of Mozilla developers for day-long miniconferences. People would talk about what they were working on, get help with problems, put faces to IRC nicks, and debate the various potential futures of the project.
These "developer days" were good.
And now they're back.
== When and Where ==
The first pair of modern-era Developer Days will be held the last week of March, 2007. Specifically:
West Coast: Sunday, March 25, 2007, Mozilla Corporation HQ, Mountain View, CA.
East Coast: Friday, March 30, 2007, Location TBD, Boston, MA.
== But that's really far from Europe/Asia/Africa/New Zealand/South America/Antarctica! ==
Hard to argue with that! The only thing harder than finding good vegan food in rural Texas is choosing physical locations for Mozilla-related events. We're starting with these two spots because they will make logistics easier, and restarting this fine tradition has enough complexity and sufficient unknowns as it is.
These are the first, not the last. We don't know how often we'll have them, but it'll sure be more frequently than every 5 years, and we'd like to do them several times a year. The format may well need to be different to make sense in other places, but we'll figure that out as we get closer to those. (Many Europeans will be having something <i>suspiciously like</i> a Developer Day at FOSDEM at the end of February, and there was recently a Developer Day held by Mozilla Japan in Tokyo, so things aren't as North American-centricly dire as they might appear.)
== These Developer Days are... ==
* for <b>active Mozilla developers</b>;
* loosely structured and very much attendee-guided in terms of format and topic;
* limited in size, which means that, quite possibly, not everyone who wants to come will be able to fit (see above, though, about these not being the last);
* entirely appropriate for grabbing a few people and holing up in a room to hack out a fix or extension;
* entirely appropriate for presenting works in progress, especially as they may affect other developers;
* going to be recorded/broadcast/minuted as best we're able;
* going to be a lot of fun, if we have any say in the matter.
== These Developer Days are not... ==
* aimed at people who want to learn about Mozilla development (those sorts of folks are welcome in the project and community, and helping them get up to speed is certainly worth some investment, but that's not what <b>this</b>
* a place to advertise your company's product or project, though if you are an <b>active Mozilla developer</b> you can certainly come and join discussion of things that are relevant to your product or project;
* fully-funded endeavours, so we won't be able to pay for travel for everyone who might like to attend (even subject to the limited spaces mention above); we may be able to help with travel expenses for an <i>extremely</i> limited number of people, if there are key developers who have no other way of arranging such things;
* set in stone, though we would prefer to make changes based on experience with these first two rather than debate potentialities before-hand; please try to keep your suggestions concrete, focused, and respectful of the fact that many different people will have different goals in their attendance, and may not consider your Obviously Most Important thing to be as important to them!
