I meant to ask earlier, why the enterprise thing? Afaik itâs for managing multiple GitHub orgs under a single umbrella? Sorry if you already wrote a blog entry or something about this. đ
it's complicated. We've had the org marked as some kind of cloud blabla account for a long time, but recently they've pushed for that sort of account is going away and is instead becoming this other account... I suspect the problem started in this other account. But who the heck knows. This is big-company mumbo jumbo at its worst.
@jakob it fits the road #GitHub has taken since it was taken over by #Microsoft. The original promise was to be #OSS friendly. Now that they are the goto place for Open Source they change the rules step by step. This also affects paying users. The SaaS price list exploded a couple of months ago. You now even pay extra for git LFS. I guess, this is the enshittification process @pluralistic is talking about.
actually, it is somewhat more complicated than so. We were "bumped up" as a courtesy by GitHub to get more github action "powers" and that makes us a little special there and that sometimes leads to ... surprises.
@jakob @pluralistic it is quite simple to me. OSS projects had full GitHub actions access. At least âno limitsâ was the advertising and my main reason to stay on that platform. That has obviously changed. Now larger OSS projects need extra attention due to limitations never revealed before.
@jakob @pluralistic I am deeply concerned about what is happening here. I read your message such that you do not have full and unlimited access to GitHub Actions with your OSS project and this definitely is not what was promised nearly a decade ago. Can you please explain what makes the special treatment of curl necessary? What kind of facts am I missing?
@markuswerle @jakob @pluralistic This is how I interpret the situation: #GitHub offers open source programs free access to GitHub actions today exactly as it did in the past. This access is limited in CPU performance and parallelism. It always was. All free CI services do this.
The #curl project was bumped to a fancier account to give us more actions powers: more CPU and more parallelism.
That is them doing us a favor and them supporting us, not the other way around.
@jakob @pluralistic thanks for the clarification. I accept your description of the limitations at place, despite me remembering them differently. Maybe the limitations were there all the time but not prominently mentioned. I should have taken screenshots at the time when I was excited about GitHub.
@jakob @pluralistic and any of these abuse attempts would be easily detectable and would immediately lead to a platform ban. I accept there was a limit you ran into but I do not follow your argument here that the limit is necessary in the first place.
@markuswerle no need to tell ME that. Tell that to every existing could-CI service out there that you clearly have figured out something they have not. I'm just a user.
@markuswerle @pluralistic GitHub Enterprise offers some additional things for security, etc. I don't know if curl uses those, but I interpret it as a way to make sure curl (as critical infrastructure) gets whatever protection they can offer.
Niels
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to daniel:// stenberg:// • • •Jakob Borg
in reply to daniel:// stenberg:// • • •a blog entry or something about this. đ
daniel:// stenberg://
in reply to Jakob Borg • • •Jakob Borg
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Jakob Borg • • •Jakob Borg
in reply to daniel:// stenberg:// • • •Markus Werle
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Markus Werle • • •Markus Werle
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Markus Werle • • •Markus Werle
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Markus Werle • • •@markuswerle @jakob @pluralistic This is how I interpret the situation: #GitHub offers open source programs free access to GitHub actions today exactly as it did in the past. This access is limited in CPU performance and parallelism. It always was. All free CI services do this.
The #curl project was bumped to a fancier account to give us more actions powers: more CPU and more parallelism.
That is them doing us a favor and them supporting us, not the other way around.
Markus Werle
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Markus Werle • • •Markus Werle
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Markus Werle • • •Jakob Borg
in reply to daniel:// stenberg:// • • •