unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Alexandrov <321942@gmail.com>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: moderation, please
Date: Sun, 13 Oct 2019 14:12:07 +0300	[thread overview]
Message-ID: <36fwq4qg.321942@gmail.com> (raw)
In-Reply-To: <dcc5e6b6158149f7762a4643d4f415e31e101495.camel@gmail.com> (Jesse Gibbons's message of "Sat, 12 Oct 2019 16:16:39 -0600")

[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]

Jesse Gibbons <jgibbons2357@gmail.com> wrote:
> On Sun, 2019-10-13 at 00:04 +0300, Dmitry Alexandrov wrote:
>> ng0 <ng0@n0.is> wrote:
>> > this list is to discuss the _development_ of GNU Guix, Shepherd, and Guix System.
>> > 
>> > It is not a general discussion list for everything else.
>> > 
>> > While we usually get by fine without imposing moderation restrictions, I don't see how any of the recent message floods have been ontopic to this list
>> 
>> Yes, indeed, though I cannot imagine, how an offtopic limited to few threads can hurt any person minimally capable of using a MUA.
>> 
>> > (other than the original announcement of the blog post
>> 
>> Indeed?
>> 
>> > If it isn't already on moderation for some people, it would be very kind to do so as numerous active people asked for this (and the people in question are on record not willing to stop the messages).
>> 
>> Anyway, ‘to stop’ is the most unconstructive proposal, it never works.  If you can name a better mailing list, please do so.  E. g., @ams@gnu.org believes for some reason, than otherwise pretty dead gnu-system- discuss@gnu.org is not suitable for discussion of the future of GNU system in the light of recent events either.
>
> Try moving it to irc or matrix. There should already be plenty of rooms related to the future of the GNU project on freenode, or you could start something new.

Why do you suggest changing a communication format for no reason?  I believe, if people choose a long and measured format of mailing list, they do it on purpose, not because they are not aware of existence of IRC channels.

> When all 50+ new messages in this list from the past hour are off-topic, it is too much.

Do not read them.  I am not a user of Evolution, just specifically checked it up for you, but it seems that this should do the trick: Context menu / ‘Ignore thread’.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2019-10-13 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 18:00 moderation, please ng0
2019-10-12 21:04 ` Dmitry Alexandrov
2019-10-12 22:16   ` Jesse Gibbons
2019-10-12 22:32     ` František Kučera
2019-10-12 23:31       ` Jesse Gibbons
2019-10-13 11:22         ` Enough Ricardo Wurmus
2019-10-13 11:12     ` Dmitry Alexandrov [this message]
2019-10-13 10:27 ` moderation, please ng0

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=36fwq4qg.321942@gmail.com \
    --to=321942@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jgibbons2357@gmail.com \
    /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://git.savannah.gnu.org/cgit/guix.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).