Live data from Hacker News

Gnome has moved to GitLab

about.gitlab.com

181–190 of 212 posts

Re: Gnome has moved to GitLab

#181

… 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.

Everyone on the CC list for each bugzilla bug was notified 6 months ago that any bug without action in over a year would be frozen instead of migrated. (Do keep in mind that GNOME, unlike corporate projects, is largely volunteer based and time, resources, and contributors are limited) As the email said, you just needed to ACK a comment on the bug to keep it alive and ensure its migration. Given the nearly 900,000 bug…

There were bugs that the Gnome devs refused to fix even with patches. And not stupid patches, but reasonable ones.

Re: Gnome has moved to GitLab

#182
post #161

If only all of the energy spent on Gnome bashing would be spent on bugfixing, we'd have a perfect Gnome desktop by now. It's sad.

It would be GNOME 98 and consist of a single shutdown button. Perfect feature minimalism and usability. It would also randomly crash when the button is clicked.

Re: Gnome has moved to GitLab

#183
post #114

Earlier quoted context omitted.

It's logical of course, but I see the irony. Or maybe it's not irony, nobody really knows what irony is, but it's mildly.. amusing? It makes half my face smile in a manner similar to but not quite like a smirk.

Is the Git project expected to uproot themselves and go chasing Github or Gitlab or Gogs or whatever else is fashionable?

Of course not.

Re: Gnome has moved to GitLab

#184

Was Github ruled out because it's not free enough in spirit or are the Gnome folks just wanting to run things on-prem?

Probably because Github is a closed-source company that can remove you, your repo, or your group at any time, for any reason. Committing to a hosted service is a bad idea (see: Sourceforge). That sort of thing isn't acceptable to a project like Gnome.

Possibly more important than any practical implications of GitHub being closed source is the simple fact that relying so intimately on a closed source product would be a really bad look for them, on account of what the first letter in GNOME stands for.

Re: Gnome has moved to GitLab

#185

Earlier quoted context omitted.

Everyone on the CC list for each bugzilla bug was notified 6 months ago that any bug without action in over a year would be frozen instead of migrated. (Do keep in mind that GNOME, unlike corporate projects, is largely volunteer based and time, resources, and contributors are limited) As the email said, you just needed to ACK a comment on the bug to keep it alive and ensure its migration. Given the nearly 900,000 bug…

I wish it was that simple, but I never received a single notice of the migration or my need to do anything at all as a bug reporter. (Just ran a liberal grep on my inbox right now.) The only notice I received was after-the-fact. Sorry. Learning of GNOME'S cavalier attitude toward user reports and eventual product direction was exactly why I moved off the platform in the intervening years. I had high hopes when I was…

Bug reporters who can't even be arsed to follow up or check in on their reports aren't worth nearly as much as you seem to think they are.

Re: Gnome has moved to GitLab

#186
This is very annoying because I can no longer see the list of bugs I filed against GNOME products. They are all owned by 'bugzilla-migration', not me!

[additional] I appear to be subscribed to the issues that I filed in Bugzilla and were migrated to GitLab, but there's no way to get a list of all the issues I'm subscribed to: https://gitlab.com/gitlab-org/gitlab-ce/issues/12697

Re: Gnome has moved to GitLab

#187

Earlier quoted context omitted.

I wish it was that simple, but I never received a single notice of the migration or my need to do anything at all as a bug reporter. (Just ran a liberal grep on my inbox right now.) The only notice I received was after-the-fact. Sorry. Learning of GNOME'S cavalier attitude toward user reports and eventual product direction was exactly why I moved off the platform in the intervening years. I had high hopes when I was…

Bug reporters who can't even be arsed to follow up or check in on their reports aren't worth nearly as much as you seem to think they are.

True, but on the other hand bugs can go unfixed for years, with developers ignoring them or prioritizing them super ultra low. I know I've opened enough bug reports over the years that I can't go back and check on all of them, but I'm still hoping they'll get fixed some day.

If it's closed for "inactivity" while I'm actively waiting for a response from the developer, that's going to annoy me.

Re: Gnome has moved to GitLab

#188

Earlier quoted context omitted.

I wish it was that simple, but I never received a single notice of the migration or my need to do anything at all as a bug reporter. (Just ran a liberal grep on my inbox right now.) The only notice I received was after-the-fact. Sorry. Learning of GNOME'S cavalier attitude toward user reports and eventual product direction was exactly why I moved off the platform in the intervening years. I had high hopes when I was…

Link for Jwz's cadt post https://www.jwz.org/doc/cadt.html (edit: I didn't see it was already posted below)

Quick reminder: JWZ despises HN, so you'll need to copy-paste that link in order to remove the referrer header.

Re: Gnome has moved to GitLab

#189

Earlier quoted context omitted.

Link for Jwz's cadt post https://www.jwz.org/doc/cadt.html (edit: I didn't see it was already posted below)

Quick reminder: JWZ despises HN, so you'll need to copy-paste that link in order to remove the referrer header.

I'm not saying the bridge has been repaired, but clicking that link doesn't seem to redirect to... THAT... image any more.

Re: Gnome has moved to GitLab

#190

Earlier quoted context omitted.

> What's the relationship between the existence of a bug in the codebase and the propensity of the bug reporter to respond to an email? It's not clear to me the question here, can you be more specific? Many bugs filed are not necessarily bugs in the codebase. I do wish we treated bugs and user support separately. I rather prefer the terseness of an engineering journal for what it is, but that tends to anger those exp…

> I do wish we treated bugs and user support separately. Why not have a buck tracking system where only contributors have write access and a second system where users can submit their reports?

I oppose this sort of thing and rather encourage forming a strong QA team to separate the fluff from the real deal.
Post reply on HN