author Edmund Wong <>
Tue, 14 Nov 2017 17:02:33 +0800
changeset 1288 358a27aa17a1802258a1aa8df0ba20baff2cd6bb
parent 1226 46c701397e00758f1a38605aa0dca795bbce0daa
child 1303 b4421cc6179a282fa234c2106ef05e2249437dd2
permissions -rw-r--r--
Bug 1313962 - Update to point to #seamonkey on irc. r=IanN

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "">
<html lang="en">

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Language" content="en">
<meta http-equiv="Content-Style-Type" content="text/css">
<meta http-equiv="Content-Script-Type" content="text/javascript">

<link rel="top" href="./" title="SeaMonkey Project">
<link rel="up" href="./" title="Home">

<title>About SeaMonkey</title>
<h1>About SeaMonkey</h1>

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 &amp; newsgroup client, HTML editor, IRC chat and web
development tools, SeaMonkey is sure to appeal to advanced users, web
developers and corporate users.

<a href="" class="mozillapower"><img
 src="/images/powered_by_mozilla_small.png" height="31" width="122"
 alt="powered by Mozilla"></a>
SeaMonkey is built on the open source
<a href="">Mozilla</a> Gecko engine, the same code which
underlies the highly successful siblings Firefox and Thunderbird.
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 <a href="">Mozilla Foundation</a>
provides hosting and legal backing for the SeaMonkey Project.

<h2 id="org">Organization</h2>

<h3 id="council">SeaMonkey Council</h3>

<p>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.</p>

<p><strong>Members</strong> (in alphabetical order):</p>

  <dt id="Ratty">Philip Chee (Ratty)</dt>
    <dd>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.</dd>

  <dt id="Mnyromyr">Karsten Düsterloh (Mnyromyr)</dt>
    <dd>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 <code>Mnenhy</code>. His key focus is upon SeaMonkey's
        MailNews development.</dd>

  <dt id="InvisibleSmiley">Jens Hatlak (InvisibleSmiley)</dt>
    <dd>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. He is also running the unofficial <a
        href="" class="ex-ref">SeaMonkey Trunk
        Tracker</a> (as time permits).</dd>

  <dt id="KaiRo">Robert Kaiser (KaiRo) - project coordinator</dt>
    <dd>KaiRo has been working on localizing the Mozilla suite (now SeaMonkey)
        since late 1999. He's also doing the EarlyBlue and LCARStrek themes and
        add-ons for data and download management, among others.
        See also <a href="" class="ex-ref">KaiRo's
        blog</a> and <a href="" class="ex-ref">the
        German SeaMonkey site</a>.</dd>

  <dt id="IanN">Ian Neal (IanN)</dt>
    <dd>Ian does work on XUL/JS stuff (mainly UI but also some backend) with a
        little bit of simple C++ stuff thrown in. He peer reviews on help and
        has been actively involved in Mozilla development for about two years
        before the SeaMonkey project was started.</dd>

  <dt id="Neil">Neil Rashbrook (Neil) - SeaMonkey code module owner</dt>
    <dd>Neil is the "module owner" of XPFE (most of the SeaMonkey-specific code),
        and a super-reviewer focussed on XPFE and MailNews. He has been very
        involved in all SeaMonkey related development for years.</dd>

  <dt id="Callek">Justin Wood (Callek) - release engineer</dt>
    <dd>Justin has been working on Mozilla since early 2003, he is currently
        the Release Engineer for SeaMonkey. When not doing releases he is also
        working on Build Config and other areas throughout the SeaMonkey Code.</dd>

<h3 id="owners">Project Area Owners and Peers</h3>

The SeaMonkey Project can be divided into several areas, which are listed on
our <a href="dev/project-areas">project areas list</a>. 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.

<h3 id="community">Community</h3>

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

<h2 id="contact">Contact</h2>

For support and help or even development questions, please turn to
<a href="./community">our community</a> 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 <a
href="">support mailing list</a>
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 <a
href="">subscribe to
the list</a>.

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<br>
Please do <strong>not</strong> use the Council address for support requests!

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