Live data from Hacker News

GitHub to Codeberg: my experience

eldred.fr

31–40 of 140 posts

Re: GitHub to Codeberg: my experience

#31
post #17

Earlier quoted context omitted.

... Training their own models out of your code...

If you're publishing your code anywhere, it's getting trained on. MS does not restrict themselves to only training on GH-hosted code.

> If you're publishing your code anywhere, it's getting trained on

citation needed. first they need to know my code exists... spend time and traffic crawling it because it's sure as hell not going to be hosted on azure... probably get detected and banned.

Re: GitHub to Codeberg: my experience

#32
post #19

What really stands out to me in this migration story isn't the technical side at all, but the reminder that "feature parity" isn't the real hurdle here. Codeberg is already good enough for most day to day workflows; what it doesn't have is the gravitational pull GitHub built through network effects, integrations, and plain old inertia.

This is partially being addressed by projects like https://tangled.org. It's built on the same protocol as bluesky, meaning your identity is preserved across different platforms so that _where_ your git is hosted is unrelated to how you discover and connect with others.

Re: GitHub to Codeberg: my experience

#33
post #7

Does Codeberg provide free CI runners? I'd estimate Microsoft spends over $100m/year on free Github CI. Likely their biggest cost. It doesn't seem like a reasonable thing Codeberg to fund for free.

You can use your own Woodpecker instance with Codeberg. I do this at work and privately and it works great and is much faster than the free CI that Codeberg can afford.

Re: GitHub to Codeberg: my experience

#34
post #19

What really stands out to me in this migration story isn't the technical side at all, but the reminder that "feature parity" isn't the real hurdle here. Codeberg is already good enough for most day to day workflows; what it doesn't have is the gravitational pull GitHub built through network effects, integrations, and plain old inertia.

This is partially being addressed by projects like https://tangled.org . It's built on the same protocol as bluesky, meaning your identity is preserved across different platforms so that _where_ your git is hosted is unrelated to how you discover and connect with others.

FWIW, Forgejo (Codeberg) is also building federation capability [0].

[0]: https://codeberg.org/forgejo-contrib/federation/src/branch/m...

Re: GitHub to Codeberg: my experience

#35
post #17

Earlier quoted context omitted.

... Training their own models out of your code...

If you're publishing your code anywhere, it's getting trained on. MS does not restrict themselves to only training on GH-hosted code.

Yet, not restricting themselves to train on permissively licensed code only.

The two ends of the spectrum, both source available and copyleft licensed code shouldn't be used for training, but who's listening.

Re: GitHub to Codeberg: my experience

#36

I've noticed that several projects on the front page today (and over the past few days) are migrating away from GitHub. Is there any recent event or broader trend that explains this shift?

Not naming names but heard from contacts that it is currently a sh*t-show of politics internally right now at GitHub and no progress is being made/large parts of the platform are abandoned unless P0.

Re: GitHub to Codeberg: my experience

#37
post #14
post #13

Earlier quoted context omitted.

For me this is the GitHub moat.

It isn't really a moat so much as a loss leader. Travis CI was free back in the day IIRC.

So it's a moat that trickles out to the sea and has to be kept filled very expensively.

(I'm just keeping the metaphor alive because for me it is the primary blocker, whatever we call it.)

Re: GitHub to Codeberg: my experience

#38
post #19

What really stands out to me in this migration story isn't the technical side at all, but the reminder that "feature parity" isn't the real hurdle here. Codeberg is already good enough for most day to day workflows; what it doesn't have is the gravitational pull GitHub built through network effects, integrations, and plain old inertia.

And just sheer amount of documentation and examples out there. Everyone uses it, therefore everyone writes about it, the new hire probably knows it, and if they don't they can find it easily.

Then again maybe for stuff like actions and in general CI/CD it's not all that bad, you don't need whole team to know exactly how to write it, you just need to have a person knowing it. and it's generally not all that hard to learn.

Re: GitHub to Codeberg: my experience

#39
post #25
post #15

Earlier quoted context omitted.

They do, but their capacity is limited so you have to ask them for access and make a reasonable case. https://docs.codeberg.org/ci/

Actually, that's only for the Woodpecker instance. Forgejo Actions can be used without asking for permission, and three tiers of (Linux-only, adm64-only) free runners are provided.

Ok, that's very interesting. Last I checked only self-hosted runners were documented, but I definitely want to look into this.

Re: GitHub to Codeberg: my experience

#40
post #15
post #7

Does Codeberg provide free CI runners? I'd estimate Microsoft spends over $100m/year on free Github CI. Likely their biggest cost. It doesn't seem like a reasonable thing Codeberg to fund for free.

They do, but their capacity is limited so you have to ask them for access and make a reasonable case. https://docs.codeberg.org/ci/

Been a while since I applied, but when I did the "reasonable case" was mostly just your repo being FOSS and having a license file (+ a very vague description of what you plan to do and how much resources you'll use)
Post reply on HN