Like I said, I'm going to put in some work to see what it looks like to re-implement current Github CI/tooling usage on Codeberg. I've setup an account, and am willing to hand that off to XSF membership if/when they want: https://codeberg.org/xsf

After looking at the automation in the xeps​ repo, I see what you mean about how much work has been put into GIthub integration. Wish me luck

Elle, I would be happy to help with these efforts. I have not worked much with automation (Woodpecker or otherwise) but have have been managing a few small Forgejo instances and am reasonably familiar with how it works.

There has also been talk in the group (more on the speculative side) about the XSF running our own Forgejo instance (to which I suggested we can implement an option to sign in via one's XMPP account). Whether that takes off or not, the fact that Codeberg runs Forgejo means any tooling we write there can more easily be shifted. I think it would be good for us to use standards-based systems (such as Forgejo which is working on ForgeFed) as much as possible, as those are what make for a more sustainable open web.

Moving away from GitHub will take a not-to-be-underestimated amount of effort and dedication. A couple of years ago, there was an experiment with moving away from GitHub to GitLab. Quite some effort has been put into that, but in the end, it didn't take off. The remnants are still accessible at https://gitlab.com/xsf
Thanks Guus for providing some context. There does seem to be a lot of interest in moving away from GitHub, though unfortunately less so in terms of volunteers available to actually set up and maintain alternate tooling. I wasn't aware that people had actually attempted to start moving to Gitlab.
My estimation is that we have less volunteer-resources available today. As such, I don't see how we would realistically pull off a migration, let alone start to maintain that new infrastructure. I'm happy to be proven wrong.

On a related note, I've also been meaning to help out with the infrastructure team. Knowing how the existing setup works sounds like a good first step to figuring out how to change it :-) that aside, given what I hear about the team being overworked and the fact that I know my way around sysadmin tasks, I think it's a place I can contribute meaningfully. Maybe this thread will provide me the push to get started!

~Badri

PS: Guus, heads-up that I'm receiving this discussion on the Standards mailing list. You may want to confirm if you copied it to the Board list as well