git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v1] Configure Git contribution guidelines for github.com

From
Lars Schneider <larsxschneider@gmail.com>
Date
Jun 13, 2017, 07:48 UTC
Message-ID
<A712386E-0C4B-4A6C-B231-EA52FA285F34@gmail.com>
In-Reply-To
<31A456B20D984421AA958A39B2FCD29D@PhilipOakley>
Show 27 quoted lines
> On 10 Jun 2017, at 14:48, Philip Oakley <philipoakley@iee.org> wrote:
> 
> From: "Lars Schneider" <larsxschneider@gmail.com>
>> 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/
>> 
>> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
>> ---
> 
> I see there are currently 84 open PRs (13 in the last 14 days), so it is real.
> 
> I also see that the Issues page for git.git appears to be disabled, and will redirect to the pulls page.
> 
> Maybe the instructions should also be part of an Issues template which could reduce the potential number of PRs being created (but could create its own problems)
I don't think that is necessary as Issues are disabled for this repo.
>> ...
>> +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](http://public-inbox.org/git/) for code submissions, code reviews, and bug reports.
> 
> Isn't the mailing list git@vger.kernel.org, with an archive at http://public-inbox.org/git/ ?
Agreed!
Show 5 quoted lines
> 
>> +
>> +Please [read the maintainer notes](http://repo.or.cz/w/git.git?a=blob_plain;f=MaintNotes;hb=todo) to learn how the Git
> 
> Is using the repo.or.cz address deliberate as a way of highlighting that Github isn't the centre of the universe when accessing a DVCS repo?
Haha, partly yes. Plus, I wasn't able to figure out quickly how to access the todo blob on GitHub. 
> Maybe the kernel.org repo should be first, or at least the alt-git.git repo at repo.or.cz listed in those same notes.
Agreed!
> It's still a good idea though.
Thanks :)
- Lars
Previous: Junio C Hamano
Message 17 of 17 in “Configure Git contribution guidelines for github.com”
  1. Configure Git contribution guidelines for github.comLars Schneider, Jun 9, 2017
  2. Ævar Arnfjörð BjarmasonJun 9, 2017
  3. Lars SchneiderJun 9, 2017
  4. Junio C HamanoJun 10, 2017
  5. Jonathan NiederJun 9, 2017
  6. Junio C HamanoJun 10, 2017
  7. Lars SchneiderJun 13, 2017
  8. Jeff KingJun 10, 2017
  9. Lars SchneiderJun 13, 2017
  10. Philip OakleyJun 10, 2017
  11. Junio C HamanoJun 12, 2017
  12. Lars SchneiderJun 13, 2017
  13. Ævar Arnfjörð BjarmasonJun 15, 2017
  14. Junio C HamanoJun 15, 2017
  15. Andreas HeidukJun 15, 2017
  16. Junio C HamanoJun 15, 2017
  17. Lars SchneiderJun 13, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.