I have essentially no software background except doing some maintenance
coding in PL/M and 8080 assembler.
I spent decades in support related functions -- QA/QC, engineering, and
end-user.
I date back to Netscape Navigator.

My path to participation would be documentation related.
Searching for "getting involved in SeaMonkey leads to
https://www.seamonkey-project.org/dev/get-involved .
It explicitly states "All *software errors* in our application should
get reported in the Bugzilla database." [emphasis added ;]

There's is a section on *writing* documentation. No *PROOFREADING*!
To make matters worse, it has a link to creating good HTML but no
guidance on writer asking self "What does user need/want to know".

How do I help?
The problems I'm finding are errors of "omission" not "commission".

Richard Owlett wrote:
> I have essentially no software background except doing some maintenance coding
> in PL/M and 8080 assembler.
> I spent decades in support related functions -- QA/QC, engineering, and end-user.
> I date back to Netscape Navigator.
>
> My path to participation would be documentation related.
> Searching for "getting involved in SeaMonkey leads to
>   https://www.seamonkey-project.org/dev/get-involved .
> It explicitly states "All *software errors* in our application should get
> reported in the Bugzilla database." [emphasis added ;]
>
> There's is a section on *writing* documentation. No *PROOFREADING*!
> To make matters worse, it has a link to creating good HTML but no guidance on
> writer asking self "What does user need/want to know".
>
> How do I help?
> The problems I'm finding are errors of "omission" not "commission".
>

The website code is in:

https://gitlab.com/seamonkey-project/website

and mirrored in

https://hg.mozilla.org/SeaMonkey/seamonkey-project-org/file/tip

If you find and error or want something changed file a bug in bugzilla against
SeaMonkeys website component:

https://bugzilla.mozilla.org/show_bug.cgi?id=1853566

This needs a patch for checkin but we can take a complete file with changes
too and do the patch ourselves. If you have something you would like to be
checked in it needs to be reviewed. I or IanN usually do this so set us at
least in cc if you have a changed file.

If you just report an error or outdated documentation there are plenty of
these and few of us who do the actual work so it will take time to be fixed. I
do it now and then only and mostly in the release notes.

FRG