From: Lars Schneider <larsxschneider@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Roberto Tyley <roberto.tyley@gmail.com>
Subject: Re: [PATCH v1] Configure Git contribution guidelines for github.com
Date: Fri, 9 Jun 2017 18:29:27 +0200 [thread overview]
Message-ID: <F9939C5D-C710-4788-81A0-4D7958971128@gmail.com> (raw)
In-Reply-To: <CACBZZX7O9DgLGOHKhojZRi7n=j3X0W9B_sRGLi6cBpc74GLyeg@mail.gmail.com>
> On 09 Jun 2017, at 18:18, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>
> On Fri, Jun 9, 2017 at 4:21 PM, Lars Schneider <larsxschneider@gmail.com> wrote:
>> Many open source projects use github.com for their contribution process.
>> Although we mirror the Git core repository to github.com [1] we do not
>> use any other github.com service. This is unknown/unexpected to a
>> number of (potential) contributors and consequently they create Pull
>> Requests against our mirror with their contributions. These Pull
>> Requests become stall [2]. This is frustrating to them as they think we
>> ignore them and it is also unsatisfactory for us as we miss potential
>> code improvements and/or new contributors.
>>
>> GitHub offers a way to notify Pull Request contributors about the
>> contribution guidelines for a project [3]. Let's make use of this!
>>
>> [1] https://github.com/git/git
>> [2] https://github.com/git/git/pulls
>> [3] https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/
>
> It would be good to have some instructions, but instead of warning
> people off we could just point them to submitgit.herokuapp.com
>
> You can submit patches to this list using that, and if someone's
> trying to submit a pull request they might be much happier using that.
Agreed! I wasn't sure if this solution is still active/maintained by Roberto!
- Lars
next prev parent reply other threads:[~2017-06-09 16:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 14:21 [PATCH v1] Configure Git contribution guidelines for github.com Lars Schneider
2017-06-09 16:18 ` Ævar Arnfjörð Bjarmason
2017-06-09 16:29 ` Lars Schneider [this message]
2017-06-10 1:44 ` Junio C Hamano
2017-06-09 17:03 ` Jonathan Nieder
2017-06-10 1:51 ` Junio C Hamano
2017-06-13 7:57 ` Lars Schneider
2017-06-10 7:35 ` Jeff King
2017-06-13 7:51 ` Lars Schneider
2017-06-10 12:48 ` Philip Oakley
2017-06-12 15:52 ` Junio C Hamano
2017-06-13 7:45 ` Lars Schneider
2017-06-15 8:09 ` Ævar Arnfjörð Bjarmason
2017-06-15 16:43 ` Junio C Hamano
2017-06-15 17:31 ` Andreas Heiduk
2017-06-15 17:59 ` Junio C Hamano
2017-06-13 7:48 ` 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=F9939C5D-C710-4788-81A0-4D7958971128@gmail.com \
--to=larsxschneider@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=roberto.tyley@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.
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).