Live data from Hacker News

GitHub to Codeberg: my experience

eldred.fr

81–90 of 140 posts

Re: GitHub to Codeberg: my experience

#81
post #52
post #49

Earlier quoted context omitted.

That’s interesting. I would have said the opposite. I’ve never used any of the social features, but the technical aspects (including integrations) are where the value is. It does break and go down; and GHA are a real pain in the ass. But the basic hosting and PR workflow are fine.

The PR workflow is fine if you don’t care about stacked PRs, you don’t write reviews, you don’t read nontrivial reviews, and you don’t need the diff viewer.

You should use your IDE to do all of those things. Much better that way.

Re: GitHub to Codeberg: my experience

#82

I lost what little respect I had for Codeberg when they tried to spin a teenager exploiting an opportunity to spam/troll[1] that GitHub had solved several years prior[2] into "hate campaigns from far-right forces" that "endanger free/libre software projects" so they could toot their own horn at how good they were in the face of adversity[3] (and generally have a good moan about the right-wing) instead of admitting th…

If they were genuinely just attempting to "troll" by spamming (which is a pretty lame thing to do to begin with), they wouldn't have had to use a racist slur in their message. The fact they did makes their intent pretty clear.

If a project taking a stance against people spamming the n-word makes you lose respect for them, that says a lot more about you than the project.

Re: GitHub to Codeberg: my experience

#83

I lost what little respect I had for Codeberg when they tried to spin a teenager exploiting an opportunity to spam/troll[1] that GitHub had solved several years prior[2] into "hate campaigns from far-right forces" that "endanger free/libre software projects" so they could toot their own horn at how good they were in the face of adversity[3] (and generally have a good moan about the right-wing) instead of admitting th…

> Running CI/CD pipelines can use significant amounts of energy. As much as it is tempting to have green checkmarks everywhere, running the jobs costs real money and has environmental costs. > Unlike other giant platforms, we do not encourage you to write “heavy” pipelines and charge you for the cost later. We expect you to carefully consider the costs and benefits from your pipelines and reduce CI/CD usage to a mini…

This seems to have been written in good spirit, addressing FLOSS maintainers.

Re: GitHub to Codeberg: my experience

#84
post #50

Earlier quoted context omitted.

I like sourcehut. It's the only forge out there that isn't set out to copy the Github UI like everyone else. And its UI itself feels instantaneous, as if it was running locally.

The UI is fast, but it can be difficult to navigate, at least if you aren't familiar with it. In particular, unless it is explicitly mentioned in the README, it isn't at all clear how to report a bug, or submit a patch, or view relevant mailing list archives.

> In particular, unless it is explicitly mentioned in the README, it isn't at all clear how to report a bug, or submit a patch, or view relevant mailing list archives.

Those are meant to be mentioned in the README. Each of sourcehut's parts including the repo frontend, project page, mailing list, task list, documentation pages, etc are independent. There is no predefined way in which these are associated with each other like on GitHub. For example, I use a single mailing list for all of my FOSS projects.

Re: GitHub to Codeberg: my experience

#85
post #4

Earlier quoted context omitted.

Ongoing availability issues, Microsoft's shoehorning of AI, GitHub's focus on migrating to Azure infrastructure rather than adding features and fixing shortcomings. If I had to guess.

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

Most people don't care about the AI being trained on their FOSS repos. If they did, they would have mass migrated when Microsoft announced it. The timing suggests that the downtime and the performance issues are definitely the irritants here.

This is not to say that people shouldn't care about AI training. I was disappointed by the public response when they announced it. The GH ToS has conditions that allow them to use your code, overriding its license. Even worse, that still applies if somebody else mirrors your code there from some other forge. And they don't stop at that. I have noticed that they just scrape off code from source registries like crates.io in the name of security. I would be surprised if they didn't use that too for training their AI.

Re: GitHub to Codeberg: my experience

#86

Earlier quoted context omitted.

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

Unfortunately it's most ActivityPub-oriented, right? Which means no name portability. That's a major shortcoming compared to an AT protocol-based thing like Tangled appears to be.

Re: GitHub to Codeberg: my experience

#87

Earlier quoted context omitted.

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 le…

This is why CI should be separate from code repository storage and that should be separate from your collaboration tools. They all can speak git if you want.

> This is why CI should be separate from code repository storage

Maybe, but for any complex project you get stuck with dependencies between various code branches and various CI repo branches anyway, so I’m not sure how much easier it really is to manage that complexity rather than just putting the CI code in your repo so that the CI dependencies are explicit.

Re: GitHub to Codeberg: my experience

#88
I have once migrated my repositories to Codeberg, but have moved back to GitHub.

While I despise a lot of features on GitHub, Codeberg is sadly lacking the gravitational pull and visibility. I know, someone has to start, but as a single maintainer I need collaboration to keep the projects alive.

Re: GitHub to Codeberg: my experience

#89

The author‘s reasons seem sensible ( https://eldred.fr/blog/codeberg/ ) But I'm sort of disappointed the end result doesn't seem like it's any better for users? (not blaming the author) The benefits for the maintainer are also mostly philosophical... Which is a shame I just tried Codeberg - I get constant "Making sure you're not a bot!" anime girls - The login with Github is hidden behind a minuscule drop down arrow.…

> I get constant "Making sure you're not a bot!" anime girls

That's Anubis:

https://anubis.techaro.lol/

There is an unbranded version available, allowing image customisation under a paid tier:

https://anubis.techaro.lol/docs/admin/botstopper

The only other one I've seen deployed out there in any wide capacity is Cloudflare's.

Makes sense that Codeberg favoured an open and non-centralised solution.

Re: GitHub to Codeberg: my experience

#90
post #86

Earlier quoted context omitted.

FWIW, Forgejo (Codeberg) is also building federation capability [0]. [0]: https://codeberg.org/forgejo-contrib/federation/src/branch/m...

Unfortunately it's most ActivityPub-oriented, right? Which means no name portability. That's a major shortcoming compared to an AT protocol-based thing like Tangled appears to be.

Nostr would being better. As it is truly free vs AT protocol is backed by VC.
Post reply on HN