Notices by Gitea (gitea@social.gitea.io)

@play0ad @nik
Gitea is not doing any crypto things (there was a proposal to investigate related technology to increase transparency,include additional community members in being able to vote in elections, but it didn’t go past that suggestion). Gitea has yearly elections https://blog.gitea.com/quarterly-23q1/ and other than expanding the TOC (done with a vote by the entire maintainer team after months of discussion) nothing has changed with governance.

@play0ad @nik as for federation we are (slowly) adding functionality to be able to federate across instances, with our focus on moderation and spam prevention first to ensure that instances have protections prior to full federation.

To answer the question we are getting: Gitea is not Open-Core. We are fully licensed under MIT, and you can confirm yourself by looking at the repo: https://github.com/go-gitea/gitea/blob/main/LICENSE
Per our contribution rules proprietary licensed code won’t be accepted and is blocked by the TOC.

@annika yup. They were moved to a dedicated path in 1.21.0, if you’re interested in the reasoning you can find it here: https://blog.gitea.com/release-of-1.21.0#%EF%B8%8F-move-public-asset-files-to-the-proper-directory-25907