The about:sumo experiment

A while back, the idea of creating an about:sumo newsletter was
proposed. Since then, we’ve been so busy with other parts of SUMO, that
we never got to follow through on that idea.

We haven’t forgotten! In the next three months, we’d like to test out
the idea, and see how it goes. The purpose of the newsletter would be to
provide a digest of news from the SUMO world for those who are not
actively involved, but still interested in knowing what we’re working on.

Over the next three months, we’ll publish a newsletter each month, and
depending on the feedback from the community, we’ll know whether or not
to make the newsletter a regular thing. Stay tuned for more information.

3 comments on “The about:sumo experiment”

  1. Bubo wrote on

    Do i get to proof read?

  2. Pseudonymous Coward wrote on

    Just recently, the NoScript/Adblock Plus controversy serves to highlight some fundamental problems with the questionable security model of the Firefox add-ons mechanism. Why are add-ons able to mess around with each other? Why must I trust that my Firefox browser will do the right thing now?

    An AMO policy is all well and good, but it is only as strong as its weakest adherent. What Mozilla needs to do is technologically enforce its AMO policy. Suggestions:

    1. A strong Javascript sandbox. (A built-in NoScript, if you will.)
    2. Why on earth do add-ons have such raw power in Firefox? We need a strong add-ons sandbox too.

    Seriously, Google Chrome at least has a very strong security model. That is far more important to establish before an add-ons mechanism, I think. If Mozilla can spend a significant amount of time competing with other browsers to copy the idea of Javascript JIT compilation, I think it should spend its time copying other virtues such as a rock-solid sandbox.

    Thank you.

  3. Chris Ilias wrote on

    Pseudonymous Coward: Your comment seems to be about AMO and this blog is about (SUMO) not AMO. Try posting in the newsgroup/mailing list.