bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Shutting down some Hurd mailing lists? (was: News 2009-08-31, documenta


From: Thomas Schwinge
Subject: Shutting down some Hurd mailing lists? (was: News 2009-08-31, documentation, wiki)
Date: Tue, 29 Sep 2009 21:32:51 +0200
User-agent: Mutt/1.5.11

Hello!

This was about off-topic discussions on bug-hurd.

On Tue, Sep 29, 2009 at 08:27:37AM +0200, Arne Babenhauserheide wrote:
> Am Montag, 28. September 2009 10:16:29 schrieb Thomas Schwinge:
> > A bit of off-topicness is always
> > needed and tolerable, but you have to know when to stop.  Else, we might
> > think about setting up a hurd-chatter mailing list?
> 
> I fear that that list would just be quite dead soon - and once we'd need it 
> again, we'd have forgotten about it... just taking the part of the discussion 
> offlist is much easier. 
> 
> And adding another list will make the Hurd lists less accessible. 

Which brings us (back?) to another topic: should we shut down some Hurd
mailing lists?  web-hurd and hurd-devel aren't being used at all;
help-hurd hardly so; what about l4-hurd?  I'd say:

  * web-hurd: totally unused, so shut down.  Make the address forward to
    bug-hurd.

  * hurd-devel: unused, so shut down.  Forward to bug-hurd.  Rationale:
    discussions amongst developers are held in public (where everyone can
    participate), they usually originate on bug-hurd or l4-hurd,
    participating people are kept in CC.

  * help-hurd: mostly unused, shut down.  Forward to bug-hurd.
    Rationale: people seeking help about using the Hurd end up on the
    debian-hurd mailing list in the vast majority of cases, all others
    can be served on bug-hurd (they are to be CCed when answering, so
    they need not even be subscribed).

  * l4-hurd: unsed in bursts.  Keep it running.  Rationale: its audience
    is quite different from the bug-hurd one, as is (at least partly) the
    area of subjects being discussed.

Opinions?


Regards,
 Thomas

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]