SeaMonkey Internet Suite

Unofficial News in English language


What about contributing to the SeaMonkey Project⁉


it’s not a secret that SeaMonkey-development is understaffed. At the right you see 2 statistic charts:

Totally 20 bugfixes / month, that is much better than (for example) at the AOo project with only 5 bugfixes each month, but much worse than in the LibreOffice project with: 545 bugfixes within 1/4 year — and see the colorful “pie“. Of course a pointless comparison, but it demonstrates the critical situation for the SeaMonkey project with very few developers.

But may be there are people with basic (or even good) bug fixing skills, who only shied from the many obstacles before they can start? Some of them can be surmounted easil:

But the next steps are much more difficult:

  • Install Mercurial, do some first steps
    Thinking about this until now my inner temptation became too strong, though there are lots of [good first bug] bugs, which should not need too much knowledge to fix them. And it would be not big, but visible progress if me and others could fix some of the bugs I find immediately. But for reaching this goal we would need a team of beginners who help each other to overcome obstacles which will appear during the beginning phase. We could start with some bugs in SeaMonkey Help and dare more demanding challenges step by step.
  • Do some first fixes
  • upload them for review

I think interested volunteers should fix a weekend with some kind of time table where they do these first steps together, help each other, might even get help of a mentor form the SeaMonkey Developers Team … .

May be we even can get some external volunteers from Hackerearth, CodeChef, TopCoder,Codeforces,HackerRank or similar communities (may be you know a better community were we can try to recruit volunteers?)? Or, if we are lucky, some “self compiling users” are willing to provide their knowledge to the SeaMonkey project?

If you have some own thoughts, please add a comment as reply to one of the threads:

  • “… – I am interested in participating”
    (only a short comment, 1 … 2 sentences concerning your background, no discussion)
  • “… – No, thanks
    (only a short comment concerning your reasons, no discussion)
  • “… general discussion
    (Ideas, criticism, anything else …)





Leave a comment

Add-On “PrefBar” crashes SeaMonkey 2.52 ⚠️️

One of my favorite add-ons crashes latest SeaMonkey Trunk-Builds like

UNofficial (by FRG) en-US SeaMonkey 2.52a1 (NT 6.1; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0 Build 20170513191754 (Default Classic Theme) on German WIN7 64bit

When I launch SeaMonkey it crashes immediately if PrefBar add-on is active.

The problem is not Win64; x64 related.


Can someone confirm the problem❔

Any theory concerning the roots of the problem❔


SeaMonkey Project – calling for volunteers

Blogpost in englischer SpracheThe SeaMonkey project is entirely driven by volunteers, and we will need some  more of them, as FRG (Frank-Rainer Grahl)  told on mozillazine.

With some HTML and XHTML knowledge (and some endurance, of course)  for example you can do substantial contribution to SeaMonkey Help. Also required: Translation to other languages than English for Help-chapters, Add-Ons, Wiki-pages

Don’t be shy, leave a comment how we can reach you and where you see your skills for contribution.

Leave a comment


Zur Mozilla-Bugzilla Homepage I still report new bugs I find with status UNCONFIRMED, even if (after careful investigation) I am pretty sure that the report is concerning a real bug and complete enough so that a developer can take on. Reason is that I believe in the two-man rule. Often a review by an other user adds information, may be concerning additionally affected Operating System or an aspect of the problem not yet mentioned or something else. But in the SeaMonkey project, due to very limit “human QA resources” and the lack of interest of most SeaMonkey users to contribute to the project, the bug review process  is horrible slow, even Bug reports what can be reproduced easily do not find a user who is willing to do a test whether he can reproduce the problem.

SeaMonkey needs you

So in future I myself will change bug status to NEW after 2 weeks (or so) of waiting if I think that all requirements for starting bug fixing process are fulfilled and nobody confirmed the bug. But, of course, it would be great if YOUR help would make superfluous this proceeding with my own “confirmation”. Be courageous and grasp the nettle of confirming some [easyconfirm] bugs.

Leave a comment

Swedish SeaMonkey: localized Help will be replaced by en-US Help

hand-792920_640This blog post in German languageread that the (apparently very outdated) Swedish SeaMonkey Help will be replaced by the en-US-Help starting with SeaMonkey 2.46. I don’t know how the situation is for the very few other Help localizations, and even the en-US-SeaMonkey-Help isn’t in a good shape. Here fortunately we have some progress, some (even new) developers are helping to do some bug fixes. Unfortunately there seems to be more or less no interest at the localization teams to port the fixes to their localizations.

My current appeal: We need some volunteers who will do translations for a new chapter in Composer Help as fixes for  Bug 1247386 SeaMonkey Help composer_help.xhtml: Chapter “Adding Mathematical Formulas to Your Web Page” missing in Localized Composer Help.

What about you?