public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Warren Young <warren@etr-usa.com>, cygwin@cygwin.com
Subject: Re: Too many mailing lists
Date: Sun, 22 Jun 2014 01:35:00 -0000	[thread overview]
Message-ID: <1434055512.20140622052307@yandex.ru> (raw)
In-Reply-To: <53A4A299.6090508@etr-usa.com>

Greetings, Warren Young!

> The Cygwin project has too many mailing lists.  This causes an 
> unjustifiable amount of friction.

Eh? Wait a second, please. Let me pull my fingers up and count.
So far, barring automatic mailing lists like -announce, we have:
1. cygwin (this exact one)
A common mailing list for all things Cygwin. Frankly, very, VERY few things
are off-topic here. With exception of /X stuff, for which there's a clearly
separated, specific list (who you are, if you did not find it from browsing
the website?), about everything cygwin-related goes here.
2. cygwin-xfree (for all things related to the version of X on Cygwin)
As mentioned above, this is the end point for all things/X that is
Cygwin-related. As vast as it can be, not everyone's interested in intricacies
of setting up and using X environment under Cygwin. I, for one, don't.
3. cygwin-talk (a non-technical barely-cygwin related list)
Smokers' room, if you allow me this association.
4. cygwin-apps (a list for PACKAGE MAINTAINERS)
Clearly labelled, this list is for questions about packaging and distribution
of applications under cygwin banner. Nobody have any interested in it, except
active package maintainers.
5. cygwin-patches
This one's going to be missing as soon as the Cygwin repo is migrated to Git,
IMO.
6. cygwin-developers
I think it's clear from the name. The list for developers of Cygwin itself.
7. cygwin-licensing a list for people who need some lawe.
I have no interest in this kind of questions, but I see them popping around
every now and then. I don't understand them, but it seems, they are rather
important for some people.

> Every time someone says "That's not on topic here, go elsewhere," it can
> easily be read as "Go away." 
Every time I remember a reply similar to this, it was not "go elsewhere", but
rather "go to <insert the name of a specific list>". Which looks far from "go
away", to my untrained eye.
(Of course, I'm not including the results from late... erm... "discussion"...
you know, which one I mean... where it was explicitly stated to "go away", and
explained, why.)

> The Cygwin project should only be pushing away toxic people, and multiple
> mailing lists do not have that happy side effect.

I can only see seven lists, of which one is barely cygwin-related, one is
unrelated, and three are developers-only mailing lists.
What's left? Two lists? Hooray, we have ALOT of two mailing lists, where a
question can misdirect!
/shame


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 22.06.2014, <05:01>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2014-06-22  1:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 21:07 Warren Young
2014-06-20 23:25 ` Steven Penny
2014-06-21 11:52 ` Adam Dinwoodie
2014-06-22 21:22   ` Too many mailing lists(passing the buck) Linda Walsh
2014-06-22 21:38     ` Christopher Faylor
2014-06-23  1:10       ` Larry Hall (Cygwin)
2014-06-23  3:42         ` Christopher Faylor
2014-06-23 17:55   ` Too many mailing lists Warren Young
2014-06-22  1:35 ` Andrey Repin [this message]
2014-06-23 18:45   ` Warren Young
2014-06-23 19:47     ` Cliff Hones
2014-06-25  0:20     ` Andrey Repin
2014-06-23 14:53 ` Eric Blake
2014-06-26  0:54 ` KIMURA Masaru

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=1434055512.20140622052307@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=warren@etr-usa.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.
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).