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

Re: Migrate away from vger to GitHub or (on-premise) GitLab?

From
Theodore Ts'o <tytso@mit.edu>
Date
Feb 2, 2024, 16:16 UTC
Message-ID
<20240202161643.GD119530@mit.edu>
In-Reply-To
<008b01da55eb$9f3c36d0$ddb4a470$@nexbridge.com>
On Fri, Feb 02, 2024 at 10:22:18AM -0500, rsbecker@nexbridge.com wrote:
Show 10 quoted lines
> >
> >Did you consider to rather read the list through
> >gmane.comp.version-control.git nntp newsgroup?
> >
> >This way you get only very specific mails in your mail-box, those
> >where you are explicitly CC'ed, and you usually get more support
> >for structuring from NNTP readers than from mail clients.
> 
> Google is dropping Usenet NNTP updates on 22 Feb 2024. I would love
> that idea, but it has a limited lifespan.

Google might be dropping Usenix NNTP updates, but news.gmaine.io and nntp.lore.kernel.org are not not run by Google. So whether or not Google groups are supporting NNTP is not really supporting.

One other thing I would note that is that if someone isn't interested in following most of the git mailing list, it's unclear how much they can actually contribute. Maybe they could fix spelling or grammer issues in the git man pages, but it's unlikely they could actually make code contributions.

So from an open source project perspective, which is primarily run by volunteers, each open source project has to make a cost-benefit tradeoff as far as the *project* is concerned. Individuals do not have a fundamental human right to contribute to a project. Hence, the open source project doesn't owe an obligation to spend a huge amount of effort supporting some kind of forge web site just because some potential contributors are clammoring for it. Especially if they are saying that they can't be bothered to follow the mailing list traffic because it's somehow too much.

(Of course, I have all of the Linux kernel mailing list flowing into my inbox, and have e-mail practices that can handle that load --- so it's hard for me to have much sympathy about people complaining that the e-mail load for git is too large --- compared to LKML, it's *nothing*. :-)

						- Ted
Previous: rsbecker@nexbridge.comNext: Michal Suchánek
Message 39 of 48 in “Migrate away from vger to GitHub or (on-premise) GitLab?”
  1. Hans MeiserFeb 1, 2024
  2. Kristoffer HaugsbakkFeb 1, 2024
  3. Hans MeiserFeb 1, 2024
  4. Antonin DelpeuchFeb 1, 2024
  5. Dragan SimicFeb 1, 2024
  6. Konstantin RyabitsevFeb 1, 2024
  7. Dragan SimicFeb 1, 2024
  8. Dragan SimicFeb 1, 2024
  9. Hans MeiserFeb 1, 2024
  10. Dragan SimicFeb 1, 2024
  11. Hans MeiserFeb 1, 2024
  12. Dragan SimicFeb 1, 2024
  13. rsbecker@nexbridge.comFeb 1, 2024
  14. Dragan SimicFeb 1, 2024
  15. Hans MeiserFeb 2, 2024
  16. Hans MeiserFeb 2, 2024
  17. Dragan SimicFeb 2, 2024
  18. Muting and unmuting threads (Was: Migrate away from vger to GitHub or (on-premise) GitLab?)Dragan Simic, Feb 2, 2024
  19. Phillip WoodFeb 2, 2024
  20. Dragan SimicFeb 2, 2024
  21. Junio C HamanoFeb 2, 2024
  22. brian m. carlsonFeb 2, 2024
  23. Patrick SteinhardtFeb 2, 2024
  24. Phillip WoodFeb 2, 2024
  25. Michal SuchánekFeb 2, 2024
  26. Dragan SimicFeb 2, 2024
  27. Oswald BuddenhagenFeb 4, 2024
  28. Dragan SimicFeb 4, 2024
  29. Michal SuchánekFeb 4, 2024
  30. Dragan SimicFeb 4, 2024
  31. Michal SuchánekFeb 4, 2024
  32. Oswald BuddenhagenFeb 5, 2024
  33. Hans MeiserFeb 2, 2024
  34. Hans MeiserFeb 2, 2024
  35. Nico WilliamsFeb 1, 2024
  36. Kristoffer HaugsbakkFeb 1, 2024
  37. Sergey OrganovFeb 2, 2024
  38. rsbecker@nexbridge.comFeb 2, 2024
  39. Theodore Ts'oFeb 2, 2024
  40. Michal SuchánekFeb 2, 2024
  41. Junio C HamanoFeb 2, 2024
  42. Theodore Ts'oFeb 2, 2024
  43. Hans MeiserFeb 6, 2024
  44. Dragan SimicFeb 6, 2024
  45. Junio C HamanoFeb 2, 2024
  46. rsbecker@nexbridge.comFeb 2, 2024
  47. Junio C HamanoFeb 2, 2024
  48. rsbecker@nexbridge.comFeb 2, 2024

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.