Repository navigation
Conversation
Gitly compares itself to GitHub and GitLab, but there was no Gitea comparison anywhere in the repository, and Gitea is the more useful bar: it is open source, single-node, and solves the same problem at the same scale. Issue vlang#142 asks for a Gitea row on the gitly.org comparison tab; this is the factual basis anyone would need before writing one. The source of truth is Gitea's own matrix at https://docs.gitea.com/installation/comparison, checked against Gitea docs version 28. Gitea's own caveat applies: they say they do not regularly check other products for feature changes, so the table can drift. That caveat is carried into the document so a reader knows the bar moves. Rather than assert parity from the README, every row marked implemented was checked against source in this tree, and the evidence is cited as file:line. Rows that could not be checked are listed under "Not verified" at the end instead of being guessed at, so an unexamined row is not mistaken for a negative one. Two findings worth calling out, because they are worse than plain gaps: - Wiki has a setting and no feature. `repo/repo.v:49` declares `disable_wiki`, `repo/repo.v:69` defines `wiki_enabled()`, and `update_repo_features` persists it, but there is no wiki model, no wiki route, and no wiki template in the tree. A repository owner can switch it on and find nothing. - Topics is a counter. `repo/repo.v:23` declares `nr_topics` and `repo/repo_template.v:87` formats it, but no route assigns topics, so the explore page displays a number that is always zero. Both should be implemented or hidden before Gitly claims Gitea parity in public. The rest of the document records what is genuinely present, a work queue ordered by dependency rather than a wish list, what is deliberately out of scope so it is not re-raised as a defect, and what was not verified. The bar is Gitea's feature matrix, not everything Gitea can do. GitLab stays tracked in docs/gitlab-parity.md and this does not replace it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a phased roadmap. Companion to gitea-parity.md.