Das ist so feist, dass meine Abteilung jetzt doch vom eher etwas rudimentären Mattermost-Kanban zum Gitlab-Issue-Management umgezogen ist.

Sehr schön auch, dass alle in der Abteilung damit einverstanden waren, dass alle aus dem Haus mit Gastrolle (erlaubt Kommentare in Tickets und Mentions) alles sehen dürfen. So eine Haltung ist nicht selbstverständlich.

Das macht so Spaß.

Quelqu'un peut m'expliquer comment publier mon site sur #gitlab pls ?

Heh, you can add emoji into #GitLab labels.

Mon client aimerait bien que je fasse la formation " GitLab CI/CD, maîtriser la gestion du cycle de vie de vos développements logiciels".
Et moi j'aimerai bien la faire à Grenoble (et les dates de la session distanciel c'est pas possible).
Pr le moment, la session de Grenoble n'est pas confirmée parce qu'on est pas assez nombreux/nombreuses. (il manque 1 personne)
Donc je jette une bouteille à la mer, si votre poste nécessite une formation Gitlab (et que votre employeur a le budget), c'est par là bas: https://www.orsys.com/fr/formation/formation-gitlab-ci-cd-gestion-du-cycle-de-vie-des-developpements-logiciels.html
Venez nous rejoindre, pr qu'on s'évite un fastidieux déplacement à Paris.
#grenoble #gitlab

Do you know a web app to show combined contributions in different code forges or code hostings?

Like I could check sum of contributions in various Forgejo instances(like Codeberg), Github and Gitlab.

If you don't know a webapp, boosts are appreciated.

Crisis averted, #GitLab reopened the epic on #ActivityPub / #ForgeFed implementation. :)

They made it clear, though, that they're not going to do it themselves in any foreseeable future, their "current focus isn't in this area", so it's up to the community to implement it. As I mentioned in the issue, I won't be able to come back to it until I'm done bootstraping the business I'm working on, so anyone who wants to see it done faster should feel free to jump in.

https://gitlab.com/groups/gitlab-org/-/epics/11247#note_2603598572

Ah, zut, #Gitlab laisse tomber l'idée d'intégrer #ActivityPub https://gitlab.com/gitlab-org/gitlab/-/issues/30672

#Gitlab just closed the issue about supporting #ActivityPub. Kai Armstrong says "our current focus isn't in this area".

This is very sad, I really think this could have been a pretty good match *espacially* for Gitlab. It could have been a puzzle piece in how to do federated open source coordination. You know, the problem with "not wanting to be on github, but kinda finding it convenient everyone has an account already".

https://gitlab.com/groups/gitlab-org/-/epics/11247#note_2597450590

#Gitlab just closed the issue about enabling federation using #ActiviyPub that has been open since 2019
https://gitlab.com/gitlab-org/gitlab/-/issues/30672#note_2597293301

Comme après tous les 3e jeudis du mois, il y a une nouvelle version de #Gitlab, donc interruption de service pour #Framagit dans quelques minutes.

Pour voir les nouveautés : https://about.gitlab.com/releases/2025/06/19/gitlab-18-1-released/

Spent an absurd amount of time searching for the "update fork" button on #gitlab's web interface.

Why? Because it turns out you can only see it if you are in landscape, in portrait view the button simply does not exist...

Anyone who has upgraded their self-hosted #Gitlab instance to 18.x might want to check their admin settings and potentially disable "Event tracking":
https://about.gitlab.com/blog/2025/03/26/more-granular-product-usage-insights-for-gitlab-self-managed-and-dedicated/

I'm finally moving over to Radicle (https://radicle.xyz) instead of switching to another centralized code forge (like GitHub, GitLab, Codeberg, etc.). I definitely love the idea behind a #P2P code forge and I'm hopeful for Radicle's future, but I do have some reservations starting off:

1) Despite talking a lot about freedom and privacy in the tutorial, the group building Radicle (https://radworks.org/) is planning to sell hosting and make a profit via an Ethereum-based cryptocurrency (https://www.tally.xyz/gov/radworks) as well as NFTs and smart contracts. Some big Libertarian red flags there.

2) At some point there was a Swiss nonprofit "Radicle Foundation", but this now seems to be a for-profit venture (see https://radicle.xyz/history). I wish it could just be a nonprofit.

3) In the user guide chapter on private repos (https://radicle.xyz/guides/user), it says that I need to use a public DNS address trusted seed node to share the repo. I understand there's no DHT here, but I hope it's not too much of a pain to run this over my local network instead of the internet. (And yeah, I know I can use git locally, I just want to test Radicle locally.)

Overall, I think that if radworks turns out to be evil it will be a way easier transition to fork Radicle than it has been to leave GitHub, but I still wish I didn't have to worry.

I've started migrating my repos from Codeberg to Worktree.ca; I'll keep the Codeberg repos as mirrors.

Doing this because Worktree is Canadian, and I subscribe; I felt a little bad using a non-profit's infra even though all my stuff there is open source and my CI needs are pretty minor.

EU folks: Codeberg.org is great (Forgejo).

CA folks: Worktree.ca is great (Gitea).