git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, philipoakley@iee.org,
	jrnieder@gmail.com, avarab@gmail.com
Subject: Re: [PATCH v2] Configure Git contribution guidelines for github.com
Date: Tue, 13 Jun 2017 05:04:27 -0400	[thread overview]
Message-ID: <20170613090427.igjz7erniblh3wie@sigill.intra.peff.net> (raw)
In-Reply-To: <20170613081807.33196-1-larsxschneider@gmail.com>

On Tue, Jun 13, 2017 at 10:18:07AM +0200, Lars Schneider wrote:

> changes since v1:
> * mention submitGit
> * link to mailing list address instead of mailing list archive

You might want to link to https://git-scm.com/community/, which has a
section on the mailing list at the top. It gives the list address but
also talks about the archive, that you can send to it without
subscribing, etc.

> * reformat long lines

I think this is OK. For CONTRIBUTING.md, GitHub re-wraps. In the pull
request template itself, though, the newlines become hard-wraps. But we
wouldn't generally expect those lines to remain in the final PR text
anyway, so it shouldn't really matter.

That's actually one annoyance I have with PR and issue templates like
this: the submitter has to manually delete them. But there's not really
a better way to get people's attention. The link to CONTRIBUTING is by
far not enough in my experience (I had to put a template in
git/git-scm.com for people to top submitting Git bugs).

The text itself looks good, but two minor grammar nits:

> diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
> new file mode 100644
> index 0000000000..fc397bb8fc
> --- /dev/null
> +++ b/.github/CONTRIBUTING.md
> @@ -0,0 +1,19 @@
> +## Contributing to Git
> +
> +Thanks for taking the time to contribute to Git! Please be advised, that the
> +Git community does not use github.com for their contributions. Instead, we use
> +a mailing list (git@vger.kernel.org) for code submissions, code
> +reviews, and bug reports.

I think the comma after "advised" is unnecessary (you could also drop
"that" to turn the first part into an introductory clause, but I think
it reads better with as "Please be advised that").

> diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
> new file mode 100644
> index 0000000000..2b617f4c25
> --- /dev/null
> +++ b/.github/PULL_REQUEST_TEMPLATE.md
> @@ -0,0 +1,7 @@
> +Thanks for taking the time to contribute to Git! Please be advised, that the

Ditto here.

-Peff

  reply	other threads:[~2017-06-13  9:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  8:18 [PATCH v2] Configure Git contribution guidelines for github.com Lars Schneider
2017-06-13  9:04 ` Jeff King [this message]
2017-06-14  7:28   ` Lars Schneider
2017-06-14 10:01     ` Junio C Hamano
2017-06-14 10:23       ` Lars Schneider

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170613090427.igjz7erniblh3wie@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=larsxschneider@gmail.com \
    --cc=philipoakley@iee.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).