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
Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Date
Feb 4, 2024, 15:12 UTC
Message-ID
<Zb+pQk9R3AOouFxF@ugly>
In-Reply-To
<20240202115004.GV9696@kitsune.suse.cz>
On Fri, Feb 02, 2024 at 12:50:04PM +0100, Michal Suchánek wrote:
Show 6 quoted lines
>Given the open nature of lore it should be feasible to provide
>additional interfaces on top of it that cater to people used to PRs
>on popular forge web UIs without hijacking the whole project and the
>existing tools and interfaces. For some reason people are set on
>replacing it as a whole, and removing the interfaces they personally
>don't use,
>calling them obosolete.
>
because they positively *are*.

when i started, patch-based code reviews were the norm, and i'm still using them for my small project with almost no external contributions.

but after working with gerrit code review for over a decade, i find it mind-boggling that people are still voluntarily subjecting themselves to mail-based reviews for serious high-volume work.

it doesn't matter just how super-proficient you got with your old tools. there is just no way you'll get anywhere near as efficient as you would with the new ones, if you just were interested enough to learn them. migrating the workflows that are worth keeping isn't such a bit deal.

i'll note that i don't consider github-like forges to be adequate tools for serious work, as they seem to intentionally discourage producing polished commits. the gerrit project is unfortunately not interested in building a proper forge, but luckily there is a bridge to github (hosted version available at gerrithub.io).

Previous: Dragan SimicNext: Dragan Simic
Message 27 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.