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
NWNico Williams <nico@cryptonector.com>
Date
Feb 1, 2024, 17:46 UTC
Message-ID
<ZbvY/01kebuFagn2@ubby>
In-Reply-To
<20240201-primitive-aardwark-of-contentment-aaabb9@lemur>
On Thu, Feb 01, 2024 at 10:39:04AM -0500, Konstantin Ryabitsev wrote:
> [excellent discussion of e-mail workflows elided]

It would surely help if the e-mail interfaces of forges were not terrible. But they really have to be as good as the mailing list approach.

I envision that the "issues" and "PRs" could be webmail-ish thread trackers that auto-close on prolonged silence. One could open issues/ PRs by e-mail, close them by e-mail, etc., all e-mails going to the same [forge-run?] list address, but still have a forge-style view of a PR's commits, still have a forge-style code review web UI (with all comments going to e-mail too, and with e-mail being first-class, not an afterthought), still have a CI checks UI, and still have a big rebase-and-merge button for maintainers.

I.e., forge e-mail UI as first-class equivalent of forge web UI.

The forges tend to be run by people who prioritize users who are not heavy e-mail workflow devs. It makes economic sense, given how few users demand e-mail as a first-class forge UI. Still, it would be quite awesome if some forge did this.

> - How to avoid a vendor lock-in? [...]

Assuming some forge exists with an e-mail UI on the same footing as its web UI, and also good enough for kernel/git/... devs, you could maintain mirrors on all the other forges, naturally, and always fallback on e-mail only if the primary forge disappears or becomes too expensive.

> - How to avoid centralization and single points of failure? [...]

It's all forks, all the time. It'd be good if the kernel maintainers maintained non-forge git servers as mirror/staging/primary repos.

> - How to avoid alienating these hundreds of key maintainers who are now
>   extremely proficient at their query-based workflows? [...]

The only answer is to stick to the current workflow until some forge provide an equivalently first-class e-mail interface. New participants just have to get used to it. IMO.

Nico
Previous: Hans MeiserNext: Kristoffer Haugsbakk
Message 35 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.