sueden.social ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Eine Community für alle, die sich dem Süden hingezogen fühlen. Wir können alles außer Hochdeutsch.

Serverstatistik:

1,8 Tsd.
aktive Profile

#gitlab

9 Beiträge9 Beteiligte0 Beiträge heute

I have now also converted my remaining personal open source Git repositories (those which we don't already host at the institute's #Gitlab instance and which are not forked from or contribution to others) from #Github to #codeberg codeberg.org/rmayr

Github was a great improvement to make open source contributions and coordination easier, and it's a shame that the current AI hype drives everything into a single, non-sustainable niche direction... While Github is dependent on Microsoft AI stuff, my repositories are archived and will not see any further changes - I might even delete them altogether.

Codeberg.orgRené MayrhoferCodeberg is a non-profit, community-led organization that aims to help free and open source projects prosper by giving them a safe and friendly home.

"Patches sent to distribution lists remains the only widely used decentralized code review framework. RFC2822-conformant (“email”) messages adhere to an established standard that ensures high level of interoperability between systems, and it remains one of the remaining few truly decentralized communication platforms."

This!

(source: b4.docs.kernel.org/en/latest/m)

b4.docs.kernel.orgMaintainer overview — B4 end-user docs documentation
#git#email#enshittification
Antwortete im Thread

@ross

@Codeberg is great, and their hoster, #INBerlin, too.

But, please, don't make it the new #MSGitHub, i.e. don't centralize all #freeSoftware on it. It is important to have various servers, not all eggs in one basket, also for #resilience against #cyberattack or #censorship.

If you can, think about #selfHosting #forgejo, #gitea, or #gitlab. If not, take a look at #sourceHut or #Salsa.debian.org, too. The latter is not only for #Debian stuff! 🙂

So, if I wanna leave GitHub and I need private repositories, where do I go?

GitLab's CEO has been problematic in the past.

Codeberg doesn't support private repos.

What other options are out there?

Do I just self-host my own git server and be done with it?

I currently (sorta) use GitHub's boards for "planning" purposes, but that's not like a hard requirement since I can get that elsewhere if I really want to.

I'm currently planning my #GitHubExit and I am wondering what the best option is to make my repos still discoverable but not in the hands of Microsoft (at least from now on).

A) Should I just add a hint to the readme and archive the repo?
B) Delete the git history and just add one commit with the new URL in the readme?
C)Delete the whole repository?
D) something different

:boostRequest:

Fortgeführter Thread

The forgefed.org developers are extending the specs, and asking for feedback in the issue trackers on #Codeberg, but none is forthcoming.

As a result large crowds root for @forgefed #forge federation to come along, but it will not happen anytime soon at the current pace.

@nlnet through #NGI0 provide funding to #ForgeFed, #Vervis, #Anvil, and also #Forgejo and these people are bravely forging ahead. More community help is needed though.

Same is true for #Gitlab's federation efforts.

forgefed.orgForgeFed

If you rework commits for an already published merge request to update it on a forge like #codeberg, #gitlab or github please consider using

git rebase -i $(git merge-base main HEAD)

instead of plain `git rebase -i` .

This avoids moving your commits to the tip of main thus easing review as the diff between revisions won't contain unrelated changes that were added to main in the meantime.

A malicious Jira ticket can cause Cursor to exfiltrate secrets from the repository or local file system. But this is not just a problem with Cursor: GitHub MCP connections can also be exploited to expose private repository data, and a vulnerability in GitLab Duo allowed private information to be exposed through automatically rendered HTML code.
labs.zenity.io/p/when-a-jira-t
#Jira #Cursor #GitHub #MCP #GitLab #ITSecurity #Vulnerability

Zenity LabsAgentFlayer: When a Jira Ticket Can Steal Your SecretsTL;DR: A 0click attack through a malicious Jira ticket can cause Cursor to exfiltrate secrets from the repository or local file system.