DISQUS

I think another key aspect of the success of 911 as a citizen-knowledge is that there are strong incentives (social and legal) to not abuse the system. Swatting aside, this is one reason that the signal is so high, and that emergency services can react to a report from an unknown person with high confidence.

Yeah, we're actually taking the "if you're out of memory, the jig is up" approach in future versions of Firefox (possibly the sequel the Firefox 3, possibly the sequel's sequel). You can follow https://bugzilla.mozilla.org/show_bug.cgi?id=42... and its dependents (chiefly https://bugzilla.mozilla.org/show_bug.cgi?id=42...) if you're interested in the process, which will involve automatic rewriting across the width of our...substantial codebase. Better performance, less code complexity, improved security; it's not every day you get all of those in one package.

I believe that Deb'll also be syndicating the content via an RSS feed, possibly devnews. Might not happen in time for the first issue, though, but rest assured that she loves a good RSS feed at _least_ as much as anyone else.

Cédric: it's not clear from your comment what the specific problem is with Mailchimp, so it's quite difficult to act on it. Deb outlined in her previous post[*] why we are using Mailchimp, and specifically asked for feedback, so it's unfortunate that you didn't offer your detailed reasoning in response to that. Just as we have the Mozilla Store operated for us by another company, we believe that we can deliver a better newsletter if we don't have to build all the CAN-SPAM compliance, HTML-mail compatibility and other expertise ourselves; if there are specific problems with Mailchimp, though, we'd certainly like to hear them. If they aren't suitable for posting publicly, please send them to deb (at) mozilla (dot) com.

Thanks!

[*] http://www.dria.org/wordpress/archives/2007/11/...

Camino is developed by the Camino development team and community; it's not a product to which the Mozilla Foundation devotes resources, other than fixing bugs that they find in the core code, and providing server resources for things like source control and builds. I don't think that ignoring those (few) bugs or denying the Camino community those server resources would have any positive effect on Firefox, but I suppose someone might think otherwise.

As an aside, you shouldn't forget that you can participate in Mozilla's development directly, from layout engine to front end to testing to localization to user support; you're not restricted to hoping that things will go as you would like, or complaining if they don't, and we have literally thousands of people with no other software development experience who help us every day to improve Firefox and our other work.

I'm a little saddened that people would read a single article somewhere describing a very significant change in development philosophy and just take it at face value, when it's really so easy to find someone directly involved in the project or go to primary sources. (Not picking on you, Jake, as it happens a lot. I think a lot of people just aren't used to the fact that the developers of a major piece of their software arsenal are actually transparent and available.) Hopefully this round of (honest) error and correction will encourage people, bloggers and journalists alike, to dig a little deeper before sounding our death knell. :)

Lizard Bites!