SeaMonkey:Project Goals: Difference between revisions
Pweilbacher (talk | contribs) m (→Target Audience: (you wanted this deleted quickly...)) |
|||
| Line 14: | Line 14: | ||
* advanced users looking for a sophisticated web client | * advanced users looking for a sophisticated web client | ||
* developers and web developers | * developers and web developers | ||
==First Release== | ==First Release== | ||
Revision as of 23:15, 27 March 2005
 | ||
| Resources | ||
|---|---|---|
| SeaMonkey Homepage | ||
| FAQ / Help | ||
| Goals | ||
| Organization | ||
| QA | ||
| Supporters | ||
| Add-ons | ||
| Localization | ||
| Reasons | ||
| Branding | ||
| Release History | ||
| Tasks & Projects | ||
| ||
| Discussion | ||
| Suiterunner |
Primary Goal
The main goal of the project is to keep a suite which is similar from a user's perspective to Mozilla 1.7.x. We are not aiming to tie Firefox and Thunderbird together in some way, or make SeaMonkey drastically more similar to FF & TB.
We plan to move to toolkit/ for the sake of code maintenance - we don't want to end up with another Firefox and Thunderbird. The suite should continue to look and feel similar to how it always has. One of the major concerns here is random changes to toolkit that have occurred in the past; moving to toolkit is contingent on the Mozilla Foundation committing to a more stable set of widgets.
Target Audience
Our target audience consists of:
- people currently using the Mozilla Suite
- people currently using Netscape 4-7 who would like a product that feels similar
- people looking for an integrated suite of internet applications
- corporate users looking to deploy a single product
- advanced users looking for a sophisticated web client
- developers and web developers
First Release
For the first release, we're looking at continuing development from the 1.8 beta1 release by the Mozilla Foundation - the product will be fundamentally the same (just with a new name and whatever development has happened in the time since the release).
Future Releases
The future releases should be a complete transition to toolkit/ code. This will entail a lot of backend grunt work, so feature additions will likely have to be lower priority. Once the transition to toolkit is complete, we want to move to XULRunner - being based on toolkit already should make this as painless as possible (which is still likely to be very painful). Embedders will not be happy.