When I file a bug report with the Flyspray web interface, why can't I specify the package it concerns? Having that option should make it possible for the package maintainers to be immediately and automatically notified of the report.
The way it works now seems to be that I have to wait for some generic bug janitor to manually assign my report to the maintainer of the package (correct me if I'm mistaken). For example, I filed a bug report nearly two days ago, but apparently no janitor (or any other maintainer) has looked at it jet, which means all that time is wasted for hardly any reason (and no, I won't specify which bug. It's irrelevant to the issue I'm addressing here.)
I believe the coders among us appreciate efficiency and automation, so maybe we can improve this system?
When I file a bug report with the Flyspray web interface, why can't I specify the package it concerns? Having that option should make it possible for the package maintainers to be immediately and automatically notified of the report.
The way it works now seems to be that I have to wait for some generic bug janitor to manually assign my report to the maintainer of the package (correct me if I'm mistaken). For example, I filed a bug report nearly two days ago, but apparently no janitor (or any other maintainer) has looked at it jet, which means all that time is wasted for hardly any reason (and no, I won't specify which bug. It's irrelevant to the issue I'm addressing here.)
I believe the coders among us appreciate efficiency and automation, so maybe we can improve this system?
...come on, not even a single flame or a "+1"? -_-;
Angus charmender@gmail.com wrote:
When I file a bug report with the Flyspray web interface, why can't I specify the package it concerns? Having that option should make it possible for the package maintainers to be immediately and automatically notified of the report.
The way it works now seems to be that I have to wait for some generic bug janitor to manually assign my report to the maintainer of the package (correct me if I'm mistaken). For example, I filed a bug report nearly two days ago, but apparently no janitor (or any other maintainer) has looked at it jet, which means all that time is wasted for hardly any reason (and no, I won't specify which bug. It's irrelevant to the issue I'm addressing here.)
I believe the coders among us appreciate efficiency and automation, so maybe we can improve this system?
...come on, not even a single flame or a "+1"? -_-;
I think job description no.1 fits you perfectly. You seem to have what it takes. :) http://www.archlinux.org/news/contributors-wanted
On Mon, Mar 28, 2011 at 9:58 PM, Grigorios Bouzakis grbzks@xsmail.com wrote:
Angus charmender@gmail.com wrote:
When I file a bug report with the Flyspray web interface, why can't I specify the package it concerns? Having that option should make it possible for the package maintainers to be immediately and automatically notified of the report.
The way it works now seems to be that I have to wait for some generic bug janitor to manually assign my report to the maintainer of the package (correct me if I'm mistaken). For example, I filed a bug report nearly two days ago, but apparently no janitor (or any other maintainer) has looked at it jet, which means all that time is wasted for hardly any reason (and no, I won't specify which bug. It's irrelevant to the issue I'm addressing here.)
I believe the coders among us appreciate efficiency and automation, so maybe we can improve this system?
...come on, not even a single flame or a "+1"? -_-;
I think job description no.1 fits you perfectly. You seem to have what it takes. :) http://www.archlinux.org/news/contributors-wanted
Uh huh, that's great, but the point I tried to make is that these janitors (or "Bug Wranglers" as they're apparently called in Arch land) are unnecessary in most cases if only users could properly flag their reports with the corresponding package. I'm In other words, I'm claiming this is mostly a UI problem rather than a man power problem. Yay for reading comprehension...
On 03/27/2011 05:16 AM, Angus wrote:
When I file a bug report with the Flyspray web interface, why can't I specify the package it concerns? Having that option should make it possible for the package maintainers to be immediately and automatically notified of the report.
you seem to be a regular bugzilla user. You can't specify a package because we have a lot of them and somebody has to add them as a project and sucks(it might be a limitation for flyspray)
instead we chose to have some style but not everyone use it.
[packagename] short description
The way it works now seems to be that I have to wait for some generic bug janitor to manually assign my report to the maintainer of the package (correct me if I'm mistaken). For example, I filed a bug report nearly two days ago, but apparently no janitor (or any other maintainer) has looked at it jet, which means all that time is wasted for hardly any reason (and no, I won't specify which bug. It's irrelevant to the issue I'm addressing here.)
I believe the coders among us appreciate efficiency and automation, so maybe we can improve this system?
only if we use bugzilla.
On Mon, Mar 28, 2011 at 10:07 PM, Ionuț Bîru ibiru@archlinux.org wrote:
On 03/27/2011 05:16 AM, Angus wrote:
When I file a bug report with the Flyspray web interface, why can't I specify the package it concerns? Having that option should make it possible for the package maintainers to be immediately and automatically notified of the report.
you seem to be a regular bugzilla user. You can't specify a package because we have a lot of them and somebody has to add them as a project and sucks(it might be a limitation for flyspray)
But a script should be able to take care of this, no?
instead we chose to have some style but not everyone use it.
[packagename] short description
I use that when reporting bugs, but it doesn't seem to get my reports assigned to the relevant maintainer(s) any faster at all...
Angus charmender@gmail.com wrote:
But a script should be able to take care of this, no?
Doesn't a script solve everything? Here is Arch's customized flyspray: http://projects.archlinux.org/vhosts/bugs.archlinux.org.git
instead we chose to have some style but not everyone use it.
[packagename] short description
I use that when reporting bugs, but it doesn't seem to get my reports assigned to the relevant maintainer(s) any faster at all...
You guessed it, its because the maintainer has to become aware of the bug report. Which usually means someone should assign it to him :)
---- Greg
On Mon, Mar 28, 2011 at 10:31 PM, Grigorios Bouzakis grbzks@xsmail.com wrote:
Angus charmender@gmail.com wrote:
But a script should be able to take care of this, no?
Doesn't a script solve everything? Here is Arch's customized flyspray: http://projects.archlinux.org/vhosts/bugs.archlinux.org.git
Thanks. Unfortunately I'm not familiar with php (I've always found it a bit too stinky stinky for my taste). If Arch would use Roundup or something else python based I could probably hack it though...
You guessed it, its because the maintainer has to become aware of the bug report. Which usually means someone should assign it to him :)
Again, I'm saying there should be a straightforward option for the user to do that him/herself when filing the bug report. This I think applies especially to a community like Arch, where there are many packages (and thus bugs) to manage and users tend to be somewhat less clueless then in most other communities. If flyspray can't be fixed to include this basic functionality, perhaps replacing it with something else would be a good idea?
On 28 March 2011 21:19, Angus charmender@gmail.com wrote:
But a script should be able to take care of this, no?
Probably. Get the prefix and then just match against a db/text file of packages and respective maintainers. If no prefix or nothing found, then let the wrangler handle it (the assignment).
Le lundi 28 mars 2011 à 22:19 +0900, Angus a écrit :
I use that when reporting bugs, but it doesn't seem to get my reports assigned to the relevant maintainer(s) any faster at all...
You just forgot one thing: Assigning automatically a bug to a maintainer does not mean the bug will be fixed any faster.
I can see now some of my bugs, assigned and fixed asap, while others are assigned and linger on for quite some time. Because the maintainer does not take any action. It entirely depends on the maintainer willingness. This is especially true for [community]
I don't want to point the finger at some maintainer here. I am trying to make a point.
On Wed, Mar 30, 2011 at 7:32 PM, solsTiCe d'Hiver solstice.dhiver@gmail.com wrote:
Le lundi 28 mars 2011 à 22:19 +0900, Angus a écrit :
I use that when reporting bugs, but it doesn't seem to get my reports assigned to the relevant maintainer(s) any faster at all...
You just forgot one thing: Assigning automatically a bug to a maintainer does not mean the bug will be fixed any faster.
I can see now some of my bugs, assigned and fixed asap, while others are assigned and linger on for quite some time. Because the maintainer does not take any action. It entirely depends on the maintainer willingness. This is especially true for [community]
I don't want to point the finger at some maintainer here. I am trying to make a point.
Separate and tangential topic. Automatic assignment, if it works, will save time (and more importantly won't lose time).
On Mon, Mar 28, 2011 at 8:07 AM, Ionuț Bîru ibiru@archlinux.org wrote:
On 03/27/2011 05:16 AM, Angus wrote:
When I file a bug report with the Flyspray web interface, why can't I specify the package it concerns? Having that option should make it possible for the package maintainers to be immediately and automatically notified of the report.
you seem to be a regular bugzilla user. You can't specify a package because we have a lot of them and somebody has to add them as a project and sucks(it might be a limitation for flyspray)
instead we chose to have some style but not everyone use it.
[packagename] short description
The way it works now seems to be that I have to wait for some generic bug janitor to manually assign my report to the maintainer of the package (correct me if I'm mistaken). For example, I filed a bug report nearly two days ago, but apparently no janitor (or any other maintainer) has looked at it jet, which means all that time is wasted for hardly any reason (and no, I won't specify which bug. It's irrelevant to the issue I'm addressing here.)
I believe the coders among us appreciate efficiency and automation, so maybe we can improve this system?
only if we use bugzilla.
Please don't.
Perhaps the package web interface could have a special "Report Bug" which files a bug into flyspray and fills in some of the fields automatically: version, maintainer, proper title template etc.
Sander
arch-general@lists.archlinux.org