daniel:// stenberg://Oct 30
One. Open. Issue.
Show threaddaniel:// stenberg://Oct 30
and now, **zero**
Show threaddaniel:// stenberg://Oct 30
Probably the first time since we switched to GitHub back in 2010.
Show threadUlf SeltmannOct 30
@bagder
The perfect time to leave GitHub.
Show threaddaniel:// stenberg://Oct 30
@smoe are we really doing this again? Will you be covering the huge CI expenses as GitHub graciously does for us now?
Show threadNik | Klampfradler 🎸🚲Oct 30

@bagder @smoe

Are we again at the point where you derail the discussion, while you know perfectly well that you can continue using GitHub's CI without requiring the community to use GitHub and move development elsewhere?

Show threadPaolo RedaelliOct 30
@nik
Using github's ci without using anything else from Github? I'm interested, where I can learn more about it?
@bagder @smoe
Show threadNik | Klampfradler 🎸🚲Oct 30

@paoloredaelli @bagder @smoe

Just mirror your repository to GitHub from Codeberg (or so). It will receive all pushes and trigger CI actions.

But I am also sure that GitHub CI is not a requirement at all. The cost argument is a red herring covering up the bribery.

Show threadAndreas Ahlenstorf
@nik @paoloredaelli @bagder @smoe Cloud CI is expensive. Free tiers or allowances for OSS have been scaled back significantly in recent years. DIY has high up-front costs and is organizationally challenging (maintenance, availability). Simply renting a server and installing Jenkins on it is a recipe for disaster. CI is a high-value target (build, signing) and offers remote code execution for everybody on the internet when building PRs.
Oct 31 at 9:07amWeb