Gershom wrote:
> Migrate community — well yes, but… migrate all the logins too?

So by "migrate" you mean building a new VM, rather
than just migrating the current VM to a new container
at a different host.

That's a lot more work, but I agree. The current c.h.o. VM
is still running Debian Lenny, which is long, long past EOL
and hasn't received any security updates for over 2 years.

> Kill rt.h.o in favor of phab — absolutely!
> But it still is used as part of the community.haskell.org process,
> and tickets are still created on it to manage those accounts.
> So we can always redirect [email protected]
> emails to create phab tickets, etc, but we must make sure
> that we set all the bits up to do so.

The web pages to request a new account or
project are simple CGI scripts written in Haskell. Their source
code can be found in ~admin/scripts on c.h.o. These scripts
create RT tickets by running the rt command, so just
redirecting an email address to phab won't be enough.

One other hidden maintenance burden on c.h.o. that I'd
like to point out: We are currently running an exim mail
server on c.h.o., backed by the clamav spam filter.
(The spam filter is way, way out of date; we can't get
updates anymore because of being stuck on Lenny.)
Nowadays, the maintenance burden for running an email
server is far higher than it was once, so it would be great
if we could avoid that. AFAIK the mail server supports the
following services:

1. Mailman mailing lists for projects
2. RT
3. c.h.o. email address for users that forward to their
real email addresses

#1 is similar to Trac - few if any projects are actually
using this service now. To shut it down, we would first
need to find out for sure who is still using it and migrate
them to something else.

#2 we discussed. #3 is probably not being used by
anyone anymore, but it would be easy enough to
grandfather forwarding for existing accounts via
some other email server.

> Also don’t forget that many www.haskell.org
> subdirectories continue to correspond to plain
> old websites and not wiki pages.

I don't think Gershom's list is complete. We really
really need an official complete list of those. Last
time haskell.org was migrated, for at least a year
afterwards there was an occasional scream of
pain by the owner of one of those sites. Some
of them were people whose complaints could
not be ignored, no matter how public and
explicit the warnings were before the migration.

Thanks,
Yitz
_______________________________________________
haskell-infrastructure mailing list
[email protected]
http://community.galois.com/mailman/listinfo/haskell-infrastructure

Reply via email to