Changes in this version:
* I bit the bullet and shamelessly plagiarized harthur's bzhome
design, so the tool is significantly prettier than it used to be
* There's a bit more coverage of various languages/project areas
* I punted on the informative displays that explained what each
component was, because I couldn't figure out a good and pretty way to
display them. Patches welcome.
* There's a much better sense of when information is being retrieved
In fact, I like what is here enough that I would be fine with people
distributing the link. I'm not certain we want to go full out on
publicizing it yet, because my private webspace may not be the best
location for it. However, if you want to hand it out to contributors
who are looking for bugs, please feel free.
Also feel free to give me feedback and/or patches! I want to make this
tool the best it can be, and I would love your input.
On Thu, Dec 1, 2011 at 1:34 PM, Josh Matthews <j...@joshmatthews.net> wrote:
> There's a new version of my Bugs Ahoy tool available, and I would love
> some feedback on it. http://www.joshmatthews.net/bugsahoy/ is the
> canonical location for the time being, and it's kept up to date with
> the git repository at https://github.com/jdm/bugsahoy/ .
> Changes in this version:
> * I bit the bullet and shamelessly plagiarized harthur's bzhome
> design, so the tool is significantly prettier than it used to be
> * There's a bit more coverage of various languages/project areas
> * I punted on the informative displays that explained what each
> component was, because I couldn't figure out a good and pretty way to
> display them. Patches welcome.
> * There's a much better sense of when information is being retrieved
=================== ^^^ For CC'd subscribers ^^^ ======================
> In fact, I like what is here enough that I would be fine with people
> distributing the link. I'm not certain we want to go full out on
> publicizing it yet, because my private webspace may not be the best
> location for it. However, if you want to hand it out to contributors
> who are looking for bugs, please feel free.
Will not IT team happily help you on this one (getting you a server)? I
guess so... //CC'd
Also feel free to give me feedback and/or patches! I want to make this
> tool the best it can be, and I would love your input.
I see the aspects (interested in topics) ORs the selection for fetching the
bugs - will be better if we could have option to AND also.
> Changes in this version:
> * I bit the bullet and shamelessly plagiarized harthur's bzhome
> design, so the tool is significantly prettier than it used to be
> * There's a bit more coverage of various languages/project areas
> * I punted on the informative displays that explained what each
> component was, because I couldn't figure out a good and pretty way to
> display them. Patches welcome.
> * There's a much better sense of when information is being retrieved
> In fact, I like what is here enough that I would be fine with people
> distributing the link. I'm not certain we want to go full out on
> publicizing it yet, because my private webspace may not be the best
> location for it. However, if you want to hand it out to contributors
> who are looking for bugs, please feel free.
> Also feel free to give me feedback and/or patches! I want to make this
> tool the best it can be, and I would love your input.
Really nice tool, faster and friendlier than Bugzilla, and way better
at finding real good-first-bugs than our older attempts. Awesome work,
Josh! I even found a bug and sent a patch :)
There's just one thing I keep hitting on it (and used to hit on the
old Bugzilla query): ASSIGNED bugs. (like
https://bugzilla.mozilla.org/show_bug.cgi?id=689834). Those should
have someone working on them already, so I think they should be hidden
or at least have lower priority.
But then there are some ASSIGNED bugs which used to have someone
working on them but the person is no longer reporting any activity
(like https://bugzilla.mozilla.org/show_bug.cgi?id=649124). Those
should still be shown on the list, so I think we should either
a) Only show ASSIGNED bugs if they are inactive for some time; or
b) Triage ASSIGNED mentored bugs more closely so we don't have lots of
cases where this happens.
Thanks for the feedback! Your point about assigned bugs is a good one.
You're right, only displaying them if they have not seen updated in
some time is a possibility. I don't think triaging them will be a good
solution - I'm trying to make this tool be as useful as possible
without making mentors change their workflow at all. However, another
possibility would be displaying the entries for assigned bugs
differently - possibly the background colour could change based on how
long it has been since an update. I think I'll play around with that
idea.
Cheers,
Josh
On 1 December 2011 19:49, Reuben Morais <reuben.mor...@gmail.com> wrote:
> Really nice tool, faster and friendlier than Bugzilla, and way better
> at finding real good-first-bugs than our older attempts. Awesome work,
> Josh! I even found a bug and sent a patch :)
> There's just one thing I keep hitting on it (and used to hit on the
> old Bugzilla query): ASSIGNED bugs. (like
> https://bugzilla.mozilla.org/show_bug.cgi?id=689834). Those should
> have someone working on them already, so I think they should be hidden
> or at least have lower priority.
> But then there are some ASSIGNED bugs which used to have someone
> working on them but the person is no longer reporting any activity
> (like https://bugzilla.mozilla.org/show_bug.cgi?id=649124). Those
> should still be shown on the list, so I think we should either
> a) Only show ASSIGNED bugs if they are inactive for some time; or
> b) Triage ASSIGNED mentored bugs more closely so we don't have lots of
> cases where this happens.
This is excellent and very very useful. I might want in the future to use it to help with the Armenian localization OR release engineering.
There's a couple of things that I believe would be very useful.
* What is this about? - Explain what this is for and how it works (I could help if you push me in the right direction).
* Brief info about the query - Give a rough idea at the bottom of how this search could be reproduced in bugzilla.
* How can I show up there? - say what is needed to make a bug show up.
Thanks a lot for this fine work and looking forward to see this grow big :)
> Changes in this version:
> * I bit the bullet and shamelessly plagiarized harthur's bzhome
> design, so the tool is significantly prettier than it used to be
> * There's a bit more coverage of various languages/project areas
> * I punted on the informative displays that explained what each
> component was, because I couldn't figure out a good and pretty way to
> display them. Patches welcome.
> * There's a much better sense of when information is being retrieved
> In fact, I like what is here enough that I would be fine with people
> distributing the link. I'm not certain we want to go full out on
> publicizing it yet, because my private webspace may not be the best
> location for it. However, if you want to hand it out to contributors
> who are looking for bugs, please feel free.
> Also feel free to give me feedback and/or patches! I want to make this
> tool the best it can be, and I would love your input.
What do I do to get this in here in a Websites option in the Are you
interested section? How can I associate skills to the bug so it shows
up in the skills section?
Do you think it makes any sense to also search by mentor? The situation
that I have in mind is a new contributor working with a mentor, getting a
very positive experience, and wanting to pick another project with the same
mentor. (The opposite case could also happen, in case for whatever reason
their first experience was really bad...)
On Thu, Dec 1, 2011 at 3:04 AM, Josh Matthews <j...@joshmatthews.net> wrote:
> There's a new version of my Bugs Ahoy tool available, and I would love
> some feedback on it. http://www.joshmatthews.net/bugsahoy/ is the
> canonical location for the time being, and it's kept up to date with
> the git repository at https://github.com/jdm/bugsahoy/ .
> Changes in this version:
> * I bit the bullet and shamelessly plagiarized harthur's bzhome
> design, so the tool is significantly prettier than it used to be
> * There's a bit more coverage of various languages/project areas
> * I punted on the informative displays that explained what each
> component was, because I couldn't figure out a good and pretty way to
> display them. Patches welcome.
> * There's a much better sense of when information is being retrieved
> In fact, I like what is here enough that I would be fine with people
> distributing the link. I'm not certain we want to go full out on
> publicizing it yet, because my private webspace may not be the best
> location for it. However, if you want to hand it out to contributors
> who are looking for bugs, please feel free.
> Also feel free to give me feedback and/or patches! I want to make this
> tool the best it can be, and I would love your input.
I like this idea. Communities are about people and it really helps to
build relationships if people can work together for a bit. At the same
time, someone might be ready to work with someone new, and so want to
pick a bug from a specific person that they are recommended to work
with next. (so not for a bad reason but for a good reason, too).
On Fri, Dec 2, 2011 at 6:33 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote:
> This looks great Josh!
> Do you think it makes any sense to also search by mentor? The situation
> that I have in mind is a new contributor working with a mentor, getting a
> very positive experience, and wanting to pick another project with the same
> mentor. (The opposite case could also happen, in case for whatever reason
> their first experience was really bad...)
>> Changes in this version:
>> * I bit the bullet and shamelessly plagiarized harthur's bzhome
>> design, so the tool is significantly prettier than it used to be
>> * There's a bit more coverage of various languages/project areas
>> * I punted on the informative displays that explained what each
>> component was, because I couldn't figure out a good and pretty way to
>> display them. Patches welcome.
>> * There's a much better sense of when information is being retrieved
>> In fact, I like what is here enough that I would be fine with people
>> distributing the link. I'm not certain we want to go full out on
>> publicizing it yet, because my private webspace may not be the best
>> location for it. However, if you want to hand it out to contributors
>> who are looking for bugs, please feel free.
>> Also feel free to give me feedback and/or patches! I want to make this
>> tool the best it can be, and I would love your input.
If some Graphics bug happens to require only JavaScript/HTML skills, not C++ skills, how can I advertise it as such, so that it will show up in bugsahoy when people select JavaScript? (Thinking about bugs in the unit tests)
I've also been thinking about mentoring in non-English languages. I think that this is a mentor property rather than a bug property, so we could have a table of supported languages per mentor. Obviously, English would be implicit for all mentors, no need to specify it. Does it sound like a good idea? Would you support it in the bugsahoy interface?
> Looks wonderful, I will link to it from GFX/Contribute as soon as it
> finds a 'permanent' home.
> I don't have suggestions other than keep it up.
> Cheers,
> Benoit
> On 01/12/11 03:04 AM, Josh Matthews wrote:
>> There's a new version of my Bugs Ahoy tool available, and I would love
>> some feedback on it. http://www.joshmatthews.net/bugsahoy/ is the
>> canonical location for the time being, and it's kept up to date with
>> the git repository at https://github.com/jdm/bugsahoy/ .
>> Changes in this version:
>> * I bit the bullet and shamelessly plagiarized harthur's bzhome
>> design, so the tool is significantly prettier than it used to be
>> * There's a bit more coverage of various languages/project areas
>> * I punted on the informative displays that explained what each
>> component was, because I couldn't figure out a good and pretty way to
>> display them. Patches welcome.
>> * There's a much better sense of when information is being retrieved
>> In fact, I like what is here enough that I would be fine with people
>> distributing the link. I'm not certain we want to go full out on
>> publicizing it yet, because my private webspace may not be the best
>> location for it. However, if you want to hand it out to contributors
>> who are looking for bugs, please feel free.
>> Also feel free to give me feedback and/or patches! I want to make this
>> tool the best it can be, and I would love your input.
Thanks for the really great suggestions, everybody! Between this
feedback and the ideas I bounced around with my girlfriend, there are
some really great directions in which I am excited to take this tool.
I'm starting to file the feedback as github issues
(https://github.com/jdm/bugsahoy/issues) so that I don't forget about
them, and I would welcome both further email feedback and github
issues.
On 2 December 2011 10:25, Armen Zambrano G. <arme...@mozilla.com> wrote:
> There's a couple of things that I believe would be very useful.
> * What is this about? - Explain what this is for and how it works (I could
> help if you push me in the right direction).
I would love to incorporate help/information about how to use it, but
I'm not sure of the best way to do that at the moment. I might need to
have a talk with a real web designer to get some ideas here.
> * Brief info about the query - Give a rough idea at the bottom of how this
> search could be reproduced in bugzilla.
That's not a bad idea. I'll file an issue about that.
> * How can I show up there? - say what is needed to make a bug show up.
I'm not certain that this information belongs on the page itself, if
that's what your suggesting. I'll share that information here, and I
hope to also give a lightning talk at the weekly meeting in which I
can disseminate it more widely.
Currently, the tool aggregates results by searching Bugzilla for bugs
with mentor= in the whiteboard. The "Are you interested in" list maps
to Bugzilla products and components, which limit the search, and the
"Do you know" list maps similarly limits the search to bugs that
contain lang=(js|c++|html|css|py), depending on the selection.
Therefore, it's easy to repurpose this tool to focus on your own
specific uses (such as localization, or other tasks that don't
necessarily fit in a code-focused tool) by changing the mappings.
The downside of this setup is that if there isn't a category in the
"Are you interested in" list that covers a Product/Component pair, any
mentored bugs in that component will not be visible in this tool
(unless it's got a language annotation). I've been trying to reduce
the Bugzilla product/component maze into a manageable "area of
interest" setup, but that doesn't necessarily map easily for
everything.
> Do you think it makes any sense to also search by mentor? The situation that I have in mind is a new contributor working with a mentor, getting a very positive experience, and wanting to pick another project > with the same mentor. (The opposite case could also happen, in case for whatever reason their first experience was really bad...)
I'm not completely sold on this, but I've filed an issue about it.
Mainly, I'm trying to think of the best way to present more
information without overcomplicating the interface. Perhaps individual
bugs in the list should be clickable and open a more detailed view
that has information including who the mentor is, and then that could
be a clickable link to a new search...
> I've also been thinking about mentoring in non-English languages. I think that this is a mentor property rather than a bug property, so we could have a table of supported languages per mentor. Obviously,
> English would be implicit for all mentors, no need to specify it. Does it sound like a good idea? Would you support it in the bugsahoy interface?
I can see value in contributors being able to see that there is a
place for them if they are more comfortable in a language other than
English, and I've filed an issue about it. Again, the way of
presenting this information will be challenging, and unfortunately
this data cannot be aggregated automatically from bugzilla. Perhaps it
could be tied in with mozillans.org when that grows a public API. I'm
really interested in keeping this tool as automated as possible.
I hope this has answered everybody's questions so far. I'm so glad for
all this feedback; it's really encouraging.
>> Changes in this version:
>> * I bit the bullet and shamelessly plagiarized harthur's bzhome
>> design, so the tool is significantly prettier than it used to be
>> * There's a bit more coverage of various languages/project areas
>> * I punted on the informative displays that explained what each
>> component was, because I couldn't figure out a good and pretty way to
>> display them. Patches welcome.
>> * There's a much better sense of when information is being retrieved
>> In fact, I like what is here enough that I would be fine with people
>> distributing the link. I'm not certain we want to go full out on
>> publicizing it yet, because my private webspace may not be the best
>> location for it. However, if you want to hand it out to contributors
>> who are looking for bugs, please feel free.
>> Also feel free to give me feedback and/or patches! I want to make this
>> tool the best it can be, and I would love your input.
> > * How can I show up there? - say what is needed to make a bug show up.
> I'm not certain that this information belongs on the page itself, if
> that's what your suggesting. I'll share that information here, and I
> hope to also give a lightning talk at the weekly meeting in which I
> can disseminate it more widely.
Could you also add the documentation to the wiki page that talks about
mentored bugs?
