6 ms·

I see no link to a relevant bug report linked in the article and without one, that bug is never going to get fixed. A bug report with a minimal testcase would

by ferongr 14y ago

I see no link to a relevant bug report linked in the article and without one, that bug is never going to get fixed. A bug report with a minimal testcase would take 50% the time it took to write the article itself but actually have greater impact.

nrkn 14y ago
Not linked to, but https://bugzilla.mozilla.org/show_bug.cgi?id=644104 https://bugzilla.mozilla.org/show_bug.cgi?id=644104
- ferongr 14y ago
  Great, thanks.
Hopka 14y ago
But you'd have to figure out how to use Mozilla's bug tracker first. And that has prevented me from reporting Bugs in Firefox every single time so far. And I guess I'm not the only one.
- kibwen 14y ago
  I was about to agree with you (especially when compared to Github's issue tracker, since everyone has a Github account), but while poking around I noticed that it offers login via BrowserID, which I just so happen to have. Since registering a new account is the biggest barrier to participating in any service, that's not so bad after all.
- ferongr 14y ago
  I'm not a professional in the field but I filed my first bug in Bugzilla some years ago effortlessly. I'd expect a web author to be even better at using technical tools. Bugzilla is a wonderful tool for Mozilla. Unlike other projects that use mailing lists or internal tools, Mozilla coordinates its projects mainly using Bugzilla. Developers discuss patch approaches there, post WIPs and do code reviews there. Considering Mozilla is comprised of many contributors all around the globe such software is a necessity. Bugzilla may look complicated and cumbersome but it's actually a powerful tool. By comparison, the issue tracker used by the Chromium project is just a public-facing ad-hoc thing. The project's workings are mostly opaque, coordinated by Google's employees. The whole project works more like typical closed-source software.

by ferongr 14y ago

nrkn 14y ago

Not linked to, but https://bugzilla.mozilla.org/show_bug.cgi?id=644104 https://bugzilla.mozilla.org/show_bug.cgi?id=644104

ferongr 14y ago
Great, thanks.

Hopka 14y ago

But you'd have to figure out how to use Mozilla's bug tracker first. And that has prevented me from reporting Bugs in Firefox every single time so far. And I guess I'm not the only one.

kibwen 14y ago
I was about to agree with you (especially when compared to Github's issue tracker, since everyone has a Github account), but while poking around I noticed that it offers login via BrowserID, which I just so happen to have. Since registering a new account is the biggest barrier to participating in any service, that's not so bad after all.
ferongr 14y ago
I'm not a professional in the field but I filed my first bug in Bugzilla some years ago effortlessly. I'd expect a web author to be even better at using technical tools. Bugzilla is a wonderful tool for Mozilla. Unlike other projects that use mailing lists or internal tools, Mozilla coordinates its projects mainly using Bugzilla. Developers discuss patch approaches there, post WIPs and do code reviews there. Considering Mozilla is comprised of many contributors all around the globe such software is a necessity. Bugzilla may look complicated and cumbersome but it's actually a powerful tool. By comparison, the issue tracker used by the Chromium project is just a public-facing ad-hoc thing. The project's workings are mostly opaque, coordinated by Google's employees. The whole project works more like typical closed-source software.