SpamAssassin Infrastructure Notes
This section of the wiki is intended to hold notes on SpamAssassin's infrastructure – mailing lists, svn, where to ask about getting stuff fixed, etc. The intended audience is the SpamAssassin committers. Hopefully most of this page will be simply links to pages in http://www.apache.org/dev/ , rather than duplicating too much of that site.
Reporting failures
http://issues.apache.org/jira/ is the bug-tracker used to report and track ASF infrastructure issues. There's no need to report anything if http://monitoring.apache.org/status/ lists it as failed, btw.
In some cases, you can also mail infrastructure /at/ apache.org
. there's a batch of mailing lists for ASF infrastructure management, see http://www.apache.org/dev/infra-mail.html .
Machines we use
http://www.apache.org/dev/machines.html lists the ASF's machines. We use:
minotaur: for publishing releases according to build/README (in svn); spamassassin.apache.org static content
Accounts for minotaur are for committers only – requested via the PMC chair.
spamassassin.zones.apache.org: a Solaris Zone running on helios.apache.org, running these services: buildbot, rsync, automc
Accounts for the zone are for committers only – requested via the PMC.
Creating accounts, granting karma, etc
Account creation is detailed in the PMC FAQ: http://www.apache.org/dev/pmc.html
Account karma can be granted by the PMC Chair: InfraNotes GrantingKarma
PMC people: http://www.apache.org/dev/solaris-zones.html explains how to create an acct in the zone.
Things to do if you're a new committer in SpamAssassin
an ASF guide doc: http://www.apache.org/dev/new-committers-guide.html
set up SSH access to minotaur: http://www.apache.org/dev/user-ssh.html
Creating rsync accounts: RsyncConfig
Mailing lists
We have several; not sure what machine they're hosted on. If you're a committer, and feel like it, it'd be great if you could help out with moderation – it's just a matter of bouncing spam that's being sent to the lists, bouncing mails being sent to the announce list, and approving people who aren't spammers for the other lists.
Administration and moderation is discussed in http://www.apache.org/dev/committers.html#mail-moderate ; this seems to be mostly up to date.
More details are at http://www.apache.org/foundation/mailinglists.html .
Note that in general, if an ASF list is for committers or members only (a few are), you need to use your @apache.org address to subscribe, it seems.
The ASF run a (very basic) archive of all the lists at http://mail-archives.apache.org/mod_mbox/ . There's also something called eyebrowse; don't use it, it's borked.
The web site
The master copy of the spamassassin.apache.org static content is on minotaur at /www/spamassassin.apache.org
. It's built with webmake, which is a simple perl website building tool. The source file is called 'main.wmk'. To run webmake on minotaur, read build/README
in svn, that tells you how to set up your path to use the installed copy of webmake in jm's home dir.
Ensure your umask is set to 002 before writing to files here – this is VERY important! We don't have root here, and screwups have to be fixed by someone on the infrastructure team who does.
Note that the static content is hosted in SVN at https://svn.apache.org/repos/asf/spamassassin/site/ . If you make any changes on minotaur, be sure to check them in – you may have to copy the changed files from the checkout there into your own checkout, btw, to be able to authenticate correctly to the svn server; or better, do the change in your own checkout first, and simply 'svn up' on minotaur.
There's a couple of mirrors for the main ASF sites, separate from the massive set of download mirrors. Files written to /www/spamassassin.apache.org
aren't visible until the mirrors update, every 2 hours or so. However, if you set the HTTP proxy setting to point to 209.237.227.195 port 80, it'll work in your browser for previewing.
Alternatively, you also have a public HTML dir on minotaur – it's at http://people.apache.org/~yourusername/ , e.g. http://people.apache.org/~jm/ . This is not mirrored, and files placed in minotaur:~/public_html will be visible there immediately. This is good for publishing prereleases and alphas.
The ASF download mirrors
The download mirrors are used specifically to mirror the /dist/ portion of the website; there's not much need to discuss that here, as there's very strict rules on what files can be published there, and their layout, and it's covered in build/README.
It is worth noting in passing though that despite what it says in http://www.apache.org/dev/mirrors.html and http://www.apache.org/dev/mirror-guide-bodewig.html , symbolic links will NOT work in that part of the site on certain mirrors! This has bitten us before. see http://issues.apache.org/jira/browse/INFRA-184
Your apache.org email address
You have a .forward file as discussed at http://www.apache.org/dev/services.html . SSH in and set it up!
Using the Zone
spamassassin.zones.apache.org: see http://www.apache.org/dev/solaris-zones.html .
BuildBot
when creating slaves on the Solaris zone, you cannot use "buildbot slave" to create it due to a bug in use of ptys; instead:
PASSWORD=slavepassword NAME=slavename mkdir /home/bbmass/slaves/$NAME chdir /home/bbmass/slaves/$NAME mktap buildbot slave --basedir /home/buildbot/slaves/$NAME \ --master buildbot.spamassassin.org:9989 --name $NAME \ --passwd $PASSWORD --usepty=0
Bugzilla
Is hosted off-ASF, with sonic.net, at the moment – this is supposed to change sometime soon, but Theo the bz wizard is busy.