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
) so that I don't forget about
them, and I would welcome both further email feedback and github
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
> 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.