mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

373K
active users

We're finally migrating to git with @gitea in August!
The migration is planned to happen on the 19th and 20th of August (European hours). It's been long awaited, more than 12 years!

Main discussion:
wildfiregames.com/forum/topic/
Migration Plan Details
wildfiregames.com/forum/topic/

@play0ad

Please do not use the VC and crypto-bullshit funded #Gitea.

The community fork is #Forgejo, which should be used instead.

@nik We support the excellent forgejo community effort, and we will consider shifting when forgejo gains widespread adoption. We wish to use the most mainstream tool to avoid lacking upstream support (for instance, Jenkins does not officially support forgejo), and we do not care for features such as federation. We will probably provide an official mirror on codeberg.org after our migration to git is effective, if you wish to avoid registering to a gitea instance.

@play0ad What the actual…

Forgejo has widespread adoption. Everyone and their dog migrated to it with its first stable release. Jenkins supports Forgejo just fine (because it is, in fact, Gitea).

The question of a mirror is entirely unrelated, but: "We don't care about federation and make a [second-class] mirror" means you are ok with some contributors being second-class.

0 A.D. ✅

@nik As far as we know @Blender hasn't and we did the switch to @gitea from Phabricator / @phorge instead of @gitlab because they did and they pledged to maintain it. If they move to @forgejo in the future maybe we'll do to. As far as we are aware the fediverse features are not in yet?
The only thing we'll miss are the awesome @davidrevoy mascots which 0 A.D. terribly misses.

@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 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.

blog.gitea.com · Gitea Quarterly Report 23Q1 | Gitea BlogHappy new year! As is tradition, the Gitea project conducted its yearly election at the end of December to decide the ownership team for 2023.

@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.

@hexaheximal @play0ad @nik hi, it is very much true. There were months of discussions between maintainers to develop a proposal for updated governance which was voted on by all maintainers, and with the exception of one maintainer all the other votes were in favour. You can read about it in our blog post along with the results of the vote. There have been multiple elections since too.

@hexaheximal @play0ad @nik just because someone makes a statement on the internet doesn’t make it fact. The facts are out there for you look up yourself. We’ve published everything for external parties to review, including strengthening votes and having election auditors.