Gnome has moved to GitLab
41–50 of 212 posts
Re: Gnome has moved to GitLab
#42Earlier quoted context omitted.
The CADT model strikes again!
All Of this has happened before and will happen again: https://www.jwz.org/doc/cadt.html Makes me wish I had seen JWZ's writeup before spending so much of my time filing the damned things.
Re: Gnome has moved to GitLab
#43Earlier quoted context omitted.
By committing to use GitHub, you’re only really committing to git. git supports multiple remotes for the purposes of mirroring — use that feature .
> you’re only really committing to git You don't use github just for git. You use it for issue tracking, pull requests and code review, CI hooks, wiki, github pages, kanban boards, bot integration, and so on. That's all stuff that locks you in to Github, and is non-trivial to migrate to another provider.
The idea that it’s GitHub locking you in rather than you locking yourself in to GitHub is the argument I take issue with. But no quarrel at all with Gnome choosing GitLab, because GitLab is genuinely great.
Re: Gnome has moved to GitLab
#44Earlier quoted context omitted.
All Of this has happened before and will happen again: https://www.jwz.org/doc/cadt.html Makes me wish I had seen JWZ's writeup before spending so much of my time filing the damned things.
jwz links don't work from Hacker News. They will get redirected.
Re: Gnome has moved to GitLab
#45Re: Gnome has moved to GitLab
#46Unrelated, but GitLab has a pretty slick cookie notice. Tells you exactly what they're doing and lets you opt out of non-essentials.
Re: Gnome has moved to GitLab
#47Earlier quoted context omitted.
By committing to use GitHub, you’re only really committing to git. git supports multiple remotes for the purposes of mirroring — use that feature .
> By committing to use GitHub, you're only really committing to git. Make sure you also tell your users not to use GitHub's comments, issue tracking, pull requests, release system, favorites/watches, or authentication. So you're suggesting that the new home for the GNOME project's code be GitHub, without the GitHub.
Please try to be more careful with how you approach reading comments.
Re: Gnome has moved to GitLab
#48Earlier quoted context omitted.
All Of this has happened before and will happen again: https://www.jwz.org/doc/cadt.html Makes me wish I had seen JWZ's writeup before spending so much of my time filing the damned things.
jwz links don't work from Hacker News. They will get redirected.
Re: Gnome has moved to GitLab
#49… and closed about a bazillion bugs I filed over the years in the process without (apparently) migrating them, too. … though I am pretty sure they left the bugs in the source intact.
It's not like gnome was utilizing bugzilla anyways. They had one bug that was 11 years old.
So the only conclusion you can really draw from "one bug was 11 years old" is that they had been using that issue tracker for at least 11 years.
Re: Gnome has moved to GitLab
#50Earlier quoted context omitted.
As others have pointed out, this is Gitlab. When it comes to github, they previously helped me transitioning a bugzilla into github issues, but it doesn't look like they do this anymore. Back then, I managed to get approval from all our contributors/issue authors so that their individual bugs and comments would show up as their individual bugs and comments, as well as retaining issue numbers. This is the code for it,…
There's an unofficial issue import API: https://gist.github.com/jonmagic/5282384165e0f86ef105 But it doesn't let you change ownership of issues or comments; everything appears as created by the importing user.