Oh, one thing, I think a lot of this might be simplified by creating a template repo rather than relying too much on documentation. E.G. putting placeholder README, LICENSE, .gitignore, etc.
There could be another section that states how to fork from the CLI
As far as I'm aware this is not possible. The issue I had isn't with using the web UI for the fork button, it was the idea…
Sorry, I disagreed really strongly about the idea of deleting and re-cloning the repo after forking. Just being quiet about it isn't a good way to handle that. The reason I disagreed is because…
Headscale contains some jank WRT using the official apps:
After opening the app, the kebab menu icon (three dots) on the top bar on the right must be repeatedly opened and closed until the…
That's a good point, that's what we have right now. I had been thinking at the time of converting the bylaws to markdown and creating a pull request so that we can all review it and make changes,…
The wiki seems to just be markdown. So, either we use the wiki for documentation and the repo for documents, or we just use the repo for documentation and documents and ignore the wiki. I lean…
While I really like MediaWiki, I think it would be more accessible to standardize on Markdown than to require everyone to learn two separate markup languages for documentation and project…
I can spin up a MediaWiki real quick if it would be helpful. Not to say that I'm against other options. I don't have any experience with ticket tracking sw like that, at least on the hosting side
I would use the ssh URL and perhaps make a note of how it differs from github ssh URLs.