Gitea is a fork of Gogs, so it has everything on that list and more. Sadly Gitea suffers from the usual problem that open source projects has, poor documentation. If you really want to compare feature lists, here's the one listed on their website (https://docs.gitea.io/en-us/).
Why compare two products by their README and not their website? Heck, why not compare them by using their test instances that are there for you to try.
Gitea has every feature that Gogs had at the point when they forked it, plus a few that they've ported over.
But there are still features that have been in Gogs for over a year now that Gitea does not have.
One example that burned me earlier this year, Gitea's backup/restore feature is still very underdeveloped. Gogs' backup/restore feature has been capable of backing up and switching databases for over a year, while Gitea still can only backup and restore to a database of the same type (e.g. Postgres to Postgres)
Doubtful. IIRC it was somewhat of a hostile & opportunistic fork. The Gogs maintainer went on vacation or something and didn't reply to issues for a couple weeks so someone forked to Gitea and declared themselves the new mainline only for the Gogs maintainer to return and not appreciate the attempted usurpation.
I think it was more than a couple of weeks. Also before the fork the maintainer was asked multiple times to allow other contributors to become co-maintainer to reduce the bus factor.
As far as I understand the reason for the fork was that Gogs has a single maintainer who want to keep control over the project (he created it, so he has that right).
Gitea on the other hand was to be more of a community project with multiple maintainers and ways for active contributors to become one.
Though Gogs has more stars, and currently, I think, more related project/integrations, looking at GH stats, Gitea has more activity, PR's, commits, etc.
That made me choose Gitea over Gogs. Really content with it.. was planning on using Gitlab at first, but it would require AWS instances with double the oomph.
The documentation could be better, agree, but a search in issues or filing a Help wanted issue comes a long way.
I'd say if you don't have time to compare them, don't offer a comparison. It's not doing anyone any favors. In fact that only serves to waste more of your precious time.
Why compare two products by their README and not their website? Heck, why not compare them by using their test instances that are there for you to try.