It continues to strike me that now, almost 4 months after last commit on any #github project, including #inxi, gh users keep starring my gh repos, even though all of them clearly state that the code is migrated to @Codeberg in the README, which is why I got sick of gh users, they don't read as a whole, and tended to post annoying issues. The users who read, tend to post good issues. that's what I see on codeberg smxi repos now. Not perfect, nothing is, but better. So happy with switch.
The sad and hilarious thing is that computer nerds already control the means of production they're just not doing anything with it other than what they're told.
@mhoye Then, they opted for #github to host their code, they built it around Github's CI/CD. They adopted #copilot. Ah, they also built their community on #discord and release their work on centralized proprietary platforms (e.g. #googleplay). Now, they own nothing.
Does anyone out there have experience with GitHub build workflows for macOS apps that include codesigning and notarizing the app? I'm having some trouble with setting mine up and I don't know what to do at all 😖
Krita is a KDE project which hosts its development on a KDE GitLab instance. They also have a GitHub mirror repository.
The GitHub mirror is starred by 6.5k accounts. Their GitLab repository is starred by 75 accounts.
And their ticketing system is Bugzilla. Which I greatly disliked before, but I don't even see an obvious way to search for issues by text filtered to the Krita project.
I think it's a shame they evade GitHub as a platform for contributions. It certainly makes me give up contributing to it. Even on issue tickets.
I moved all my private and public repositories from #github to #gitlab and I must say I’m happy with that change. I love how smart the pipelines are - much cleaner code for CICD than with Actions. The only problem I see for now is the fact that adding #mastodon to the GitLab profile doesn’t add the rel=me, so it doesn’t show as green on my profile here.
Worth noting that some Jia Tan commits to #xz were made with the github web interface. You can tell because they are signed by a gpg key github uses for web edits (4AEE18F83AFDEB23).
The most recent one is 62efd48a825e8f439e84c85e165d8774ddc68fd2.
So if #Github keeps logs since January, they might have IP address information or other info.
Lasse Colin posted an update on the #xz#openssh backdoor situation. It doesn't give a lot of details, but still useful as a primary source of information.
TL;DR: Damage control is underway in the project, but it's been somewhat inhibited by #Github taking it down and suspending Lasse's account.
Hey it's totally cool that #Microsoft#GitHub blocked access to one of the repositories in the very center of the #xz backdoor saga. :blobeyes:
It's not like a bunch of people are scrambling to try and make sense of all this right now, or that specific commits got linked to directly from media and blogposts and the like. :blobcatcoffee: