just as we're considering how soon we want to move away from GitLab.com... I guess the answer now is "fast as we <heck>ing can"
@postmarketOS
GitLab is honestly the answer to the question:
What if we just made a really crappy alternative to GitHub
Gittea and Gogs FTW; with some new protocol for submitting patches to a server, probably without git, or atop a git hash; and documented formal mechanisms for running CI and cloning
@lewiscowles1986 @postmarketOS GitLab used to be incredibly powerful compared to GitHub, as GitHub stayed rather barebones for a good while. Today you don't see it like that because over years GitHub has caught up with most of the things that made GitLab unique.
@dos @postmarketOS
I think this might be where a bug is touted as a feature though.
I Don't want my version control, being too clever or doing to much. I want it to do what it does, and then defer to other tooling.
GitHub and GitLab offering CI is fantastic for some users. SBOM's advanced integrations. All great, for companies that should have to pay $$$ to access that inane, corporate BS
@lewiscowles1986 @postmarketOS It's good that neither of them is about doing version control then. Gitweb is super easy to set up ;)
@lewiscowles1986 They don't do version control. Their primary feature is to do project management *around* version control. Their basic value propositions are based on issue tracking and contribution management. Features like CI are useful for scrappy one-dev projects and big FLOSS communities altogether, it's hardly a "corporate BS".
Again, if all you care about is version control, all you need is gitweb.
@dos
I don't know if you realise this, but you are just reporting marketing hype.
The majority of GitHub users, and I'd suspect GitLab users have very few commits and do not meaningfully interact with anyone.
Much more useful software exists for issue tracking, where styled markdown is not the standard for issue reporting, which is some vague half-way house between ideas, bugs and discussion, which GitHub is trying to disambiguate.
@dos and why you keep pointing at gitweb when I'd earlier expressed my like of gittea and gogs, I don't know
@lewiscowles1986 Well, it's easy - because both Gitea and Gogs follow the GitHub's approach. They take a VCS tool and build a project management & collaboration tool around it. You already said that's not what you want ;) The approach you described used to be popular in FLOSS about 20 years ago (with projects commonly deploying single-concern tools like Bugzilla, Trac, Jenkins, gitweb, Patchwork etc.), but these days it appears to be used just by a minority of long-standing projects.
@lewiscowles1986 I guess SourceHut is as close as it gets to be a modern take on such approach, since while it's a suite of various tools for various purposes you should be able to easily mix'n'match them or deploy in parts (e.g. git.sr.ht is analogous to gitweb and only becomes a project management tool when combined with lists.sr.ht and todo.sr.ht)
@dos @postmarketOS
Sorry, I'm not sure if I understood the point you are making there. GitHub and GitLab are not doing version control?
That is their primary feature bud.