151–160 of 212 posts
Earlier 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.
Earlier quoted context omitted.
The whole blog post was made to sound like GNOME moved to gitlab.com, so I guess not including the link was intentional.
Mesa is also moving, but they explicitly mentioned it's a locally run instance of Gitlab, not gitlab.com.
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. 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? > Personally, I think a lot of bugs in Bugzilla were just left open instead of closed due to a difference of opinion/vision but diff…
> 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…
Right. So your goal is to separate reports about bona fide bugs in the codebase from reports that either a) are no longer bugs in the codebase or b) are issues outside the scope of the codebase. That's a laudable goal.
Filtering out years of bugs based on the lack of timely response from a submitter (or others) doesn't seem like a sound way to achieve that goal. There's no clear relationship between a lack of response and the relevant bug's existence/non-existence.
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. 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? > Personally, I think a lot of bugs in Bugzilla were just left open instead of closed due to a difference of opinion/vision but diff…
> 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…
Earlier quoted context omitted.
Probably the infamous "thumbnails in file picker" bug that is a meme on 4chan's /g/: https://wiki.installgentoo.com/index.php/File_Picker_meme https://bugzilla.gnome.org/show_bug.cgi?id=141154&
But that's not a bug. It's a feature request
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?
git makes it even possible to host a repo on multiple git* hostings, but apparently nobody came up with a successful distributed pullreq/issue tracker yet.
Earlier quoted context omitted.
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.
I feel like this is unfortunate. Github has a giant user-based, and using github would be a great way to reduce the friction of having first-time contributors submit a pull-request. In my case, if KiCAD were hosted on github, I would have already contributed by now. I think its a shame that more of these projects don't adopt a strategy of "let's try github, and if they screw us over, then we'll migrate to a platform…
I suppose it's useful never to underestimate the role of culture and tradition when it comes to these things. For the Gnome project, it's probably very important not to rely on a closed-source system, and their developers have a long history of using very different tools anyway.
The barrier doesn't work that way for everyone, either. I "grew" up (programming-wise) before Github. It seems way less cumbersome for me to make changes and submit a patch via email or whatever than to go through Github's fork the repo - do the changes - make a pull request - sync the repos dance.
(Edit: this is especially true for early contributions, or for late and complex contributions, where the review process is a little more, you know, long-winded. Github's review tool is quite atrocious.)
> I think its a shame that more of these projects don't adopt a strategy of "let's try github, and if they screw us over, then we'll migrate to a platform with more freedom".
That's a really risky thing to try. First, moving the entire infrastructure to Gitlab has been a pretty massive undertaking for Gnome -- and Gnome is one of those open source projects that really has resources. Most projects with Gnome's size and history can maybe afford to do that once every seven years, when there's a relatively quiet time and whatnot.
Second, you never really know how that "screw us over" thing is gonna happen. What if the way it happens is that, among other things, when they close your repos or whatever, they cut access to the API for your project? How are you going to migrate to a platform with more freedom then? Copy-paste every bug report ever?
IMHO, 10-15 years from now we'll be really happy that Gnome really understood that "there's no cloud, it's just someone else's computer" thing :-).
Was Github ruled out because it's not free enough in spirit or are the Gnome folks just wanting to run things on-prem?
Gitlab has an open source version [2], which means that preferring Gitlab over Github prevents giving more control of the project's direction to another entity. ( Not speaking on behalf of GNOME of course, just remarking that it is a good thing that free software projects are preferring Gitlab over Github )
… 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…
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 young and naive.
I realize GNOME is volunteer-based with a pillar of corporate backing from Red Hat and similar, but it strikes me as botched that if enough will existed to migrate to GitLab, an endeavor that requires serious engineering hours of research and planning and execution, that nobody could have said: let's query and build a list of unique email addresses from bug reporters and personally email them once with a quick letter, letting them know what they need to do. Compared to the actual migration, that is drops in a bathtub. Simple due diligence for user-facing goodwill.
I want to be sympathetic — really.
JWZ's CADT supposition has a lot of explanatory power here combined with the opportunity to "scrub a lot of bugs quickly".
Earlier quoted context omitted.
I find these GDPR notices useful. Obviously every website use cookies, but it's nice to know what these cookies actually do. I've already encountered a few news websites listing 100+ advertising/targeting companies whose cookies they use. That was quite eye-opening. I also appreciate all the GDPR emails that landed in my email box recently. I've replied to about every second of them asking for my account/data to be e…
Apparently, Tumblr shows more than 300 [1] [1] https://gdprhallofshame.com/22-to-continue-to-use-tumblr-ple...