SeaMonkey:Home Page: Difference between revisions
(→Meetings: add log of meeting) |
(SeaMonkey has landed, reflect that on the main SeaMonkey wiki page.) |
||
| Line 1: | Line 1: | ||
{{SeaMonkey-Resources}} | {{SeaMonkey-Resources}} | ||
This is the wiki home of the ''' | This is the wiki home of the '''[http://www.mozilla.org/projects/seamonkey/ SeaMonkey project]''', which continues development on the code of the Mozilla application suite. | ||
For quick answers to common questions, please explore the [[SeaMonkey:FAQ|SeaMonkey FAQ]]! | For quick answers to common questions, please explore the [[SeaMonkey:FAQ|SeaMonkey FAQ]]! | ||
| Line 7: | Line 7: | ||
== Status == | == Status == | ||
The Mozilla Foundation has announced that there won't be any more official releases of the Mozilla Application Suite | The Mozilla Foundation has announced that there won't be any more official releases of the Mozilla Application Suite, but they will provide infrastructure for community members who wish to continue development under the [http://www.mozilla.org/projects/seamonkey/news.html#2005-07-02 new project name "SeaMonkey"]. The project has a new team that is independent of the Mozilla Foundation, cares about that application and that takes over the lead for its development. | ||
The Mozilla Foundation still provides the new mozilla.org-hostes project with needed infrastructure, as promised in the [http://www.mozilla.org/seamonkey-transition.html "transition plan" document], as well as maintain the Mozilla 1.7.x application suite product, but concentrates development work on their new mainline products Firefox and Thunderbird. | |||
[http://www.mozilla.org/seamonkey-transition.html | |||
== The plan == | == The plan == | ||
We have created a [[SeaMonkey:Project_Organization#SeaMonkey_Council|Council]] group. This group will have final say over which bugs are in and which are out for a particular release (and be the group that has control over the relevant bugzilla flags), | We have created a [[SeaMonkey:Project_Organization#SeaMonkey_Council|SeaMonkey Council]] group. This group will have final say over which bugs are in and which are out for a particular release (and be the group that has control over the relevant bugzilla flags), is responsible for finding people to work on the bugs that need to be fixed, etc. | ||
Our [[SeaMonkey:Project Goals|Project Goals]] document describes where the project is basically headed. | Our [[SeaMonkey:Project Goals|Project Goals]] document describes where the project is basically headed. | ||
For one thing, we have to get | For one thing, we have to get [[SeaMonkey:First Release|SeaMonkey 1.0]] out the door. | ||
In preparation, we need testers to work on [[SeaMonkey:QA|SeaMonkey QA]] to help improve the quality of this first release. | In preparation, we need testers to work on [[SeaMonkey:QA|SeaMonkey QA]] to help improve the quality of this first release. | ||
| Line 28: | Line 22: | ||
A 'blocking-seamonkey1.0a' flag has been set up in bugzilla to help keep track of what needs to be done before the first release. You can [https://bugzilla.mozilla.org/query.cgi?product=Mozilla%20Application%20Suite&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=blocking-seamonkey1.0a create your own query] with this flag, or view the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%2B open approved bugs] and [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%3F yet to be approved bugs] blocking the release. | A 'blocking-seamonkey1.0a' flag has been set up in bugzilla to help keep track of what needs to be done before the first release. You can [https://bugzilla.mozilla.org/query.cgi?product=Mozilla%20Application%20Suite&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=blocking-seamonkey1.0a create your own query] with this flag, or view the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%2B open approved bugs] and [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%3F yet to be approved bugs] blocking the release. | ||
For the future, the first step | For the post-1.0 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 [https://bugzilla.mozilla.org/show_bug.cgi?id=255807 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. | We also should port a few things of the new apps back to SeaMonkey, but retain what makes us like the suite. | ||
| Line 37: | Line 31: | ||
== The team == | == The team == | ||
A group of very active SeaMonkey developers has recently gathered on IRC and agreed on a [[SeaMonkey:Project_Organization#SeaMonkey_Council|Council]] who are responsible for project and release mangement. | A group of very active SeaMonkey developers has recently gathered on IRC and agreed on a [[SeaMonkey:Project_Organization#SeaMonkey_Council|SeaMonkey Council]] who are responsible for project and release mangement. | ||
That doesn't mean we don't need an even bigger group of developers working on the product or taking resposibilities of certain areas in the project. We also need people doing QA and regular testing on our product. How those groups will be structured and organized is currently being discussed and we hope to have some information about that soon. | That doesn't mean we don't need an even bigger group of developers working on the product or taking resposibilities of certain areas in the project. We also need people doing QA and regular testing on our product. How those groups will be structured and organized is currently being discussed and we hope to have some information about that soon. | ||
Revision as of 16:26, 8 July 2005
 | ||
| Resources | ||
|---|---|---|
| SeaMonkey Homepage | ||
| FAQ / Help | ||
| Goals | ||
| Organization | ||
| QA | ||
| Supporters | ||
| Add-ons | ||
| Localization | ||
| Reasons | ||
| Branding | ||
| Release History | ||
| Tasks & Projects | ||
| ||
| Discussion | ||
| Suiterunner |
This is the wiki home of the SeaMonkey project, which continues development on the code of the Mozilla application suite.
For quick answers to common questions, please explore the SeaMonkey FAQ!
Status
The Mozilla Foundation has announced that there won't be any more official releases of the Mozilla Application Suite, but they will provide infrastructure for community members who wish to continue development under the new project name "SeaMonkey". The project has a new team that is independent of the Mozilla Foundation, cares about that application and that takes over the lead for its development.
The Mozilla Foundation still provides the new mozilla.org-hostes project with needed infrastructure, as promised in the "transition plan" document, as well as maintain the Mozilla 1.7.x application suite product, but concentrates development work on their new mainline products Firefox and Thunderbird.
The plan
We have created a SeaMonkey Council group. This group will have final say over which bugs are in and which are out for a particular release (and be the group that has control over the relevant bugzilla flags), is responsible for finding people to work on the bugs that need to be fixed, etc.
Our Project Goals document describes where the project is basically headed.
For one thing, we have to get SeaMonkey 1.0 out the door.
In preparation, we need testers to work on SeaMonkey QA to help improve the quality of this first release.
A 'blocking-seamonkey1.0a' flag has been set up in bugzilla to help keep track of what needs to be done before the first release. You can create your own query with this flag, or view the open approved bugs and yet to be approved bugs blocking the release.
For the post-1.0 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
A group of very active SeaMonkey developers has recently gathered on IRC and agreed on a SeaMonkey Council who are responsible for project and release mangement.
That doesn't mean we don't need an even bigger group of developers working on the product or taking resposibilities of certain areas in the project. We also need people doing QA and regular testing on our product. How those groups will be structured and organized is currently being discussed and we hope to have some information about that soon.
A list of the currently known supporters is kept on a separate page (SeaMonkey:Supporters).
Meetings
There was a Town Hall meeting at IRC on Wednesday July 6th 2005 at 15:00 UTC (log).
If you have agenda items, please e-mail Alex Vincent with your ideas.