> 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.
