clogger RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: mailing list migration
Date: Thu, 14 Aug 2014 19:59:28 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Who's on this list?

I'd like to move this to hosting on  I can configure mlmmj
to not require subscription as well as use public-inbox[1] so the
archives are downloadable via git.

I originally liked librelist because of rsyncable archives;
but that doesn't seem to be coming back.  public-inbox means
archives are stored in git (via ssoma[2])

In addition to the mail address change, this means posters must Cc:
everyone, since we no longer count on people being subscribed.
The big upside is drive-by emails become more common

Spam hasn't been a problem on the unicorn mailing list, either,
as public-inbox uses SpamAssassin very effectively.

I will never encourage or rely on proprietary communications platforms
or protocols.  Plain-text email is the lowest common denominator and the
preferred platform of git.git developers.


           reply	other threads:[~2014-08-14 19:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

  List information:

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

  git send-email \ \ \ \
    --subject='Re: mailing list migration' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).