git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org, peff@peff.net
Subject: Re: [PATCH v1] Configure Git contribution guidelines for github.com
Date: Tue, 13 Jun 2017 09:57:01 +0200	[thread overview]
Message-ID: <C7CB1ED2-D7B0-40D3-A239-893BA444CF63@gmail.com> (raw)
In-Reply-To: <xmqqtw3o4nl8.fsf@gitster.mtv.corp.google.com>


> On 10 Jun 2017, at 03:51, Junio C Hamano <gitster@pobox.com> wrote:
> 
> Jonathan Nieder <jrnieder@gmail.com> writes:
> 
>> Lars Schneider 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.
>> 
>> I think this description could be more focused.  It's also not
>> self-contained --- e.g. the link to stalled pull requests is likely to
>> become stale over time, especially if GitHub gives us a way to disable
>> pull requests for the repository some day.
>> 
>> Could you summarize for me the motivation behind this patch?  Is it to
>> make Git more approachable, to avoid frustrating contributors, etc?
> 
> I wonder if s/stall/stale/ is what Lars meant.

Of course :)

- Lars

  reply	other threads:[~2017-06-13  7:57 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
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 [this message]
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=C7CB1ED2-D7B0-40D3-A239-893BA444CF63@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=peff@peff.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.
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).