git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: git@vger.kernel.org
Cc: Emily Shaffer <emilyshaffer@google.com>,
	Denton Liu <liu.denton@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>, Eric Wong <e@80x24.org>,
	Kerry@google.com, Richard <richard.kerry@atos.net>
Subject: [PATCH v3] MyFirstContribution: add avenues for getting help
Date: Thu, 12 Dec 2019 17:31:28 -0800	[thread overview]
Message-ID: <20191213013128.6268-1-emilyshaffer@google.com> (raw)
In-Reply-To: <20191115230637.76877-1-emilyshaffer@google.com>

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

Since #git-devel's traffic is fairly low, it should be OK to direct some
questions there too. 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.

Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
---
Since v2:

- Removed a double slash in a URL
- public-inbox -> lore.kernel.org
- Removed indication that Git list should be a fallback; instead, treat
  it as equally useful for first attempt at Q&A.

As for the conversation which spun off regarding the access controls on
git-mentoring list, since the list still hasn't seen traffic, I'm going
to keep them as they are for a little longer.

 - Emily

 Documentation/MyFirstContribution.txt | 32 +++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/Documentation/MyFirstContribution.txt b/Documentation/MyFirstContribution.txt
index 35b9130aa3..e7489d156a 100644
--- a/Documentation/MyFirstContribution.txt
+++ b/Documentation/MyFirstContribution.txt
@@ -23,6 +23,38 @@ useful additional context:
 - `Documentation/SubmittingPatches`
 - `Documentation/howto/new-command.txt`
 
+[[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.
+
+==== 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.
+
+==== https://lore.kernel.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. 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.
+
 [[getting-started]]
 == Getting Started
 
-- 
2.24.1.735.g03f4e72817-goog


  parent reply	other threads:[~2019-12-13  1:31 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   ` Emily Shaffer [this message]
2019-12-13  3:00     ` [PATCH v3] " 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=20191213013128.6268-1-emilyshaffer@google.com \
    --to=emilyshaffer@google.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Kerry@google.com \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=liu.denton@gmail.com \
    --cc=richard.kerry@atos.net \
    /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).