unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Michael Fischer <mfischer@zendesk.com>
Cc: "Eric Wong" <e@80x24.org>,
	"Jérémy Lecour" <jeremy.lecour@gmail.com>,
	"Liste Unicorn" <mongrel-unicorn@rubyforge.org>,
	unicorn-public@bogomips.org
Subject: Re: [ANN] unicorn 4.8.3 - the end of an era
Date: Wed, 7 May 2014 21:25:23 +0000	[thread overview]
Message-ID: <20140507212523.GA22785@dcvr.yhbt.net> (raw)
In-Reply-To: <CABHxtY6CYM5+tTsLmiNSK=_EAbKjoqmapJWb92=4-SHN1FLg-Q@mail.gmail.com>

Michael Fischer <mfischer@zendesk.com> wrote:
> Is there some compelling reason why the mailing list simply cannot be
> moved to another provider?  IMHO your users and fellow developers
> shouldn't have to do anything other than change the submission
> address.

We would need to migrate again if/when that provider goes dead or
service starts deteriorating.  Ease-of-migration and being forkable
again in the future was the top priority.

If I'm hit by a bus or start allowing too much spam, it should be
trivially easy to migrate the project[1] and all its archives and
infrastructure.

> I respect your desire to power the communication platform with free
> software (and I'm sure this can still be done with Mailman or
> whatever), but keep in mind the practical reality of our time, where
> most of us these days are now comfortably using Webmail or or POP/IMAP
> against a remote server that's not under the user's control and have
> no desire to implement yet another communication conduit.

I will probably take the addresses of active subscribers who've posted
here[2] imported into the new delivery system, even.

It would be great to be able to make the list of ML subscribers public,
too, to ensure forkability.  I'm not sure how the lurkers will react to
that, though...


[1] of course, whoever takes over may not be a Free Software zealot
    like myself.
[2] those addresses are already public, but lurkers will probably
    have to resubscribe (or use ssoma or the Atom feed).

  reply	other threads:[~2014-05-07 21:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  8:05 [ANN] unicorn 4.8.3 - the end of an era Eric Wong
2014-05-07  9:30 ` Jérémy Lecour
2014-05-07  9:46   ` Eric Wong
2014-05-07 10:16     ` Lin Jen-Shin (godfat)
2014-05-07 10:52       ` Alejandro Riera
2014-05-07 19:54         ` handling SMTP subscribers to public-inboxen Eric Wong
2014-05-07 20:33     ` [ANN] unicorn 4.8.3 - the end of an era Michael Fischer
2014-05-07 21:25       ` Eric Wong [this message]
2014-05-07 12:08 ` Bráulio Bhavamitra
2014-05-07 20:25   ` Xavier Noria
2014-05-07 20:34     ` Eric Wong
2014-05-07 20:37       ` Xavier Noria

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140507212523.GA22785@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=jeremy.lecour@gmail.com \
    --cc=mfischer@zendesk.com \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=unicorn-public@bogomips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).