Fwd: Re: DocBook VM

[Bob Stayton <bobs@sagehill.net>]

I'm forwarding some mails for comment from Stefan Seefeld, who is 
working on the XSL build system on Github.  He is suggesting 
consolidating the 3 docbook mailing lists into the docbook.org domain 
and using a Rackspace VM as host.  We would be moving docbook and 
docbook-apps from OASIS, and docbook-developers from SourceForge. 
Please read the two messages below and let us know your concerns and 
suggestions.

Bob

On 12/15/2016 5:35 AM, Stefan Seefeld wrote:
> Hi David, Bob,
>
> a few months ago we talked about DocBook infrastructure, notably the
> rackspace VM (?) we used to use for CI and release preparation. Since
> all of this is nowadays covered by github / travis-ci, we should
> reconsider what we need. Our last tie to sourceforge.net now is the
> developers' mailing list. I wonder whether we could migrate that to the
> above VM. In particular, I was wondering whether it would be possible
> (and useful) to add a subdomain 'mail.docbook.org', combined with an MX
> record for mails to @docbook.org, which would allow us to use
> [developers, docbook, docbook-apps]@docbook.org and possibly others.
>
> If OASIS is willing to support us we could collocate the developers'
> list with the docbook and docbook-apps lists, otherwise we could use the
> rackspace VM for that. But as with cdn.docbook.org, I'd prefer hiding
> the details behind a proper DNS alias (subdomain / MX record), if
> possible, so users don't have to be aware of such migrations in the 
future).
>
> What do you think ?
>
>         Stefan
>

-------- Forwarded Message --------
Subject: Re: DocBook VM
Date: Thu, 15 Dec 2016 13:36:57 -0500
From: Stefan Seefeld <stefan@seefeld.name>
To: David Cramer <david@thingbag.net>, Bob Stayton <bobs@sagehill.net>

On 15.12.2016 12:04, David Cramer wrote:
> Providing a VM from that Rackspace account is no problem if that's the
> direction we go.

OK, so there are three (potential) options to consider.

1) migrate all lists to OASIS
2) migrate all lists to a Rackspace VM
3) don't change anything, i.e. keep two lists on OASIS, and one on sf.net

The one reason speaking against 1) and 2) is that any change a) requires
work and b) affects users.
The benefits I expect from a move are:

  * no more dependency on sf.net
  * a cleaner interface (using docbook.org to hide technical details
such as ISPs etc.)
  * better control over list and subscription attributes (when using
mailman)
  * the ability to add more lists if we want them

Note that all of these points are "nice to have" only. There is no
urgent need to act, I'm just a bit in a "cleanup" mood right now.
If you think this is a bad idea, I'll be quiet. :-)

        Stefan

--

      ...ich hab' noch einen Koffer in Berlin...