From: "Frank Ch. Eigler" <fche@elastic.org>
To: overseers@sourceware.org
Subject: Re: Closing mailing lists
Date: Sun, 01 Mar 2015 20:11:00 -0000 [thread overview]
Message-ID: <20150301201114.GD115268@elastic.org> (raw)
In-Reply-To: <20150301200031.GA14141@calimero.vinschen.de>
Hi -
On Sun, Mar 01, 2015 at 09:00:31PM +0100, Corinna Vinschen wrote:
> [...]
> > > OK. I don't have any real advice as to policy decisions like the ones
> > > you are asking. What option is best for your community is entirely up
> > > to you and them. (In their shoes, the first thing I'd ask is what's
> > > unsatisfactory about the status quo.)
> >
> > Well, the first three lists I mentioned are pretty much undisputable
> > not required anymore.
(OK, but the status quo may still be fine. Such unused lists don't
consume resources.)
> > Merging the announce lists is also helpful since there's only one list
> > left with all the announcements, rather than two with a somewhat
> > artificial spilt between them.
> >
> > The two problems left are
> >
> > - The cygwin-xfree list probably has its defenders in the community so
> > this may deserve a discussion on the list.
> >
> > - What to do with subscribers of an announce list if its merged into
> > another announce list? Moving the subscribers over or just informing
> > them of the close down? How is that usually handled?
> >
> > It's the latter which would be interesting to know.
You/the community need to decide what you would like to happen and
then let us know.
> Btw., if we close mailing lists, will the archives stay available?
Again, you/the community need to decide what you would like to happen
and then let us know. (IMHO outright deleting a list, together with
its history/archives, would be undesirable.)
- FChE
prev parent reply other threads:[~2015-03-01 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 15:47 Corinna Vinschen
2015-03-01 15:56 ` Frank Ch. Eigler
2015-03-01 16:17 ` Corinna Vinschen
2015-03-01 20:00 ` Corinna Vinschen
2015-03-01 20:11 ` Frank Ch. Eigler [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150301201114.GD115268@elastic.org \
--to=fche@elastic.org \
--cc=overseers@sourceware.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.
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).