About SeaMonkey

The SeaMonkey project is a community effort to develop the SeaMonkey all-in-one internet application suite. Such a software suite was previously made popular by Netscape and Mozilla, and the SeaMonkey project continues to develop and deliver high-quality updates as well as new features and improvements to this concept. Containing an Internet browser, email & newsgroup client, HTML editor, IRC chat and web development tools, SeaMonkey is sure to appeal to advanced users, web developers and corporate users.

SeaMonkey is built on the open source Mozilla Gecko engine, the same code which underlies the highly successful Thunderbird and is the base for the Firefox browser. SeaMonkey benefits from the cross-fertilization with these other projects, by gaining (and contributing) new features and the ongoing security updates which are a modern necessity. The SeaMonkey Association provides legal backing for the SeaMonkey Project.


SeaMonkey current Council

The SeaMonkey Council is the project leading team. Its responsibilities include release management (deciding when to cut releases and what code is included in a release; the release engineer of the Council is responsible for actually doing the release) and being the final instance for decisions about features when developers disagree. The SeaMonkey Council also decides on legal issues concerning the SeaMonkey project, in conjunction with the Mozilla Foundation, which provides legal backing for the project.

Members (in alphabetical order by last name):

Frank-Rainer Grahl (frg)
frg does development and support work. He is actively involved in most SeaMonkey areas. As a former software developer on z/OS he joined the team in 2015 to brush up his skills and got a bit more involved than he originally planned. When he is not doing work on SeaMonkey he can be usually found fixing or playing pinball machines.
Ian Neal (IanN) - SeaMonkey code module owner
Ian does work on XUL/JS stuff (mainly UI but also some backend) with a little bit of simple C++ stuff thrown in. He is the de facto project manager and main reviewer and has been actively involved in Mozilla development for about two years before the SeaMonkey project was started.
rsx11m does development and support work. He is mostly doing development in the preferences and mail/news areas of SeaMonkey.
Edmund Wong (ewong) - release engineer
ewong took over from Callek as the Release Engineer for SeaMonkey. He is doing the releases and working on the Build Config area in the SeaMonkey Code.

SeaMonkey Council Members Emeriti

No longer active in the project, we owe these Council members a great deal for making the current SeaMonkey the only full Internet suite left on earth.

Former Members (in alphabetical order):

Philip Chee (Ratty)
You are Philip Chee, an eccentric extension developer who started using the Suite when it was still called Mozilla. You eventually got involved in SeaMonkey development some time in 2006. You work on the front end of SeaMonkey (XUL/CSS/JS) and have applied yourself to most parts of SeaMonkey. Your main areas of focus are customizable toolbars and tabbed browsing. You are also actively involved in community outreach including communicating with end users and extension developers. Your less desirable traits include the regrettable tendency of posting the occasional snarky comment in Firefox and Thunderbird forums, and talking about yourself in the second person.
Karsten Düsterloh (Mnyromyr)
Karsten's Mozilla addiction started as a Netscape 1.1 user and hasn't left him since - in late 2002 he published the first version of his Mozilla addon Mnenhy. His key focus is upon SeaMonkey's MailNews development.
Jens Hatlak (InvisibleSmiley)
Jens has been a Mozilla user since the early days, naturally migrating to SeaMonkey and eventually starting to contribute. He is mainly involved in Sync, general suite UI (including MailNews), Help and website maintenance.
Robert Kaiser (KaiRo)
KaiRo has been working on localizing the Mozilla suite (now SeaMonkey) since late 1999. He served as project coordinator until 2011. He was also doing the EarlyBlue and LCARStrek themes and add-ons for data and download management, among others. See also KaiRo's blog and the German SeaMonkey site.
Neil Rashbrook (Neil) - former SeaMonkey code module owner
Neil was the "module owner" of XPFE (most of the SeaMonkey-specific code), and a super-reviewer focussed on XPFE and MailNews. He was very involved in all SeaMonkey related development for years.
Justin Wood (Callek)
Justin has been working on Mozilla since early 2003, he used to advise ewong in all tasks SeaMonkey release related.

Project Area Owners and Peers

The SeaMonkey Project can be divided into several areas, which are listed on our project areas list. Each of those areas should have an owner and possibly several peers (people who know the code well enough to give reviews there), who together care about that area. The sum of those areas build a strong group of developers, who can move the SeaMonkey project forward.


Additionally, there's a vibrant community surrounding those developers, see the SeaMonkey community page for how to get in touch with those people.
If you want to take an active role in testing or even developing SeaMonkey, getting involved with the project is fairly easy for anybody who can donate their time to our efforts.


For support and help or even development questions, please turn to our community which usually can help you faster and often better than our very small project steering team, the SeaMonkey Council. If you are seeking general support, send your question to the support mailing list and include which version of SeaMonkey your are using and on which platform (Windows/Linux/Mac). In order to receive the replies you also need to subscribe to the list.

If you have questions about legal issues, project management issues or topic that need to stay undisclosed to the wider public, please mail the SeaMonkey Council at seamonkey-council@mozilla.org.
Please do not use the Council address for support requests!

If you find an issue with this website, please check whether it has already been reported and file a new bug if necessary.