13 ms·
Remember when people tracked bugs?
- hotbot2 14y agoSet your User-Agent string to "Mozilla/5.0" and try to access jwz's site. I thought he was smarter than to make stupid assumptions. Is he ever going to fix this (bug)? Doesn't look like it. Maybe the assumptions are left over from his experience with Netscape? There's no RFC I know of that requires some silly user-agent string scheme. But feel free to enlighten me.
- rwmj 14y agoWhy is it jwz's responsibility to fix something when you have deliberately set up your browser to report the wrong thing?
- brudgers 14y agoTANSTAAFL.
- raldi 14y agoMaybe we need a feedback-responsiveness rubric for open source projects, websites, even whole organizations, and a site which issues them A+ through F grades based on the score.
- davidw 14y agoImageMagick: try GraphicsMagick instead - the maintainer is a nice guy and seems pretty responsive.
- rst 14y agoDiscussed in the comments on jwz's post, where several people say claims of ImageMagick's death are greatly exaggerated, and it has actually fixed bugs that still exist in GraphicsMagick.
- lazyjones 14y agoThey still do - just not for shitty projects. To see how this is done properly, check out for example: 1) Go language issues: https://code.google.com/p/go/issues/list https://code.google.com/p/go/issues/list (I had a bug fixed within 9 minutes after posting a few days ago!) 2) the PostgreSQL mailing lists (see other submission regarding "Tom Lane writes a lot of emails")
- ianfernz 14y agoTotally feel you on the PostreSQL comment. I am very impressed by the dedication that's apparent in that process.
- imglorp 14y agoUm, with (2) you're kind of supporting Jamie's point because PostgreSQL's bug system has plenty of drawbacks. While yes there is an outstanding and responsive community, its cultural bug knowledge is stored in a mailing list here: http://www.postgresql.org/support http://www.postgresql.org/support. Greg at End Point thrashed this system better than I can, two years ago: http://blog.endpoint.com/2011/05/postgres-bug-tracking-help-wanted.html http://blog.endpoint.com/2011/05/postgres-bug-tracking-help-... (TLDR: no metadata, no workflows)
- ordinary 14y agoTom Lane writes a lot of emails For reference: https://news.ycombinator.com/item?id=5171284 https://news.ycombinator.com/item?id=5171284
- danielweber 14y agoIf you mean only the very largest projects, or projects with corporate support, can handle the open source model, that's not very re-assuring about the future of open source. Also, it sucks when I need to sign up for something to report a bug.
- dmethvin 14y agoIt sucks when you run a bug tracker and it's spammed relentlessly because you allow anonymous comments. It sucks when someone files a legit bug anonymously and there's no way to reach them for followup or clarification.
- smackfu 14y agoEspecially dislike when the only point-of-contact is twitter.
- mainguy 14y agoHow about volunteering to run the bug tracking for the project?
- mainguy 14y ago'cuase I gave up on a couple open source projects I started because bug tracking and feature request tracking was eating up a lot of time and taking away from coding (or even fixing bugs).
- NelsonMinar 14y agoYeah, what has jwz ever done for open source? </heavyirony>. The solution to "this thing is broken" can't only be "fix it yourself".
- iomike 14y agoThat's what I use to get from Mozilla forums. Then I moved the company off of any Mozilla tools since we could get help on our issues. Been almost 10 years back, so not sure if it's still the case.
- Turing_Machine 14y agoIt isn't "you've already given me a bunch of your time, so now you owe me even more", either.
- smackfu 14y agoI think that's missing the point... you can either provide an easy way to report bugs (for instance email is the easiest) or you can say the project is no longer being maintained. The complaint is about projects that insist they are being maintained but have no way to report bugs. That seems like a concious choice on the maintainer's side, not just a lack of volunteers.
- kevingadd 14y agoHow's he going to volunteer to run the bug tracker when the project maintainers don't respond to email?
- cryptoz 14y agoI use GitHub to track issues for pressureNET. When I find a bug, I log it there. Others have logged bugs there too. I pay attention and respond to every user who reports something is wrong, fix the bugs as fast as I can and send out the updates. Updating pressureNET causes a significant drop in measurements per hour since the update stops the old code. So I lose data when I fix bugs. But I still track them and still fix them because improving the software is important. Don't rant and be rude to all open source projects because you're obsessed with a few poorly run projects. Open source is in a better position than ever when it comes to developer accountability and bug fixing.
- logn 14y agoRemember when you paid for software?
- npsimons 14y agoYes, last year for Debian DVDs. Also, AGit (https://play.google.com/store/apps/details?id=com.madgag.agit&hl=en https://play.google.com/store/apps/details?id=com.madgag.agi...) and MobileOrg (http://mobileorg.ncogni.to/ http://mobileorg.ncogni.to/), etc. Your point . . . ?
- danielweber 14y agoI took his point as either 1. if people would just accept that they need to buy software, it would be easy to charge for it, and it would be easy to support it 2. "hey, it was free, ass-wipe" [1] Either way I approve. [1] http://www.youtube.com/watch?v=3Y8x5hbdaPM&feature=youtu.be&t=5m30s http://www.youtube.com/watch?v=3Y8x5hbdaPM&feature=youtu...
- npsimons 14y agoNeither one of those points is necessarily true. Especially point the first, where margins on software were ridiculously inflated by certain companies, with no discernable change in software quality. Just as one example, apparently paying $59 for something that should have already worked, that you already paid for, doesn't mean it will be fixed: http://toddsnotes.blogspot.com/2009/11/microsoft-genius-error-occurred-while.html http://toddsnotes.blogspot.com/2009/11/microsoft-genius-erro... As for the "ass-wipes can't be choosers" argument, that's just flat out unprofessional. If you were building a house for Habitat for Humanity, would you slack off and not hammer all the nails in because "hey, it was free, ass-wipe"? Maybe my point of view is skewed, because in one of the charities I volunteer for, doing something half-assed is fairly certain to get someone killed. I get that OSS isn't always someone's day job, they may not have enough time to handle bug reports or documentation, etc, etc. But as the solutions to supporting an OSS project go, ignoring bug reports or making them hard to file rank pretty low. If someone doesn't have the time to handle the load, they need to communicate that. Post it on the project page. Put out a call for help to other volunteers. Have the bug reporting system autorespond that the project is not moving very fast. At least let your users know where they stand.
- rthomas6 14y agoThis isn't the generalized case, is it? This is just a short list of open source projects to stop using/replace.
- jiggy2011 14y agoSounds like he's trying to report bugs in projects that are either dead,half-dead or just the work of one guy as a side project. Before you start using an OS project for anything serious, take a look at their forums, bug databases and repos. Is there active discussion from more than 2 or 3 people? Are there regular commits? How are they handling bugs? I've considered open sourcing code that I have written in the past, mainly stuff I built for one project where it serves the purposes of that project fine. In such a case handling bug reports from users trying to do different stuff with it would realistically just be a low priority. jwz rants always make me feel that the author is somehow bitter about the world not revolving around his needs.
- smackfu 14y agoThe problem is that ImageMagick was clearly the image handling software of choice for years and years. So you rationally build a solution on it, then you find a bug (often a regression caused by an upgrade), and then there is no support for it. That sucks, and changing to another project that happens to be well-supported this week doesn't really fix the core gripe.
- npsimons 14y agoI was about to say something similar; last I checked, ImageMagick was far from dead or "just one guy". As I was reading TFA, I was thinking "Okay, two projects I haven't heard of, might be one offs" but then his retelling of his experience with ImageMagick made me sit up and take notice. If it's really this bad, it might be time for someone else to take it over.
- plorkyeran 14y agoImageMagick has been just one guy ever since the GraphicsMagick fork in 2002.
- npsimons 14y agoAh, yes, seeing that now. I get them mixed up sometimes.
- methodin 14y agoSeems like we need more Open Source QA people to confirm bugs or gather missing info. Developers aren't necessarily capable of (for lack of want) or good at doing that.
- IgorPartola 14y agoWe need more QA people period. I have never met a developer that wanted to do QA work. The closest a developer will come to doing QA is automated testing. There is a reason for this. Doing QA is tedious and involves a lot of work which may not be particularly stimulating. OSS developers that produce quality software are fairly rare. OSS QA's are orders of magnitude harder to find.
- danielweber 14y agoIt's usually very hard to QA one's own work. You are trying to find out why you suck which is very weird. (I am currently testing the ever-living daylights out of a piece of open-source software I'm working on, but I inherited it from someone else, which I'm sure makes me more willing to find out how it handles.) I have no problem QA'ing other people's work. And, I have no problem when someone else finds bugs in my code. Maybe we need a QA-swap-meet.
- armored_mammal 14y agoThe reason we don't do much of it is that it's not viewed as a productive expenditure of dev time by management.
- philk10 14y agoDepends on your attitude and approach... I'm a dev that turned into a tester as I loved doing it and find it a great challenge. I'm currently helping test Wikipedia, enjoying it, so might go looking for other projects to help out
- CJefferson 14y agoI did quite a lot of QA for a large open source project (I don't want to pick on them, so I aren't going to name them). At first it is great fun, reducing testcases, talking to users, etc. However, the problem is that you still aren't a developer, and can't actually fix bugs. Also, because this is open source (and you are just a QA person), you can't direct what bugs you think need fixing most importantly. Those bugs lie open for months, making you (the QA person) look bad, but you obviously can't do anything about it yourself. When you complain, the obvious suggestion is "move into development, then you can fix bugs yourself". Of course, when you do that, you don't have time for QA any more. Therefore, good QA people usually either leave, or turn into developers. Do I have a suggested fix for this? Not really. We can't really demand that developers donating their time do what QA people donating their time tell them to do.
- ef4 14y agoOverall it has gotten much easier to report bugs and submit patches to open source projects, and I give that credit to Github. It comes down to friction: even if your system is better, it still means I need to learn your system before I can usefully contribute. If you're using a well-known system I'm much more likely to bother contributing back.
- IgorPartola 14y agoNo. It is as easy to ignore a pull request as it is to ignore an email. Here is an example of this: https://github.com/taichino/croniter/pulls https://github.com/taichino/croniter/pulls and https://github.com/taichino/croniter/issues https://github.com/taichino/croniter/issues There is nothing major in those pull requests/issues, but they are ignored. This project is great for what it does (lets you parse cron schedule input and gives you a datetime of the next execution), but the author seems to have abandoned the project. Now I am left with a difficult choice of using the project as is, or forking it and and making my own changes. If I fork it, I then have to monitor whether the upstream author shows up again and then I have to figure out what to do about his/her changes. If anything GitHub makes it easier for someone to half-ass a project and then abandon it as it is starting to get popular. Places like SourceForge had some vetting that may or may not have prevented this type of thing. GitHub works well for projects that have lots of contributors, but for a "small library that does X" it becomes a graveyard.
- kgo 14y agoYep. I think out of all the reports I've done on github, probably between 5-10% have gotten any answer, even if it was, "piss off!"
- tinco 14y agoYou make it sound like GitHub being a graveyard is a bad thing. Does this mean that you rather had Croniter not exist at all? It is simple, you see a project you like. If it has a bug you fix it in a fork. You use the fork until the project lead responds to your pull request. And if the project leads response doesn't suit you, you just continue to use the fork, you can pull from the original project whenever you like.
- jpswade 14y agoMaintaining Open Source projects is hard, especially if it's not funded by anything but your day job. You're likely to get a much better response if you make a donation.
- pdknsk 14y agoGoogle is very good in not acknowledging Chrome bugs filed by its users. http://notchromium.appspot.com/ http://notchromium.appspot.com/
- k3n 14y agoCorrelation doesn't imply causation. You can't honestly expect that John Q. Public is going to be as successful as a Chrome team member for getting a bug accepted; I've seen many of the bugs that get filed for Chrome, and I'd say a fair amount of them are by non-technical users. I'd be willing to bet that if you took any non-trivial project and ran the same metrics on the bug DB for developers vs. QA, you might get about the same results. When a dev puts a bug in, more times than not, it's a bug. But when QA puts one in, there's a very good chance that they're either mistaken about the expected functionality, or are reporting a bug that's already been fixed in trunk.
- simonsarris 14y agoThis frustrates me too. I've run into a laundry list of Browser (mostly canvas) bugs over the years, 95% in Chrome (my main browser) and 5% in Firefox. Typically they'd be ignored, fixed several months later if I'm lucky[1], and still ignored as they get closed by an automated bot[2]. Chrome specifically created an "icebox" to automatically close old bugs. I'm convinced that the Chrome team at least has an internal bug-tracker they use and the external one (crbug.com) serves the same purpose as fake thermostats on the walls of office buildings. (To Chrome's credit, they took the only security bug I filed very seriously and fixed it in a couple days.) [1] Unlucky: Still an issue with broken translating gradients in non-hardware-accelerated canvas: https://bugzilla.mozilla.org/show_bug.cgi?id=774387 https://bugzilla.mozilla.org/show_bug.cgi?id=774387 [2] This bug was ignored, fixed, and for a year I asked for it to be closed. It was finally closed by a street-sweeping bot: https://code.google.com/p/chromium/issues/detail?id=62373 https://code.google.com/p/chromium/issues/detail?id=62373
- js2 14y agoChromium has more bugs than devs to fix them all. There have been heated debates on chromium-dev about what to do about old bugs. Some devs think they should stay open till they are fixed, but given Chromium's development pace that doesn't necessarily make sense. So they close them, assuming if the bug is still relevant it will be reopened. One way they prioritize bugs (I believe) is by the number of times the bug has been starred. I do not believe they have separate bug databases. They do have the ability to mark bugs private, which afaik is only used for security issues.
- KaeseEs 14y agoThis is a slightly worse version of the behavior that prompted JWZ's first rant about bugtrackers in open source software (cf. http://www.jwz.org/doc/cadt.html http://www.jwz.org/doc/cadt.html ).
- js2 14y agoHere's the most recent discussion on chromium-dev I can find about it - http://thread.gmane.org/gmane.comp.web.chromium.devel/34134 http://thread.gmane.org/gmane.comp.web.chromium.devel/34134
- armored_mammal 14y agoI agree with you as a generalization, but imagemagick is pretty much known to be a deadbeat project. Give graphicsmagick a go. The maintainer is well known for working with people who have questions, bugs, and such (if you can forgive the continued use of SourceForge).
- alcuadrado 14y agoWho the hell ignores an email from jwz? That's even more crazy!
- martinced 14y agoWow. If jwz was to report a bug, even on a project I did write or maintain back in the days and that did since then fall into oblivion, I'd still get all excited! I mean, seriously, how can someone get an email / FB message / whatever from jwz and not even read the damn bug report!? This is beyond me. The guy knows what he's talking about. Long live jwz, thanks for all you did.
- danielweber 14y agoI think lots of people have no idea who jwz is. He doesn't have a github page so he must not exist. (Okay, he does have a github page, but nothing is on it, so he must be a newb.)
- jiggy2011 14y agoIf jwz reported a bug to me I'd tell him to go fuck himself , just to watch him rage.
- monochromatic 14y agoI'd probably play really dumb for awhile and string him along first.
- vacri 14y agoI've been banned from his site. He was bitching about trolls in the previous day's post. I reported that I read the thread, and I couldn't see the problematic comments, what was he on about? He replied that he'd deleted the posts (fair enough), then banned me. Nice one there, jwz, banning someone for reporting accurately on information that you know is incomplete for them. Amount of sympathy for his unanswered bug reports = 0.
- cookiecaper 14y agoSame sentiments here. jwz has been an industry hero to me for a long time. It's incomprehensible that an informed person, as I assume at least the imagemagick team has, can get a mail from him and choose to ignore it. jwz is an upper echelon guy.
- kreek 14y agoI think it depends on the project/author. First thing I check on a project is the commit history. Was the last commit a year and a half ago? Might be a clue :) I've reported bugs to bootstrap, d3.js, and fabric.js. Everyone was very responsive and each was resolved in at least two weeks. Actually with fabric I had bugs and feature suggestions which were implemented the next day!
- theallan 14y agoI run an open source project and I typically use github to track bugs, but I'm reluctant to have a dedicated bugzilla (or whatever) for the project as ~90% of bug reports are not bugs in my library, but rather installations issues or bugs in people's own code. I'm not saying my code doesn't have bugs(!) but what are often reported are bugs are nothing of the sort. It would be nice to have a bug tracker, but I just don't believe it would be used to track only bugs and would thus take up time which I'd rather use for developing the software.
- nswanberg 14y agoHere is how Jamie handles bugs for his software: http://www.jwz.org/xscreensaver/bugs.html http://www.jwz.org/xscreensaver/bugs.html
- ishkur101 14y agoThis seems very useful to me. I have struggled with a bug that I think is in Nouveau but I haven't reported it because im not sure what information would be required. This at least tells me what the dev requires to understand the issue.
- Someone 14y agoThat's not how he handles them, but more how he attempts to prevent to be flooded in issue reports. He might be very responsive if you use this way to report bugs or he might ignore them. That page does not tell anything about it.
- endgame 14y agoI see absolutely nothing wrong with that page.
- glass- 14y agoThat page reads like the sort of page someone might make after receiving hundreds of awful bug reports.
- howeyc 14y agoOh my. "This individual doing open source software FOR FREE is not fixing bugs that I provide to him to fix FOR ME AND MY NEEDS is not fixing them to MY SCHEDULE AND SATISFACTION. THE NERVE." Indeed. I feel for you.
- packetslave 14y agoThat's a lovely strawman you're beating on. If you actually read the post, jwz isn't complaining that bugs aren't being fixed on "[HIS] SCHEDULE AND SATISFACTION. THE NERVE." He doesn't say anything at all about bugs not being fixed. His complaint is that his bug reports are being completely ignored, and/or developers providing no way to even REPORT bugs. I imagine he would be happy (well, HAPPIER, it is jwz) if a project owner said/posted "this is a one-man show. I'm really busy and don't have any time at all to work on it right now. Here's a bugzilla/github issues/whatever where you can report bugs and at least see if it's a known issue"
- vacri 14y agoOne of the bug reports he's bitching about - the first one he mentions - is only 3 weeks old.
- packetslave 14y agoI'm pretty sure that's his point: that it has become acceptable to completely ignore a bug report for 3 weeks with no indication that it will EVER be looked at.
- vacri 14y agoI've worked as a dedicated software tester for a team of programmers and I've lodged bugs for them about the product that they're currently working on, that haven't had anything done to them in the system for that long. Sometimes there is other shit happening and that subsystem is on the backburner while it's sorted out. Or perhaps the coder responsible for that subsystem has been on holiday and is working through a backlog. Or perhaps their 'day job' has blown up on them and they haven't had quality time to look over things. I think jwz is just being precious here.
- slajax 14y agoSimple, don't use source that isn't maintained. And while your at it don't use terminal green on black for your website schema. Ouch my eyes.
- shurcooL 14y agoI don't think anyone saw this potential bug report for Sublime Text 2 either, because I made the mistake of posting it in a relevant context rather than starting a new thread. http://sublimetext.userecho.com/topic/52275-down-arrow-doesnt-make-cursor-go-next-line-if-text-is-selected/#comment_152988 http://sublimetext.userecho.com/topic/52275-down-arrow-doesn...
- geebee 14y agoThis may be a stretch, but do you think there is any chance that the decline of formal bug tracking may be related to the rise of automated unit and integration testing? Obviously, they are different things - I don't think that very good test coverage eliminates the usefulness of a bug database... but maybe it does make it easier to get away without one. Suppose you have a discussion forum, and someone sees a potential bug. In the past, they might add a bug report. Now, they go to their integration testing suite and write "URL shortener should provide valid menu links at navigation depth greater than three" (just to come up with a completely contrived example that never happens in real life, heh). This still tracks the bug, and is probably more useful, because now you can't ignore it because there's a red bar in everyone's dev environment. I do notice a lot more unit and integration testing these days, so it is possible that some of this is standing in for what used to be a bug database. I hope nobody interprets this as a claim that it replaces everything you get from a bug database, I'm just seeing it as something that might reduce the impact of the absence of a bug database.
- patio11 14y agoIf you require an SLA to spell out acceptable timelines for issue resolution by an on-call engineer capable of debugging ImageMagick, that is probably something which can be bought, either from the maintainer of ImageMagick or from third-party providers.
- up_and_up 14y agoOne place to look for a ImageMagick consultant would be to post for one under the 'consultant' section in the IM forums themselves [http://www.imagemagick.org/discourse-server/viewforum.php?f=24&sid=f94cd391723c847aa15004884e7e752a http://www.imagemagick.org/discourse-server/viewforum.php?f=...]
- pnathan 14y agoBitbucket and github's bug trackers are pretty nice. No, they aren't as subtle as bugzilla, but I like them. Speaking for myself, I make a personal point of pride of responding to every bug that shows up on my bug trackers. Not that it's very high traffic at all. :-)
- twodayslate 14y agoEmailing developers usually works for me and they are more than happy to help. I then usually toss a couple bucks their way for the help. It is a win-win.
- brownbat 14y agoIt's a pattern I've run into recently with Google products: I see unexpected behavior (Voice repeatedly fails to send SMS, Android fails to accept default action settings, Gmail hosts a 'mixed content' vulnerability...). I run through a short help questionnaire from Google to rule out the most common issues, it eventually recommends the Google Support Forums. I search there for others with the same problem, I find them or not, no one has a solution. I post my issue and ask for feedback, never see any response. I just chalked it up to the "support is expensive so we don't do any" model. I worry that the way Google handles support is spreading to other companies faster than the way Google handles algorithms or stripped down interfaces.
- reidrac 14y agoYes, it is very frustrating indeed; specially if I can't fix the problem myself. My favourite situation is when I submit a bug with all the information I can gather and after a year (or even more) a developer updates the ticket asking if I can still reproduce the problem. Most of the time I can't because I moved on and I'm using a different software, upgraded version, or simply I don't care any more. To be honest, I almost prefer the bug is automatically closed because it won't be fixed (no activity for some time, Fedora EOL, etc). At least the bot closing tickets can't care more :) But it's not always like that. I've been submitting bug reports for 10+ years, and sometimes you get a fix in hours or days. Your success may vary :) I've found that very popular projects (ie. Ubuntu, Fedora, or GNOME), with a large user base are suffering of "bugtracker bankruptcy": too many tickets to be handled properly. I don't know the reason for that, but I suspect it could be related to automated bug reporting used by distributions plus the increase of "consumer users" and not "producer users". If the distributor/upstream relationship is not working (ie. distro packages version X, upstream is already working on X+1 and lacks of manpower to maintain X), then after some months you get a mail from a bot :) </rant> Anyway, if you think about it... that's a good way of experiencing OSS: adopt an unmaintained project!
- lizzard 14y agoLarger projects like GNOME and Mozilla are developing communities of bug triagers to help with exactly this problem! For example: https://wiki.mozilla.org/Bugmasters https://wiki.mozilla.org/Bugmasters https://live.gnome.org/Bugsquad https://live.gnome.org/Bugsquad http://www.mediawiki.org/wiki/Bug_management/Triage http://www.mediawiki.org/wiki/Bug_management/Triage So adopting a little bit of a big project, and watching its bugs come in to help triage them, is going to be helpful for this increased ratio of consumer users to producer users.
- friendly_chap 14y agoDat fontcolor!
- mindcrime 14y agoMaybe I'm outing myself in terms of age, but not only do I pretty much agree with jwz here, but I'm happy to say that we[1] use Bugzilla[2] for our bug tracker[3] for all our open source projects. Of course, you might argue that it's easy for us, as we don't have a ton of users opening gazillions of bugs. It is a fair point, that simply triaging bug reports can become a big time sink in larger projects. Makes me wonder if some technological tooling (eg, better "dupe" detectors, etc.) could help manage the problem. [1]: http://www.fogbeam.com http://www.fogbeam.com [2]: http://www.bugzilla.org/ http://www.bugzilla.org/ [3]: http://dev.fogbeam.org/bugzilla/ http://dev.fogbeam.org/bugzilla/
- sirmarksalot 14y agoThis reminds me of a talk by Brad Fitzpatrick about a year ago: http://blip.tv/djangocon/keynote-brad-fitzpatrick-5572560 http://blip.tv/djangocon/keynote-brad-fitzpatrick-5572560 Basically, if you put your email address in a project, you're going to get emails from random people for the rest of your life. Sort of like getting a tattoo, a spur-of-the-moment decision early on sticks with you forever. Just one possible reason the projects you look at don't have an e-mail address for the maintainer.
- up_and_up 14y agoRe Imagemagick issues/questions etc, the OP did it wrong. You need to post to the Imagemagick forums: http://www.imagemagick.org/discourse-server/ http://www.imagemagick.org/discourse-server/ They are extremely active and you will get a response from someone within hours. Several of the people who frequent the IM forums are extremely experienced and helpful including: Anthony: http://www.imagemagick.org/Usage/ http://www.imagemagick.org/Usage/
- cpeterso 14y agoThis comment on Oracle's MySQL bug database is a perfect example: "Moving to the internal bug DB so the issue doesn't get lost." http://bugs.mysql.com/bug.php?id=68250 http://bugs.mysql.com/bug.php?id=68250
- danbmil99 14y agoMy experience with open source projects is that bug reports are only taken seriously from people who are involved in the project. That means either you have contributed code, or you are a serious user who has spent time introducing yourself in the 'real' forum the developers use (typically freenode/IRC back in the day). Otherwise, the signal/noise ratio is just way too low for it to be useful to read through all the reports, particularly if the project is to any degree high profile. The assumption is that a 'real' bug will eventually be reported by a 'serious' user or developer. Maybe that's wrong but that is how it works in the real world.
- Macsenour 14y agoI worked at a place where I was the only person responsible for the game dev section of the company, about 50 people. On my second day I discovered that QA listed a bug as high priority with a "1", while the developers put a "10" on the highest priority. I think you can see that there was an issue. They had operated with this system for more than a year before I got there. I switched them to a letter system, "A" being top priority, "B" is second etc on my third day. Their world changed.
- radley 14y agoI think everyone is pivoting right now trying to stay in the mobile race, so they're letting older projects go dormant. I think part of it has to do with how Apple & M$ are handling the big pivot. OSX is turning to crap but iOS is booming so Apple is huge. In contrast, M$ is trying to sustain their old OS and it's not working.
- belorn 14y agoFor projects that are distributed in Debian, I have stopped reporting bugs at the "official" site and opted to use reportbug instead. It might be slower, but I rarely if ever have bugs being completely ignored. At worst, a debian sponsor will either fix the issue as a debian fix, or remove the package.
- FlukeATX 14y agoRegarding the "ignored" message sent via Facebook, it's possible that the message didn't hit the recipient's inbox but the "Other" folder if the sender and recipient weren't friends. That has happened to me a number of times.
- thesis 14y agoI contacted the jPlayer folks recently for them to do a PAID project, since on their site they say they do custom work. Needless to say... they never contacted me back.
- damian2000 14y agoFYI, an update to his jPlayer issue: http://www.jwz.org/blog/2013/02/more-jplayer-grief/ http://www.jwz.org/blog/2013/02/more-jplayer-grief/
- duaneb 14y agoI would pay money for a plugin that just detected sites like this and filtered them through readability.
- simias 14y agoI've reported a security vulnerability to the KeepassX maintainers (certain types of keysfiles would be ignored and result in an empty passphrase without the user having any way to know) and never got any answer. While digging through the file format (.kdb) I also found multiple oddities (the number of entries and the checksum of the contents being unencrypted in the header for instance) that seemed to weaken the format and leak info for no reason. It was several months ago and I never got any reply. That being said, the last release is from 2010, so it might be abandonware. Anyway, if you use KeepassX to store your passwords, be careful, the whole crypto behind felt a bit amateurish.
- gnud 14y agoKeepassx is a cross-platform version of KeePass 1 - they're using the file format from another (legacy) program, and I doubt they can change it. I use KeePass2 myself. It uses a new file format, and it's .net, runs well under mono on linux. And it's definitely not abandonware. See http://keepass.info/ http://keepass.info/
- simias 14y agoI'll look into it, thanks!
- perfunctory 14y agoRemember when people paid for their tools?
- thyrsus 14y agoI've been quite happy with the responses I get to Fedora/RHEL bugs in bugzilla.redhat.com, especially considering what I paid for it ($0). I also suspect that, once a problem is identified as coming from upstream, the Red Hat folks get more attention from the upstream folks than others. Based on a small sample, Red Hat seems to do worse with "documentation bugs" - such as when their documentation described using raidtools in RHEL4, when it had been replaced by madm (which appeared to me at the time as "missing raidtools").