git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Denton Liu <liu.denton@gmail.com>
Subject: Re: [PATCH v2] MyFirstContribution: add avenues for getting help
Date: Tue, 19 Nov 2019 19:49:19 +0100	[thread overview]
Message-ID: <20191119184919.GM23183@szeder.dev> (raw)
In-Reply-To: <20191118214519.GH22855@google.com>

On Mon, Nov 18, 2019 at 01:45:19PM -0800, Emily Shaffer wrote:
> On Sat, Nov 16, 2019 at 12:05:45PM +0900, Junio C Hamano wrote:
> > > +==== https://public-inbox.org/git[git@vger.kernel.org]
> > > +
> > > +This is the main Git project mailing list where code reviews, version
> > > +announcements, design discussions, and more take place. If you fail to receive
> > > +help via the channels above, you can ask your question here. The Git list
> > > +requires plain-text-only emails and prefers inline and bottom-posting when
> > > +replying to mail; you will be CC'd in all replies to you. Optionally, you can
> > > +subscribe to the list by sending an email to majordomo@vger.kernel.org with
> > > +"subscribe git" in the body.
> > 
> > Sounds good; I agree with Denton, especially with the mention of
> > "you must join" on the other mailing list, that it is a good idea to
> > explicitly say that subscription is optional in this entry.
> > 
> > You can ask questions even if you haven't tried other avenues and
> > failed, but this entry makes it sound as if an earlier failure
> > elsewhere is a prerequisite for asking for help here.
> 
> I envision an exchange sort of like this:
> 
> Newbie to git@vger.kernel.org: "I'm having trouble compiling Git and I
> want to write a patch, I'm getting X error"
> 
> Veteran to Newbie, cc git-mentoring, bcc git@vger.kernel.org:
> "Please build with blah flag and paste console output, plus let us know
> system information blah blah blah"

That won't work if the veteran is not registered to the mentoring
list, and we can't assume that the newbie is registered there either.
I don't think that we should send anyone who asked a question here to
somewhere else, especially if that elsewhere requires registration.

> I don't mind the idea of pushing folks to ask on the mentoring list
> first. It's pretty well attended already - just now I count 16 list
> members, a pretty significant majority of which are project veterans. I
> have no problem suggesting newbies ask their questions, which others
> probably had and solved before them, in a space separate from the main
> mailing list.
> 
> Of course if you want to encourage newbies to ask in any of these three
> venues, weighted equally, I can change the language. But suggesting the
> main list as a last resort was intentional.

git@vger is the ultimate source of all wisdom :) and it is openly
accessible for anyone for writing, reading, and searching.  Therefore
these three venues cannot be weighted equally, but git@vger should be
the explicitly preferred venue.  Only if the newbie has some other
preferences should the other two be considered; e.g. if more
interactive, chatty communication is preferred, then try #git-devel.


  parent reply	other threads:[~2019-11-19 18:49 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 21:53 [PATCH] MyFirstContribution: add avenues for getting help Emily Shaffer
2019-11-15 22:05 ` Denton Liu
2019-11-15 23:03   ` Emily Shaffer
2019-11-15 23:06 ` [PATCH v2] " Emily Shaffer
2019-11-15 23:38   ` Johannes Schindelin
2019-11-16  0:09   ` Jonathan Nieder
2019-11-16  3:05   ` Junio C Hamano
2019-11-18 21:45     ` Emily Shaffer
2019-11-19  1:45       ` Junio C Hamano
2019-11-19 18:49       ` SZEDER Gábor [this message]
2019-11-19 21:29         ` Johannes Schindelin
2019-11-19 21:41           ` SZEDER Gábor
2019-11-20  1:50             ` Eric Wong
2019-11-20 11:41             ` Johannes Schindelin
2019-11-20 23:40               ` SZEDER Gábor
2019-11-20 10:45           ` Kerry, Richard
2019-11-20 11:37             ` Junio C Hamano
2019-11-19 18:25   ` SZEDER Gábor
2019-12-13  1:31   ` [PATCH v3] " Emily Shaffer
2019-12-13  3:00     ` Derrick Stolee
2019-12-13  4:14       ` Emily Shaffer
2019-12-13  4:16       ` [PATCH v4] " Emily Shaffer
2019-12-13 17:20     ` [PATCH v3] " Junio C Hamano
2019-12-13 17:49       ` Emily Shaffer
2019-12-13 18:40         ` Junio C Hamano
2020-01-24 20:09     ` [PATCH v5] " emilyshaffer
2020-01-24 20:35       ` Junio C Hamano
2020-01-24 20:50         ` Emily Shaffer
2020-01-24 20:54           ` Emily Shaffer
2020-01-24 21:11           ` Junio C Hamano
2020-01-24 21:01       ` [PATCH v6] " Emily Shaffer
2020-01-24 21:18         ` Junio C Hamano
2020-01-24 21:20           ` Emily Shaffer
2020-01-24 21:26         ` [PATCH v7] " Emily Shaffer
2020-01-24 21:56           ` SZEDER Gábor
2020-01-24 23:44             ` Junio C Hamano
2020-02-06  1:07               ` SZEDER Gábor
2020-02-06 16:33                 ` Junio C Hamano
2020-02-06 19:49                   ` Emily Shaffer
2020-02-06 22:13                     ` Emily Shaffer
2020-02-14  2:03                   ` [PATCH] MyFirstContribution: rephrase contact info Emily Shaffer
2020-02-14  2:10                     ` Jonathan Nieder
2020-02-14 17:36                       ` Junio C Hamano
2020-01-24 22:05           ` [PATCH v7] MyFirstContribution: add avenues for getting help Junio C Hamano

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=20191119184919.GM23183@szeder.dev \
    --to=szeder.dev@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=liu.denton@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.
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 NNTP newsgroup(s).