Re: your mail
- From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
- Date
- Jun 22, 2017, 21:58 UTC
- Message-ID
- <878tkjk7m7.fsf@gmail.com>
- In-Reply-To
- <xmqq8tkjiu3d.fsf@gitster.mtv.corp.google.com>
On Thu, Jun 22 2017, Junio C. Hamano jotted:
Show 49 quoted lines
> Simon Ruderich <simon@ruderich.org> writes: > >> On Thu, Jun 22, 2017 at 01:55:27PM +0000, Patrick Lehmann wrote: >>> The description on https://github.com/git/git doesn't reflect that policy. >>> >>> a) >>> It explains that discussions take place in the mentioned mailing list. >>> b) >>> It describes how to subscribe. >> >> However it doesn't say that you have to subscribe to send, only >> how to subscribe. > > For that matter, we also say "everyone is welcome to post", which > makes it clear that no subscription is required. > > But I view these merely being technically correct. And making it > absolutely obvious does not cost too much. > >>> With knowledge of other mailing lists (mostly managed by mailman), >>> subscription is required for participation. >> >> That depends on the mailing list, some require subscription to >> prevent spams but not all do. > > Yes. But not many people realize that the world they know is the > only world. We are used to an open list and are shocked when we > encouter a closed one; let's not forget that shock. > > How about doing it like this? > > README.md | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/README.md b/README.md > index f17af66a97..bbaf54bffb 100644 > --- a/README.md > +++ b/README.md > @@ -31,6 +31,10 @@ The user discussion and development of Git take place on the Git > mailing list -- everyone is welcome to post bug reports, feature > requests, comments and patches to git@vger.kernel.org (read > [Documentation/SubmittingPatches][] for instructions on patch submission). > + > +You can send messages without subscribing to the list, but it is > +recommended to read what other people are saying on the list before > +you speak. > To subscribe to the list, send an email with just "subscribe git" in > the body to majordomo@vger.kernel.org. The mailing list archives are > available at <https://public-inbox.org/git/>,
It's unclear what that means. I *think* it means "consider taking a look around the list before you post", but then it's probably better advice to tell people to skim the archives first to get an idea of the traffic.
E.g. if I page through the first 2 pages of public-inbox.org I get messages going back to the 19th, but if I were to subscribe to the list I'd need to wait 4 days to get the same mail.
Which, in the context of what this follows (how to submit a bug, questions etc.) isn't a good use of time for the person reading the instructions.
Maybe something more like:
diff --git a/README.md b/README.md index f17af66a97..dc175757fa 100644 --- a/README.md +++ b/README.md @@ -36,6 +36,12 @@ the body to majordomo@vger.kernel.org. The mailing list archives are available at <https://public-inbox.org/git/>, <http://marc.info/?l=git> and other archival sites. +You don't need to be subscribed to the list to send mail to it, and +others on-list will generally CC you when replying (although some +forget this). It's adviced to subscribe to the list if you want to be +sure you're not missing follow-up discussion, or if your interest in +the project is wider than a one-off bug report, question or patch. + The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for