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
HMHans Meiser <brille1@hotmail.com>
Date
Feb 1, 2024, 18:36 UTC
Message-ID
<DB9P195MB21303B5546A764A18FE78C97E2432@DB9P195MB2130.EURP195.PROD.OUTLOOK.COM>
In-Reply-To
<c3b6de0c2ccf71f0dfa5aff06fa63d8f@manjaro.org>
> Could you, please, clarify what kind of git documentation are you
> referring to?  Are you having git man pages in mind?
Yes, these in particular.
From my point of view, many of these are quite unorganized, hard to read and – as I believe – need a fix-up. Markdown could replace the currently used language, so editing them would be more easy, proving support for preview and lint the documentation.
>Quite frankly, I think you've missed some important points from the
> Konstantin's message.  To sum it up a bit, not having continuous support
> is simply unacceptable for any kind of a long-term project.
As I wrote, once installed on-premise, no-one will shut down an on-premise git server except for yourself. It can run for eternity. You just need someone to administer it properly and publish the website.
In the end, it's all just about git. You may create your own git webserver (https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb), or just use an existing one, like the GitLab server: https://about.gitlab.com/install/
In these servers, everything is configurable. Moreover, many plug-ins exist for plumbing extensions to these providers. It's possible to establish your own workflow, rights management and automatic handling. You just need someone who is an expert with the tool of your choice.
Many other great repositories already are using one of those providers; Meta, Google, Microsoft for example share their code there – just to name a few. I wouldn't consider these users as being known for being exceptional risk-takers.
Previous: Dragan SimicNext: Dragan Simic
Message 11 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.