Full Article Attached New tinderstatus Tool Available

Thursday January 16th, 2003

In a newsgroup posting, Myk Melez announced the availability of tinderstatus, a new browser extension that allows you to quickly see the current status of the SeaMonkey tree. The extension should be particularly useful for sheriffs (those assigned to watch over the tree), hackers who check in a lot of code and people who like pretty icons in their status bar.

You can install the extension in Mozilla, Phoenix and Netscape. Note that the current version does not include an uninstaller.

#10 Re: Re: Re: Uninstalling of extensions?

by asa <>

Sunday January 19th, 2003 1:21 PM

You are replying to this message

"For now I think Netscape made Mozilla just for using thousands of free testers and some free development. Can someone comment on this?"

I wasn't in the room when the folks at Netscape were making these decisions so I can't comment from direct experience. I don't think your speculation is at all correct though. It's definitely not now the case, or for the last few years that I've been directly involved in Mozilla.

"I begin to think that Netscape made Mozilla just for releasing own branded versions."

Maybe you weren't around back in the old days so this might be news to you but there haven't always been binaries and when Netscape released the code and created it was clear from statements coming out of that wasn't a binary distribution. "The products of Mozilla are source code and their customers are developers. Whereas the products of Netscape Client Group is a program, a binary and its customers are users." "Mozilla is not engaged in producing binaries intended for users. It produced source intended for developers." <> That we have daily and milestone binaries today is because a lot of people, inside and outside of Netscape, thought it would make testing and development a lot easier for everyone involved.

"[Netscape] do not want many features that already are in Phoenix (and really needed and waited features!)"

Point me to one place where someone ported a Phoenix change over to Mozilla and it was rejected by a reviewer or Module Owner employed by Netscape. You're just making this up with nothing to support it.

"[Netscape] do not want a new splash-screen for mozilla

That's total bs. The splash screen has nothing to do with what Netscape wants or doesn't want. They don't use it and they don't care what it looks like., however, does. There are licensing issues, there are unity of UI design issues, but there is absolutely no Netscape involvement in this issue (with maybe the exception that people inside Netscape would like to see the end of the use of the old-style green lizard).

"[Netscape] do not want other fixes I was ready to contribute for..."

Point me to your fixes that were denied by a reviwere or a Module Owner employed by Netscape. I challenge you to point me to a single patch you've done that was rejected because Netscape didn't want it.

"What's the point of being open source, but when community does not have any influence what and when something will happends in the project. "

Right. Now you're just talking garbage. You just haven't been paying attention if you think that the community doesn't have any influence in the projects. Boo-hoo. It's a crying shame. hasn't done anything about the community concerns with the splash screen. That the community hasn't been able to get the splash screen changed doesn't mean jack when you look at the fact that the community convinced to throw out pretty much its entire browser and start over with a new XPFE based on the new Gecko rendering engine <http://www.mozillazine.or…/talkback.html?article=88> ? If the community didn't have any infulence then why did make the switch in Oct of 98 <…/roadmap-26-Oct-1998.html> ?

"Isn't this a major point why Apple desided to go with KHTML? Is Mozilla independent? "

No and yes.