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

Re: Working with public-inbox.org

From
Jakub Narębski <jnareb@gmail.com>
Date
Aug 28, 2016, 11:41 UTC
Message-ID
<d4c44d3c-7361-2a33-4ae5-03cc45f8a034@gmail.com>
In-Reply-To
<alpine.DEB.2.20.1608281033340.129229@virtualbox>
Hello Johannes,
W dniu 28.08.2016 o 10:36, Johannes Schindelin pisze:
Show 20 quoted lines
> On Sun, 28 Aug 2016, Jakub Narębski wrote:
>> W dniu 25.08.2016 o 14:58, Johannes Schindelin pisze:
>>> On Mon, 22 Aug 2016, Eric Wong wrote:
>>>> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>>>>
>>>>> I just want developers who are already familiar with Git, and come up with
>>>>> an improvement to Git itself, to be able to contribute it without having
>>>>> to pull out their hair in despair.
>>>>
>>>> We want the same thing.  I just want to go farther and get
>>>> people familiar with (federated|decentralized) tools instead of
>>>> proprietary and centralized ones.
>>>
>>> Why require users to get familiar with (federated|decentralized) tools
>>> *unless* they make things provably more convenient? So far, I only see
>>> that this would add to the hurdle, not improve things.
>>
>> Arguably for some federated/decentralized tools are preferred
>> (for philosophical reasons), even if they do not achieve even feature
>> parity with centralized tools (c.f. FSF).
Philosophical and ideological reasons.
> This statement is false. If you had talked about *your* preference, it
> would be true. But to state that federated/decentralized tools are
> universally preferred is nonsense.
The key word is "some" (or, if you prefer, "a few").
Show 5 quoted lines
> You know as well as I do that most users/contributors go for convenience.
> 
> And if you require an inconvenient step (e.g. subscribing to a
> federated/decentralized philosophy), most potential contributors simply
> stop being potential contributors. End of story.

For some people registering on GitHub and using web interface (though I think there is also command line interface, don't know if it covers PRs) would be the inconvenient step. Just saying.

What I would like to see is bidirectional bridge between email and GitHub (and possibly other hosting sites), so that everybody could use their favorite interface, be it Git + email client, or Git + web browser (or desktop client for GitHub). Just like thanks to Gmane and Gmane-like public-inbox I can use either email client or news reader, and it is [nearly] transparent regarding to which one I use.

Even better if hosting site implementation (of pull requests, etc.) were based on federated systems (like email, or Usenet, or IRC, or XMPP), and not closed in walled gardens; with hosting site just being one particular implementation (like e.g. Ghost blog engine, and Ghost Pro hosting site).

I agree that lowering barriers to contribution for new class of users (like MS Windows users; setting up MTA on Linux etc. for git-send-email or git-imap-send is not very complicated), if it would be possible without inconveniencing existing reviewers... which are even more important, judging by the amount of "needs review" messages in "What's cooking...".

Best,
-- 
Jakub Narębski
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 28 of 59 in “Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path]”
  1. Stefan BellerAug 16, 2016
  2. Junio C HamanoAug 16, 2016
  3. Jeff KingAug 16, 2016
  4. Junio C HamanoAug 16, 2016
  5. Stefan BellerAug 16, 2016
  6. Junio C HamanoAug 16, 2016
  7. Eric WongAug 16, 2016
  8. Eric WongAug 16, 2016
  9. Johannes SchindelinAug 18, 2016
  10. Eric WongAug 18, 2016
  11. Junio C HamanoAug 18, 2016
  12. Johannes SchindelinAug 19, 2016
  13. Johannes SchindelinAug 19, 2016
  14. Stefan BellerAug 19, 2016
  15. Eric WongAug 19, 2016
  16. Johannes SchindelinAug 22, 2016
  17. Jeff KingAug 22, 2016
  18. Eric WongAug 19, 2016
  19. Johannes SchindelinAug 22, 2016
  20. Jakub NarębskiAug 22, 2016
  21. Johannes SchindelinAug 25, 2016
  22. Jakub NarębskiAug 28, 2016
  23. Johannes SchindelinAug 29, 2016
  24. Eric WongAug 22, 2016
  25. Johannes SchindelinAug 25, 2016
  26. Jakub NarębskiAug 27, 2016
  27. Johannes SchindelinAug 28, 2016
  28. Jakub NarębskiAug 28, 2016
  29. Johannes SchindelinAug 29, 2016
  30. Jeff KingAug 19, 2016
  31. Jakub NarębskiAug 20, 2016
  32. Johannes SchindelinAug 22, 2016
  33. Duy NguyenAug 22, 2016
  34. Philip OakleyAug 22, 2016
  35. Johannes SchindelinAug 24, 2016
  36. Eric WongAug 24, 2016
  37. Johannes SchindelinAug 25, 2016
  38. Jakub NarębskiAug 27, 2016
  39. Johannes SchindelinAug 28, 2016
  40. Announcing Git User's Survey 2016 [was: Working with public-inbox.org]Jakub Narębski, Aug 28, 2016
  41. Johannes SchindelinSep 9, 2016
  42. Jakub NarębskiSep 9, 2016
  43. Johannes SchindelinAug 24, 2016
  44. Eric WongAug 24, 2016
  45. Jeff KingAug 24, 2016
  46. Eric WongAug 24, 2016
  47. Johannes SchindelinFeb 10, 2017
  48. Arif KhokarFeb 13, 2017
  49. Johannes SchindelinFeb 13, 2017
  50. Arif KhokarFeb 14, 2017
  51. Arif KhokarFeb 14, 2017
  52. Eric WongFeb 14, 2017
  53. Junio C HamanoFeb 13, 2017
  54. Arif KhokarFeb 14, 2017
  55. Junio C HamanoFeb 14, 2017
  56. Arif KhokarFeb 14, 2017
  57. Jeff KingFeb 14, 2017
  58. Johannes SchindelinAug 25, 2016
  59. Johannes SchindelinAug 26, 2016

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.