SeaMonkey:Home Page: Difference between revisions
m (make in-wiki link more-apparant) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{SeaMonkey-Resources}} | |||
{ | |||
The '''Mozilla "SeaMonkey" application suite''' should get its new wiki home here. | The '''Mozilla "SeaMonkey" application suite''' should get its new wiki home here. | ||
Revision as of 22:44, 11 March 2005
 | ||
| Resources | ||
|---|---|---|
| SeaMonkey Homepage | ||
| FAQ / Help | ||
| Goals | ||
| Organization | ||
| QA | ||
| Supporters | ||
| Add-ons | ||
| Localization | ||
| Reasons | ||
| Branding | ||
| Release History | ||
| Tasks & Projects | ||
| ||
| Discussion | ||
| Suiterunner |
The Mozilla "SeaMonkey" application suite should get its new wiki home here.
Status
The Mozilla Foundation have announced that there won't be any more official releases of SeaMonkey but they will provide infrastructure for community members who wish to continue development. SeaMonkey survival will need a new team that cares about that product and that will take over the lead for its development.
What we currently need for the survival of this product is some place to turn to for people who want to support us, and a plan how the immediate future of SeaMonkey should look like. Additionally, someone should be the project leader and officially the contact for the "outside world" (MoFo, etc.) on matters that concern the SeaMonkey project. We're still working on that.
Boris Zbarsky has posted an open letter to MoFo signed by a number of interested parties, laying out a community transition plan. MoFo are agreeing to support this plan.
MoFo Transition Plan Announcement
The plan
For one thing, we have to get a 1.8 release out the door.
In preparation for this 1.8 release, we need as many testers as possible to download and use Mozilla 1.8 beta 1 or recent nightly trunk builds. Bugs should be reported in Bugzilla (after checking for duplicates) and regressions marked with the regression keyword. This way, we'll be able to see what bugs need to be fixed before a 1.8 release.
For the future, the first step, is that we have to get SeaMonkey to use the infrastructure of the new products (for example the toolkit which is discussed in bug 255807), preferrably up to the whole XULRunner thingy. We also should port a few things of the new apps back to SeaMonkey, but retain what makes us like the suite.
I guess we could do a list here of what's to do and who is working on what.
An overview of some thoughts of what has to be done is available at the user page of Biesi
The team
We're in the process of gathering people together to form a SeaMonkey project team, we'll see what comes out of that... A list of the currently known supporters is kept on a separate page (SeaMonkey:Supporters).