Mozilla Foundation in More Development Trouble

sebFlyte writes "After the reports of problems with Firefox' development earlier this week there are now rumblings about more serious problems with the Mozilla Suite. Some developers want to spin the suite out as a community project that the foundation has no responsibility for, and others want to create a Firefox Foundation to deal with the success of the standalone browser."

Comments

pointless?

[dhbiker]

wouldn't it be foolish to create a firefox foundation when so much of the firefox code comes from the mozilla suite (and vice versa to some extent)?

Re:pointless?

[LurkerXXX]

Since when has that stopped the open source community from forking code? It happens all the time. Most of the time it IS foolish and useless. Occasionally some good comes from the split. Like evolution, it's all a crapshoot.

Re:pointless?

[nine-times]

More to the point, the Mozilla foundation is dealing with a whole bunch of products from the original Mozilla suite (Thunderbird, Firefox, Sunbird, and others). What would be the point of pulling Firefox away from that?

It seems like the Mozilla Foundation made a decision that they preferred the Firefox development model. Firefox, Thunderbird, and Sunbird are set to be the *new* Mozilla suite, and the old one is in maintenance mode. It seems like this is comparable to people complaining that Microsoft isn't putting enough development into Windows 3.1.... Well, yeah, it's the old product that they've discontinued.

Now, it's all open source, so if someone wants to work on it, go ahead. But why people are trying to convince the Mozilla foundation to offload their new, exciting, successful, popular line-up of software and head back to what's become a bit of a dead-end, I don't know.

Re:pointless?

[Ubergrendle]

Proving once again that the Open Source community continues to be its own worst enemy. There's alot of pig-headed "If you don't play by ~my~ rules I'm taking my toys and going home!" attitude. I suspect its an artifact of the enterprenurial spirit that leads people to contribute to open source in the first place. And because the code is open, anyone can do this. Its the nature of the environment.

Unfortunately, a serious break with Mozilla at this point will INSTANTLY cripple Firefox adoption across enterprise organisations. Now not only do you have to pick a browser (or browser suite) to standardize upon, now you have to pick the flavour of that suite. IT managers (or CIOs) have to bet twice -- once that Firefox will continue to be an optimum choice down the road, and a second time that you chose the right 'branch'.

Microsoft, IBM, Google win their audience over by representing consistency. Here's a quick example: think of McDonalds -- poor quality food, but consistent in quality. People 99% of the time will go with what they know, rather than gamble on the family-run restaurant across the street, even though the family-run restaurant might represent a great hidden and unknown deal.

The wonders of open source

[Sparr0]

FOSS is great. They can do any or all of the above. I could fork my own version of Mozilla or Firefox right now if I felt that my development process was superior to that of the existing community. I dont see why there is such a big debate here. Do it, see how many developers flow to each side, work from there.

Meh

[AKAImBatman]

Some developers want to spin the suite out as a community project that the foundation has no responsibility for, and others want to create a Firefox Foundation to deal with the success of the standalone browser.

Or maybe... they could just leave it where it is? Is the Mozilla Foundation really all THAT bad? While I'm sure that everyone has reasons for their position, this smacks of a variation of "Not Invented Here Syndrome".

Re:Meh

[CTho9305]

It's not that the Mozilla Foundation is evil - there are a few issues here. First, they aren't saying much. Pretty much everything we hear is coming from only Asa Dotzler, not official statements by MoFo. Second, the Mozilla Foundation does have limited resources - the points people are making about two products being difficult are valid. Marketing is another big issue. It would be in the Mozilla Foundation's best interest to present ONE front: the aviary products (Firefox, Thunderbird).

I don't think NIH is the big problem - the problem is that while Firefox could have been just the browser portion of the suite, it isn't. It looks and feels different. The people who like the suite like the look and feel of it. Switching to Firefox means giving up a mature, stable, familiar user interface for something different that changes a lot with every 0.1 release (for example, Firefox 1.1 will have a completely rewritten preferences panel).

One of the major concerns right now of developers interested in SeaMonkey is the development process currently used for the aviary products: gigantic patches are included without any review, and often with very little testing. Regressions are found by users, and they file bugs which get fixed. However, the lack of review still allows much lower-quality code to enter the source. Between the landing of the patch and fixing of regressions, nightly builds (which developers work from) are often in very bad (unusable) shape.

The SeaMonkey front-end currently requires not one, but TWO reviews of all code. Does this slow the pace of development? Yes. It's extremely difficult to thoroughly review the bigger patches (doubling a patch length probably quadruples the work), but it maintains high code quality, and minimizes the introduction of new bugs. It helps that the SeaMonkey front-end is already mature, because less development needs to happen.

In theory, the Mozilla project was supposed to offer a cross-platform application development toolkit. This toolkit would be maintained, and an application written for it should work properly on future versions of the toolkit. This would offer a way to easily save Mozilla: port it over to this toolkit (which is just a modified version of what it uses right now, minus thorough code review). However, there is doubt among the developers that the Mozilla Foundation will actually keep this toolkit in usable shape - the track record of Firefox developers has been "change what we want when we want to", which would mean any application using this toolkit would need frequent updates. Porting the suite to a toolkit like this would mean we get all of the downsides (less code review), plus extra maintenance work required.

Basically, I think most of the suite developers just want their favorite browser not to die, and not to be based on shoddy code.

Helpful news?

[n0dalus]

This must be the third article about Firefox/Mozilla development process problems this week.
Aren't these kinds of problems going on with most projects, including proprietry software projects?
I can't help but feel as though people are just trying to run a smear campaign against the Mozilla Corporation.

Sheesh...

[gowen]

The article is headlined "Mozilla's future under debate"

How the hell did "under debate" become "More Development Trouble" in the /. headline.

(Answer : someone high up at OSDL clear believes "scandal-mongering = advertising revenue")

I think it is sad...

[AHarrison]

In a time when the open source community needs solidarity, one of the largest and most popular organizations is spreading itself too thin to the point of breaking.

I don't get it

[Jaeger]

I've been using Mozilla, in some capacity or another, for almost six years, and it's been the only browser I've used (on purpose) for at least five years. So I was confused when Firefox showed up on the scene and suddenly attracted attention. What is it that makes Firefox better than Mozilla? Firefox has tabbed browsing, and pop-up blocking, and all that, but Mozilla did it all two years ago.

Re:I don't get it

[nine-times]

As far as I know...

• Firefox is faster- I haven't tried it in a while, but at least a couple years ago, when I made the switch, Firefox loaded faster, and seemed generally more lightweight
• Firefox is prettier- totally a matter of opinion, but it seems to be the majority opinion that Firefox has a better interface all around
• Firefox's Extensions- I'm not a developer, but people seem to think that Firefox's extension system is easier, more flexible, and generally better than any means to alter/add-on to the Mozilla suite. (don't know much about it though)
• the Mozilla suite seemed stagnant- this is an issue of perception, but I've talked to a number of people that thought the Mozilla suite has a clunky interface from 10-15 years ago (it still looked like Netscape 4). The mere appearance of 'newness' was enough to get some people excited. Along these lines, the Firefox people have done a better job of making Firefox look native on various operating systems
• breaking Mozilla suit up made sense for development- eh, it's arguable, but many people seem to believe that breaking the suite up into its components (browser, e-mail, calendar, chat, composer, etc.) would make it possible for each individual component to progress faster. Besides giving people the ability to pick and choose the components they wanted, and increasing the efficiency of the resources used by not including components that people weren't going to use, there's the idea that breaking some of the interdependencies between components will allow developers to do, for each component, what is best and will make the most sense, without needing to worry as much about the effect on other components. The rapid progress of both Firefox and Thunderbird seems to indicate that there's something to it.

So that's what I can think of off hand. Personally, I'm not sure why a web browser ever had a e-mail program and HTML editor and chat all built into it anyway. Sure, make a suite, distribute them all together, but why make them all part of the same program?

Just started doing Firefox/XUL development

[Anonymous Coward]

Well I hope they don't lose any momentum because I just started doing Firefox development for some financial services companies. However, my perception is that development is much more difficult than it needs to be. In order to do anything significant, you have to get the entire tree and program in C++ with many different layers in between. I just think that the development doesn't feel like it's a "platform" you're developing on. The development SDK should be more like a development "kit". I know it hasn't stopped thousands of extensions from being written, but perhaps there could be more significant applications written otherwise.

Mod Parent up

[rider_prider]

I would if I had mod points. This is healthy open discussion about the future of an open source project. I seem to remember the original developers of what became Firefox started that project because they were unhappy with the direction of the mozilla browser at the time. This is not instability or trouble, it is part of the evolutionary process of open software...

"problems" inaccurate

[bmetz]

Sounds like a debate, which is what organizations do. They debate strategic moves. Saying they are having "problems" implies something else entirely.

Huh?

[rpdillon]

People in a team having differeent ideas for the future of a project != "in trouble".

"Google is in trouble - some employee want to bring Google News out of Beta, while others do not."

Re:Maybe...

[CTho9305]

It's trickier than that. A lot of developers like the suite much more than Firefox. Some core devs have suggested they might stop working on Gecko if the suite dies. The Mozilla suite is basically in the opposite situation of Firefox: Firefox has LOTS of users and apparently way too few developers; Mozilla has LOTS of developers and not as many users. Killing the suite doesn't mean all of those developers would jump ship to Firefox. I personally don't like Firefox, so I write code for Mozilla. If it comes down to "Firefox or else", there's a good chance I'd find something else to do with my time.

WTF is the big fat hairy deal?

[Qbertino]

Is the Licence so restricted? Can't anyone who would like to just fork the project?

It's open source people, this is how it works when heavy problems show up:

1) Gee cool project. I like the tool .

2) Gosh, I miss foo in this. But I guess someone would need to implement bar before that could work.

3)
- "Hey folks, I've done this patch. Could you check it out, merge it in and may I join the devteam?"
- "No. You stink. We don't want you. You know to much, and besides: I'm the big guru around here. Go away."
- "Ok. Sorry for wasting your time."

4) sf.net/my/.makeNewProject( my tool );

Or did I miss something here?

Why Firefox?

[gvc]

I'm a Luddite when it comes to Firefox. I don't really understand why it was created, notwithstanding that I've been told several times that if I had any savvy at all I would find the reasons apparent, as everybody else does.

I see it as brand-name dilution. I was an early Mozilla evangelist. Now all the people I converted from the dark side are terribly confused and groaning "Do I have to change again?" You mean I have to replace Mozilla browser/mail by 2 different programs? "It's almost the same only better - I'll help you convert" doesn't play very well as an answer.

I have no ready solution, now that Firefox has established a beach head (IMO, due to surrendipity and marketing rather than inherent superiority). I suppose I'll have to try my best to convince the disciples that they should change horses yet again.

I still use Mozilla

[Isldeur]

I don't know about the rest of you people but I still use Mozilla as my 3rd browser behind konqueror and firefox.

I'm sure other people have found similar things. It remains the only browser that opens most of those silly Javascript sub-windows. I can only imagine the other browsers don't do this because the javascript is some broken hack - but whether it is or isn't, sometimes you just need to open these things.

Abandoning Moz Suite undermines all products

[guanxi]

If they abandoned Mozilla Suite and its users, how do I know they won't abandon the current Firefox or Thunderbird apps?

That's the question every business will ask before adopting any other Moz app, if Mozilla Foundation abandons the Mozilla Suite. In fact, some will ask it about any FOSS product. That particular FUD already exists; this move would reinforce it.

It might seem unlikely that Firefox would be abandoned, but what happens to 1.0 when FF 2.0 comes out? Support and maintenance for old products is essential for any business customer; upgrading can be very expensive (deploying across thousands of computers, modifying any integrated software, etc) and often doesn't help the business' bottom line. IBM supports products forever, it seems; Microsoft supported Windows 98 until (last year?). The Linux 2.4 kernal is certainly maintaned; what about 2.2? IBM's name is behind Linux, anyway.

MoFo would look like an unreliable vendor with a good product. I posted in Slashdot previously that they aren't really community driven, which isn't necessarily a bad thing -- it's just different. It appears they may not be customer driven, either. What's driving MoFo?

Re:shame on slashdot

[Karn]

Perhaps you should learn how to sensationalize things like sebFlyte does. Honestly, what sounds better: "Mozilla Foundation in More Development Trouble" or "Mozilla Foundation Experiencing Perfectly Normal Behavior" ? The first implies that not only was the Mozilla Foundation in trouble before, they are now in even MORE trouble now! Based on this headline, I'd say it's only a matter of hours before the Mozilla project dies completely.

Community

[Anonymous Coward]

Developer's are often their own worst enemies, throwing a hissy fit every time things aren't going smoothly. It generates lots of useless emails and /. posts, but rarely does much good.

Mozilla and Firefox are not two separate entities, they are just two flavors of the same brand ice-cream. One can live without the other, but they are stronger together. If they separate, only the competition will benefit.

I'm fairly confident that many in the Mozilla/Firefox community know this and are not going to let some whiney volunteers cause a rift. Its natural for there to be problems in the community and for people to voice their discontent, but that doesn't mean the project is in jeopardy. It just forces people to look at what their doing and decide if there really is a problem that needs to be addressed. This is what helps community/volunteer-based development thrive after all, the constant reflection and criticism of the project that drives developers to do their utmost.