FWGS / xash3d-fwgs

Xash3D FWGS engine
1.58k stars 241 forks source link

sr.ht migration #1552

Open a1batross opened 11 months ago

a1batross commented 11 months ago

Clickbait title!

I don't think it makes sense to move from GitHub, but we're (me and @mittorn) has tried using sr.ht for engine development, and it was mostly fine for both of us.

What I want is to have another development mirror just in case there will be issues with GitHub (we already had the "sanctions" plaque on the xash3d repository, I already was banned on GitHub once, and already lost 2FA once earlier this month, and so on), so I don't have to stop working on the engine while trying to restore access to GitHub.

I think sr.ht having the classic, email-based workflow, forces following some of the contribution rules we already have. I understand that's a controversial topic, and I'm still not a fan of emails, but I think we can handle it. At least, until Forgejo gets federation support. Also, sr.ht frontend is pretty lightweight, which compared to GitHub (not to mention GitLab, ew) is a giant advantage.

Here goes the To-Do list on what we need to do to have SourceHut as a viable alternative for developers and contributors:

nekonomicon commented 11 months ago

I'm not sure whether @nekonomicon would like to migrate hlsdk-portable

I don't mind. I like new things and hate legacy.

jeefo commented 11 months ago

Politics about sanctions on github is very unclear, for example: https://github.com/FWGS/regamedll is marked as sanctioned too for an unknown reason: image

a1batross commented 11 months ago

@jeefo yeah, they already marked FWGS restricted. However, as support said, it only restricts us from paid services. Using GitHub for free is fine... for now.

@nekonomicon that's cool. :)

a1batross commented 10 months ago

builds.sr.ht integration: DONE