Post B6FWyMgxvMhSrYHCYS by janl@narrativ.es
(DIR) More posts by janl@narrativ.es
(DIR) Post #B6DckGo3DmchxmKhu4 by mntmn@mastodon.social
0 likes, 0 repeats
the developments at gitlab feel unsettling. we have all our sources in a self hosted gitlab since a long time, and migrating to i.e. forgejo would be a big undertaking, with the tons of deeplinks from our docs into the repositories, a bunch of tricked-out CI yamls etc. and we're under a lot of pressure to ship hardware atm, so i can't pick that battle right now :/
(DIR) Post #B6DcowcjgdswofGlWq by flaki@flaki.social
0 likes, 0 repeats
@mntmn 💜
(DIR) Post #B6Dcsu4t5uyk4vKCvI by mntmn@mastodon.social
0 likes, 0 repeats
(referring to https://about.gitlab.com/blog/gitlab-act-2/)
(DIR) Post #B6DdLtXOBMWUnhTqKm by pmdj@mstdn.social
0 likes, 0 repeats
@mntmn Yeah, for CI in particular, Forgejo doesn't seem anywhere near as flexible as GitLab yet. For our purposes, I may just have to put our GitLab instance behind a VPN and freeze its version to a reasonable one indefinitely. Set up Forgejo and get the repos mirrored across the 2 systems, then start gradually moving tasks/issues etc. and eventually tackle the CI situation.
(DIR) Post #B6DdqaCy69uxpRYuCu by janikvonrotz@fosstodon.org
0 likes, 0 repeats
@mntmn Maybe go half way? The tricky part when moving from gh or gl to forgejo is rebuilding the ci/cd infra. Replacing this part is the hardest and also feels like the least important.
(DIR) Post #B6DpwLL3UjxatnrF32 by DamonWakes@mastodon.sdf.org
0 likes, 0 repeats
@mntmn It's never a good sign when someone begins communicating in listicles.
(DIR) Post #B6Dsymlamy1OPJ7tuy by PaulaMaddox@mastodon.social
0 likes, 0 repeats
@mntmn oh god that’s bad especially this quote “Software will be built by machines, directed by people. AI is the substrate on which future software gets built.”So wrong, so very very wrong.
(DIR) Post #B6Dw01tSKhAzTT5bPM by updn@chaos.social
0 likes, 0 repeats
@mntmn With even just the most basic knowledge of process design, it should be obvious that "rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs" is nothing short of flushing all of the meticulous work that went into organising your organisation down the metaphorical toilet. In other words, leadership is toast and it's only going to get worse for everyone else. A sad sight...
(DIR) Post #B6DwaFjWM1lMp3iNkG by mntmn@mastodon.social
0 likes, 0 repeats
@updn yeah i cannot understand how someone can seriously do this...
(DIR) Post #B6E2fDqNPETq8SfsHI by riaschissl@sigmoid.social
0 likes, 0 repeats
@mntmn I think we've been using a local GitLab CE instance for over a decade now and have only recently added a Forgejo deployment for some projectsApart from the fact that Forgejo is simply brilliant - it is - migrating these projects from GitLab to Forgejo wasn't too difficult. The key is to script the entire migration and use the REST endpointsPipelines are a different story, but as Forgejo's actions are GitHub compatible, it's not too hard to find plenty of documentation on how to do it.
(DIR) Post #B6FWyMgxvMhSrYHCYS by janl@narrativ.es
0 likes, 0 repeats
@mntmn you could apply for funding a migration at the STA. We’ve done a large docs merge/migration for systemd with them. Ama. 😘
(DIR) Post #B6FXQvU69zhksUsQsK by shaadra@mastodon.gamedev.place
0 likes, 0 repeats
@mntmn I feel like the writing has been on the wall for a while with GitLab. Open core is not a good model for FOSS in my book.I moved my personal projects to Codeberg recently. It was annoying to have to spend the time doing that, but I'm glad it's done.Sounds like the deep links are the kind of extra pain poin you'll have to deal with. On the plus side, self hosting forgejo is a breeze compared to GitLab. I've hoste both at $DAYJOB and forgejo is far easier.
(DIR) Post #B6FYTW2xIGh4o5yo6K by mntmn@mastodon.social
0 likes, 0 repeats
@janl ohhh, that sounds extremely interesting