Slashdot Mirror

← Back to Stories (view on slashdot.org)

Problems With the Firefox Development Process

Posted by Zonk on from the eyes-on-the-prize dept.

An anonymous reader writes "Mike Connor, one of the core Firefox developers, is raising a flag concerning the Mozilla Firefox methodology of development. From his blog: "In nearly three years, we haven't built up a community of hackers around Firefox, for a myriad of reasons, and now I think were in trouble. Of the six people who can actually review in Firefox, four are AWOL, and one doesn't do a lot of reviews." In an earlier entry, he raised concrete concerns about the community involvement. Asa Dotzler recently elaborated on the process, as previously covered on Slashdot."

3 of 563 comments (clear)

  1. It's the Branding by Baricom · · Score: 5, Interesting

    Seriously. Mozilla's obsessive-compulsive disorder when it comes to their trademarks is above and beyond any other open source project's, and I think it's probably turning a lot of people off toward helping them.

  2. That's strange... by Smerity · · Score: 5, Interesting

    That's strange...

    From what I read on the last Slashdot Mozilla/Firefox article, people thought that there were too many coders in Firefox, thus creating bloated code...

    I guess that's a myth, eh? Community misconception?

  3. Re:Bah, what's the big deal? by shadowmatter · · Score: 5, Interesting

    From the article:

    Of the six people who can actually review in Firefox, four are AWOL, and one doesn't do a lot of reviews. And I'm on the verge of just walking away indefinitely, since it feels like I'm the only person who cares enough to make it an issue.

    What good is people submitting patches if no one is there to review the code prior to commit? Indeed, I submitted a very trivial usability enhancement to Firefox, and it was quickly swept under the rug. Perhaps it should simply be made into a plug-in, I don't know. Just thought I would share it as first-hand experience.

    - shadowmatter