git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: emilyshaffer@google.com
Cc: git@vger.kernel.org, Denton Liu <liu.denton@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Eric Wong <e@80x24.org>, Richard Kerry <richard.kerry@atos.net>,
	Derrick Stolee <stolee@gmail.com>
Subject: Re: [PATCH v5] MyFirstContribution: add avenues for getting help
Date: Fri, 24 Jan 2020 12:35:28 -0800	[thread overview]
Message-ID: <xmqq7e1gzj73.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20200124200915.249473-1-emilyshaffer@google.com> (emilyshaffer@google.com's message of "Fri, 24 Jan 2020 12:09:16 -0800")

emilyshaffer@google.com writes:

> From: Emily Shaffer <emilyshaffer@google.com>

Hmm, unlike folks who use GGG, your From: address seem almost usable
without having to waste two extra lines (which matters when one has
to review many patches a day).

> With https://lore.kernel.org/git/20191114194708.GD60198@google.com/ we
> now have a mentoring mailing list, to which we should direct new
> contributors who have questions.

Yay.

> Mention #git-devel, which is targeted for Git contributors; asking for
> help with getting a first contribution together is on-topic for that
> channel. Also mention some of the conventions in case folks are
> unfamiliar with IRC.
>
> Because the mentoring list and #git-devel are both a subset of Git
> contributors, finally list the main Git list and mention some of the
> posting conventions.

> +[[getting-help]]
> +=== Getting Help
> +
> +If you get stuck, you can seek help in the following places.
> +
> +==== https://groups.google.com/forum/#!forum/git-mentoring[git-mentoring@googlegroups.com]
> +
> +This mailing list is targeted to new contributors and is a great place to post
> +questions and receive kind, detailed answers from volunteers on the Git
> +project. You must join the group to view messages or post.

OK.


> +==== https://webchat.freenode.net/#git-devel[#git-devel] on Freenode
> +
> +This IRC channel is for conversations between Git contributors. If someone is
> +currently online and knows the answer to your question, you can receive help
> +in real time. Otherwise, you can read the
> +https://colabti.org/irclogger/irclogger_logs/git-devel[scrollback] to see
> +whether someone answered you. IRC does not allow offline private messaging, so
> +if you try to private message someone and then log out of IRC, they cannot
> +respond to you. It's better to ask your questions in the channel so that you
> +can be answered if you disconnect and so that others can learn from the
> +conversation.

OK.

> +==== https://lore.kernel.org/git[git@vger.kernel.org]

Hmph.  I would have expected mailto:git@vger.kernel.org as the main
URL here, as this enumeration is not for those who lurk to passibly
receive information, but for those (new) contributors who want to
ask help by actively transmitting.  Mentioning lore as an archive
when talking about the list is necessary, but it shouldn't obscure
the main e-mail address people need to know in order to send their
requests.

> +
> +This is the main Git project mailing list where code reviews, version
> +announcements, design discussions, and more take place. 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.

Thanks.

  reply	other threads:[~2020-01-24 20:36 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
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 [this message]
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=xmqq7e1gzj73.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=e@80x24.org \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=liu.denton@gmail.com \
    --cc=richard.kerry@atos.net \
    --cc=stolee@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).