One. Open. Issue.
and now, **zero**
Probably the first time since we switched to GitHub back in 2010.
@bagder
The perfect time to leave GitHub.
@smoe are we really doing this again? Will you be covering the huge CI expenses as GitHub graciously does for us now?

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

@nik @smoe aha you are in charge of GitHub's sponsorship decisions and can tell this, awesome!

@bagder @smoe

No. I am in charge of "tired of hearing bagder whine about what a crap platform GitHub is while being otherwise fine with their bribery".

@nik
Using github's ci without using anything else from Github? I'm interested, where I can learn more about it?
@bagder @smoe

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

@nik @paoloredaelli @smoe yeah, I'm doing this for all the easy and quick money I get from big tech. You caught me.

@bagder @paoloredaelli @smoe

I did not say that ;).

@nik @bagder @paoloredaelli @smoe You implied bribery. Which is ridiculous, mean and insulting to Daniel. It's also not helping your (good) agenda.

@bagder Big curl just wants curl to run on anything!! 😤

The code is portable, light on resources, and under a permissive license. I've been following this conspiracy for many years now, and curl continues to become better and more popular. 😡

You even go to great lengths to recruit new contributors to this global conspiracy! It's one of the most welcoming open source projects around. J'accuse!

@nik @paoloredaelli @bagder @smoe well, don’t think I need to hear anything else you might have to say.
@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.
for a small project where free github CI runners are enough, you just create a mirror of your project in GitHub, and then in your official repository you create an auto-push to github via post-receive-hook or whatever else. boom easy peasy.

but that doesn't work for curl, they don't fit in free stuff. curl gets official github sponsorship AKA "everything's free". the implication, of course, is that curl has to stay on github and without a viable CI alternative, it probably isn't smart to make anti-github moves

CC: @[email protected] @[email protected] @[email protected]
@nik @bagder @smoe The derailment has started with "time to leave github." You are in the replies of a post by Daniel, I think he is allowed to set the direction of this conversation. Shame on you.
@nik @bagder @smoe I don't think GitHub would be happy to sponsor curl if it wasn't on GitHub anymore (because people might wonder why that's the case).