Can we have that? so that people can filter out bugs that are require skills for certain languages only?
For example if I needed to fix something that is C++ I would just tag it so, same for PHP, JS, etc... So that C++ devs could filter out only all bugs that require C++ knowledge and see all bugs across all of wikimedia that can be fixed in that language.
Developers could then simply filter out only bugs that they are interested in or able to fix.
On Wed, 2014-06-25 at 10:44 +0200, Petr Bena wrote:
Can we have that? so that people can filter out bugs that are require skills for certain languages only? For example if I needed to fix something that is C++ I would just tag it so, same for PHP, JS, etc... So that C++ devs could filter out only all bugs that require C++ knowledge and see all bugs across all of wikimedia that can be fixed in that language.
Developers could then simply filter out only bugs that they are interested in or able to fix.
Well, before developers can simply filter out bugs, somebody would have to go through ~14000 open tickets, understand which language(s) a bug report is about, and set the language(s) on all of these tickets. Would you like to volunteer? :)
More seriously, doesn't the Bugzilla product or component that a bug report belongs to already pretty much define the programming language(s) in that area? That's the level where I'd expect such information to be located. (Or in a <programming-language> tag of a project's DOAP file in its code repository.)
andre
No, they wouldn't need to do this, it would more like optional feature for new bugs and only for these which are created by person who need assistance from someone who understand the language. For example if I needed something in JS, I could just flag it so that pool of programmers we have on wikimedia project would know someone need their help and did it.
For example I can resolve probably any C/C++/C#/VB bug we have on bugzilla. But I will not do that because I have no idea which bugs are these.
If there was such a keyword, PHP programmer who need help from some HTML5 programmer, could create a bug for some feature and set HTML5 keyword so that HTML5 people are aware of that bug, it would same as "ops" keyword now. It exist just to inform ops that there is a bug which they can resolve. Now we would have it for other "teams" as well.
On Wed, Jun 25, 2014 at 12:52 PM, Andre Klapper aklapper@wikimedia.org wrote:
On Wed, 2014-06-25 at 10:44 +0200, Petr Bena wrote:
Can we have that? so that people can filter out bugs that are require skills for certain languages only? For example if I needed to fix something that is C++ I would just tag it so, same for PHP, JS, etc... So that C++ devs could filter out only all bugs that require C++ knowledge and see all bugs across all of wikimedia that can be fixed in that language.
Developers could then simply filter out only bugs that they are interested in or able to fix.
Well, before developers can simply filter out bugs, somebody would have to go through ~14000 open tickets, understand which language(s) a bug report is about, and set the language(s) on all of these tickets. Would you like to volunteer? :)
More seriously, doesn't the Bugzilla product or component that a bug report belongs to already pretty much define the programming language(s) in that area? That's the level where I'd expect such information to be located. (Or in a <programming-language> tag of a project's DOAP file in its code repository.)
andre
Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Regarding your second point. This is sci-fi in case of small projects, it maybe works for large ones, but for example when I create a bug for huggle or wm-bot where PHP, python, or JS guy is needed, nobody ever notice that. BTW mozilla is already doing this and it seems to be pretty effective, I think wikimedia could get inspired a bit (this idea is actually not from my head) :P
On Wed, Jun 25, 2014 at 1:48 PM, Petr Bena benapetr@gmail.com wrote:
No, they wouldn't need to do this, it would more like optional feature for new bugs and only for these which are created by person who need assistance from someone who understand the language. For example if I needed something in JS, I could just flag it so that pool of programmers we have on wikimedia project would know someone need their help and did it.
For example I can resolve probably any C/C++/C#/VB bug we have on bugzilla. But I will not do that because I have no idea which bugs are these.
If there was such a keyword, PHP programmer who need help from some HTML5 programmer, could create a bug for some feature and set HTML5 keyword so that HTML5 people are aware of that bug, it would same as "ops" keyword now. It exist just to inform ops that there is a bug which they can resolve. Now we would have it for other "teams" as well.
On Wed, Jun 25, 2014 at 12:52 PM, Andre Klapper aklapper@wikimedia.org wrote:
On Wed, 2014-06-25 at 10:44 +0200, Petr Bena wrote:
Can we have that? so that people can filter out bugs that are require skills for certain languages only? For example if I needed to fix something that is C++ I would just tag it so, same for PHP, JS, etc... So that C++ devs could filter out only all bugs that require C++ knowledge and see all bugs across all of wikimedia that can be fixed in that language.
Developers could then simply filter out only bugs that they are interested in or able to fix.
Well, before developers can simply filter out bugs, somebody would have to go through ~14000 open tickets, understand which language(s) a bug report is about, and set the language(s) on all of these tickets. Would you like to volunteer? :)
More seriously, doesn't the Bugzilla product or component that a bug report belongs to already pretty much define the programming language(s) in that area? That's the level where I'd expect such information to be located. (Or in a <programming-language> tag of a project's DOAP file in its code repository.)
andre
Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, 2014-06-25 at 13:51 +0200, Petr Bena wrote:
it maybe works for large ones, but for example when I create a bug for huggle or wm-bot where PHP, python, or JS guy is needed, nobody ever notice that. BTW mozilla is already doing this and it seems to be pretty effective
What do you refer to? http://www.joshmatthews.net/bugsahoy/ where you can query Mozilla Bugzilla tickets by programming language? Or the "[lang=php]" tags in the Status Whiteboard of Mozilla Bugzilla? If the latter, anybody can edit the whiteboard of tickets in Wikimedia Bugzilla, so you can just do it. :)
andre
ok that seems to be good enough for me. What is actually difference between these keywords and white-board if it can serve the same purpose?
On Wed, Jun 25, 2014 at 3:04 PM, Andre Klapper aklapper@wikimedia.org wrote:
On Wed, 2014-06-25 at 13:51 +0200, Petr Bena wrote:
it maybe works for large ones, but for example when I create a bug for huggle or wm-bot where PHP, python, or JS guy is needed, nobody ever notice that. BTW mozilla is already doing this and it seems to be pretty effective
What do you refer to? http://www.joshmatthews.net/bugsahoy/ where you can query Mozilla Bugzilla tickets by programming language? Or the "[lang=php]" tags in the Status Whiteboard of Mozilla Bugzilla? If the latter, anybody can edit the whiteboard of tickets in Wikimedia Bugzilla, so you can just do it. :)
andre
Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, 2014-06-25 at 17:11 +0200, Petr Bena wrote:
ok that seems to be good enough for me. What is actually difference between these keywords and white-board if it can serve the same purpose?
See https://www.mediawiki.org/wiki/Bugzilla/Fields
andre
wikitech-l@lists.wikimedia.org