Talk:Mozilla Application Suite/Archive 1

message: "In February 1998, Netscape released most of the code base for its popular Communicator suite (including the Navigator browser) under an open source license.  To support Mozilla's collaborative development, Netscape also created the Mozilla organization and mozilla.org website."
These sentences seem a little disjointed.  It's not clear what Mozilla is.  I'd fix it, but I don't know enought to fill in the gap.  I think we just need a connection between open-source Communicator and Mozilla.  --Spikey 16:23, 21 Dec 2003 (UTC)
replies: text: I've had a go. -- Tarquin 16:31, 21 Dec 2003 (UTC)

text: Well, first of all AOL didn't release it under an open source licence - Netscape Communications Corporation, which was at the time a completely independent company, did; the article seems to me to be pretty clear on that. But as to why they released it, perhaps we could do with a bit more info. Basically, I think they wanted the help of the masses in bringing their next version up to scratch, seeing as something of a revolution was clearly needed... - IMSoP 00:24, 23 Oct 2004 (UTC)
thread_title: First two sentences

message: I thought that the list at the bottom of the subprojects section looked mixed. The header reads
"Also, the task of Mozilla development itself spurred the creation of tools for geographically distributed, cross-platform software development. Some of these tools were widely adopted by the larger open source community, including the following:"
and the list includes Thunderbird and Rhino. I never heard of Rhino, but I use Thunderbird and I don't think that Thunderbird is well described as a tool for geographically distributed, cross-platform software development, although it can be used for that. Am I missing something, or should Thunderbird and Rhino be removed?--Chealer 07:51, 2004 Oct 16 (UTC)
:Rhino, apparently, is  a by-product of Netscape's abandoned "Javagator" project that also produced Grendel; both are related to Mozilla in that they have been continued as open source projects under the auspices of mozilla.org, but it looks to me like Mozilla itself uses the C-based SpiderMonkey for its JS engine.
:I certainly think Thunderbird is misplaced here; in fact, I think the "sub-projects" and "spin-off browsers" sections need reorganisation, and possibly merging - certainly they should be next to each other, rather than with other sections in between. Perhaps "Mozilla technology" could mention the structure of the suite itself, and then a "Related projects" section could deal with:
#Development tools: bugzilla, tinderbox, bonsai, etc
#Gecko-based browsers: whether they be gecko-GUI'd or just gecko-rendered
#Projects based on Mozilla code: thunderbird, sunbird, XMLTerm, et al
#Other projects hosted by mozilla.org: rhino, grendel, ElectricalFire, Mstone (although it's hard to tell where on the scale from 'active' to 'abandoned' these projects are)
:What think ye? - IMSoP 14:00, 16 Oct 2004 (UTC)
replies: text: Well, I've gone ahead and re-arranged it, so if anyone thinks I've done it really badly, they'll have to rearrange it better . Actually, my main worry is that this page as a whole is rather large, and could possibly do with being split up somehow. Hm... - IMSoP 20:03, 23 Nov 2004 (UTC)
thread_title: Subprojects

message: It appears that there is some criticism of the way Mozilla handles security problems. See ,  and the following RUS-CERT advisory (can't read that last one, could someone translate?). Also see http://www.mozilla.org/projects/security/security-bugs-policy.html We really should be adding this to the article, I just don't know where to put it. Also, we have nothing on the XUL vulnerability that I saw a while ago. If we pretty much flay Internet Explorer, then we should be at least adding this information to our article. - Ta bu shi da yu 06:20, 15 Dec 2004 (UTC)
replies: text: Not that I'm necessarily disagreeing with you, but we have to keep things in perspective.  Mozilla isn't constantly on the news (and by news I mean things like CNN and BBC), with stories about security bugs that need to be patched ASAP.  As far as I remember, the White House hasn't felt it necessary to hold a press conference to talk about security issues with Mozilla.  Can't say they won't in the future, but it hasn't happened yet.  AlistairMcMillan 09:41, 15 Dec 2004 (UTC)
replies: text: No, but it has had some security issues, though not many to be sure and Mozilla has a much better track record than I.E. I don't see why we can't cover them. I mean, I'm not endorsing the criticism. At work I refuse to use anything except for Firefox. I just won't use IE. But nonetheless, criticisms have been made and I do think it means that we should report them. Besides this, my point wasn't meant to be a comparison between I.E. and Mozilla. It was meant to show that if we cover one thing in a similar article, and there is similar criticism for another related article it seems a bit POV not to include that criticism. - Ta bu shi da yu 12:59, 15 Dec 2004 (UTC)
thread_title: Security information

message: Mozilla will support XForms really soon . Should we mention it here or in Gecko? -- Minghong 20:15, 25 Jan 2005 (UTC)
thread_title: XForms

message: This article should be cleaned up. e.g. "Mozilla-based app" should be moved to Gecko; "Mozilla Suite" should be moved to Seamonkey (if it is the final name of the "Mozilla 1.8"). This article should turn into a description of the Mozila history, and pointers to other Mozilla Foundation projects/products. --minghong 09:09, 22 Apr 2005 (UTC)
replies: text: I agree that anything not specific to the Mozilla Application Suite should be moved to some other page. However, the info on the Mozilla Suite should stay here because the Seamonkey Suite will be a completely separate product. --Schapel 13:25, 22 Apr 2005 (UTC)
replies: text: Maybe move the suite related stuffs to "Mozilla Suite"? This name is used on Mozilla website . --minghong 08:14, 24 Apr 2005 (UTC)
replies: text: I've just done that. ;-) --minghong 17:36, 11 Jun 2005 (UTC)
thread_title: Clean up