jdm / bugsahoy Goto Github PK

The goal is to get this tool hosted on mozilla.org, and it would be really great to get the design integrated with the site template. Relevant links:
http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/includes/

16:01 <davidwboswell> for templates, take a look at an existing /contribute page and you'll see they're called through php
16:01 <davidwboswell> http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/contribute/index.html?revision=97289&view=markup
16:02 <davidwboswell> can reuse the top and bottom of an existing page and it should work

It's worth getting in contact with David Bolter (davidb on IRC) to get solid pointers on accessibility resources.

From your blog, it seems http://www.joshmatthews.net/bugsahoy/ is the place bugsahoy lives... yet it isn't listed either as the website associated with this repo or in the README.

If we're loading from multiple sources (ie. at least one github repo), we're gated on whichever source is slowest. We should add some message like "X sources remaining..." while X > 0.

Something like 'Are you a mentor? Find out how to add your bugs to Bugs Ahoy!'. I'm not certain whether we should do this, but it would be worth trying.

It's especially useful for Gaia because it will tell you which application is concerned.

http://help.lighthouseapp.com/kb/api

The following repositories under the mozilla account are applicable to Web QA:

• FlightDeck-selenium
• Affiliates-Tests
• moztrap-tests
• Addon-Tests
• mdn-tests
• mcom-tests
• snippets-tests
• sumo-tests
• Socorro-Tests
• marketing-project-template
• mozwebqa-test-templates
• qmo-tests
• wiki-tests
• bouncer-tests
• marketplace-tests

Is the 'mentored' label required to include these in Bugs Ahoy? I think any of these open tasks are up for grabs by contributors.

Web QA holds tasks in Pivotal Tracker and it would be great to have Bugs Ahoy list suitable tasks. I have added a 'mentored' label to one of the tasks, which I think would probably be most suitable as it aligns with others.

The API is documented, and I suspect the most relevant section would be get stories by filter.

It would be nice for me, as a developer, to be able to see on http://www.joshmatthews.net/bugsahoy/ how to file bugs/github issues/whatever that will be slurped up by bugsahoy. While the way to file bugzilla bugs is baked into my brain, I have had many people ask how to do this, so online instructions might be nice. I don't know how to file github issues to be picked up by bugsahoy, so I generally don't. If there was online help, I probably would.

It would be nice for contributors, IMHO, to have more online help about the role of bugsahoy in the Mozilla ecosystem. Even a brief description and a page of links would be a big help.

This could just be static HTML. It should be linked to from the top of the page for easy access (TBH, I'd move the footer, " Bugs Ahoy! is written by Josh Matthews (get the source!) " to the top of the page too, and probably replicate it in the "help").

I suspect there are a bunch more categories that could be added to ensure better coverage of the Core/Toolkit/Firefox products. We should also consider categories that cover Release Engineering and Testing - talk to lsblakk and ctalbert/jhammel about those.

Some bugs are assigned and being worked on. Others are assigned and forgotten. We should display assigned bugs in some way that shows their status, such as changing the background colour based on how long it has been since the last modification.

STR:

1. select a category
2. select another category before the first one finishes loading
3. notice that the throbber disappears after the first load finishes, yet another is still ongoing

The arrow panel when hovering over a bug in the bug lists shows "Assigned to: undefined" (currently working example: bug 1007490), presumably because the bug was assigned to just an email-address and the assignee hasn't created an account yet.

At minimum, bump the default result count to the maximum (100, I believe.)

Everything got automigrated to the custom field and now bugsahoy is very sad. :-(

• suggest contribution opportunitiies (Chinese engineering)
• suggest mentors

Find some way to obtain this information from the user.

While working to get the remaining languages in for our github mappings, I wanted to setup bugsahoy locally for testing. Sadly I cannot figure out how to best run it. It would be very helpful to get some instructions how to setup bugsahoy.

A typo in the source code prevents the language list to be displayed on the left column. This makes selecting a bug harder as you don't really know which language you have to know to fix the displayed bugs.

I'm new to github so I don't know how to commit the fix to the repo, but here's the fix :
On line 54 in index.html, change " ["html", "HTML/CSS"]]" to " ["html", "HTML/CSS"]"

Somebody gave me a good reason to provide links to equivalent Bugzilla queries for each category. I forget what it was, but it seems like something worth doing.

The goal is to keep bugsahoy as customizable as possible for other groups using Bugzilla to track work items. It would be ideal to move all definition of mappings into an external config file that could be processed at deployment time, creating the static index.html that would be served to visitors. This mapping would include:

• Sections of clickable groups and names, with parameters that indicate whether to perform a union or intersection of the results
• Corresponding bugzilla searches to perform
• Extra information boxes

In other words, everything that defines the non-universal aspects of the current UI. JSON would be a reasonable choice for the config file format, with a python script to perform the translation.

It's conceivable this could be a desirable way to find further bugs to work on.

Otherwise the numbering is kind of strange, and it's hard to tell what you're really looking at.

https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox&component=Developer%20Tools#Developer%20Tools

If we provided a 'beginner', 'intermediate', 'advanced' label map for github integration it would be great for users of Bugs Ahoy to filter by this. This way it should be easy for users to find an easy first task, or something more challenging.

I think placing them on the right hand side would be less visually complex. The text is quite small at the moment as well, and the background colour really fit with the colour scheme. Something lighter would probably be a better choice.

It's important to be able to look at all C++ bugs. However, it's more sensible to intersect the results of a component search by the languages present, rather than aggregating all the results.

Be it resolved:

1. a language selected with no components shows all bugs of that language
2. a language selected with at least one component shows all bugs of those components and that language
3. multiple languages select with at least one component shows all bugs of those components and the union of the intersection with each language

I envision popups that appear based on the actions you take - first time visitors see a popup pointing at the categories, explaining what they do. When a category is selected, the first popup disappears and another one appears pointing at the bug list.

Apparently it can be silly to see the "No categories selected" message when >1 is selected and a load is ongoing.

There are two uses here - first, allow sites to link to specific searches that are already in place (eg. the Graphics team wants a default search of Graphics bugs), and secondly, allow users to bookmark searches. We can use the HTML5 history API to do this: https://developer.mozilla.org/en/DOM/Manipulating_the_browser_history

I'm not sure how I got into this state, but there's a tooltip that won't disappear. We should probably ensure that all tooltips are hidden when the bug list refreshes.

It would be nice to be able to filter bugs to look for Perl. Bugzilla and BMO have good first and mentored bugs (or plan to add more). :)

Just noticed that there is no checkbox option to view a list of bugs categorized under the Webmaker component. It would be nice to have this added as well.

As a new contributor, i've noticed there's a number of bugs with flag "good first bugs" with assignation to nobody@ but inside comment this ticket there's a declaration of contribution and some work is already progressing.
I think it would be easier to filter out interesting bugs if we could display and sort them by days from last update.

I can add this to bugsahoy if you agree.

More importantly, github issues have a much higher chance of overlapping.

It would be great to include github issues from mozilla projects that have a suitable label.

When loading http://www.joshmatthews.net/bugsahoy I am redirected to http://flyinformation.nfshost.com/bugsahoy/

This appears to be causing issues with the github API calls.

Results of nslookup:

$ nslookup www.joshmatthews.net
Server: 10.246.75.5
Address: 10.246.75.5#53

Non-authoritative answer:
www.joshmatthews.net canonical name = flyinformation.nfshost.com.
Name: flyinformation.nfshost.com
Address: 208.94.116.151
Name: flyinformation.nfshost.com
Address: 208.94.116.183
Name: flyinformation.nfshost.com
Address: 208.94.116.120

This is the response I'm getting:

'<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">\n<html><head>\n<title>301 Moved Permanently</title>\n</head><body>\n<h1>Moved Permanently</h1>\n<p>The document has moved <a href="http://flyinformation.nfshost.com/bugsahoy/">here</a>.</p>\n</body></html>\n'

mentor searching should use "is not empty" instead of "mentor contains @"

"is not empty" is faster:

current:
https://bugzilla.mozilla.org/bzapi/bug?bug_mentor=%40&bug_mentor_type=contains&whiteboard_type=contains_all&..

suggested:
https://bugzilla.mozilla.org/bzapi/bug?f1=bug_mentor&o1=isnotempty&...

For example, Benoit has considered mentoring in other languages. This could simply tie in with #2, but it might be nice if contributors could see that there is an option for other languages from the very start.

Without authentication we're rate limited for github API requests.

Hey

Michael Kelly told us about this page and we'd love to see our team's bugs listed here!

We're filing bugs under Developer Ecosystem and then App Center, Apps, Dev Kit and Web Components.

I presume this should be entered into https://github.com/jdm/bugsahoy/blob/master/magic.js somehow, but I'm not quite sure where...

As of now, http://www.joshmatthews.net/bugsahoy/?releng=1&py=1 returns bugs that are in products other than 'mozilla.org' as configured https://github.com/jdm/bugsahoy/blob/master/magic.js#L126

For example: https://bugzil.la/738473 (product 'testing'); https://bugzil.la/531074 (product 'webtools')

Perhaps related or informative - watch the display change with variations of "Release Engineering" and "Test Automation" selected. Test Automation is a proper subset of Release Engineering this might be news to them:) I think releng is the only category using product 'mozilla.org', so we may be a corner case.

Awesome app! Thanks!

All queries are responding 400

https://api-dev.bugzilla.mozilla.org/latest//bug?status_whiteboard=mentor%3D&whiteboard_type=contains_all&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=UNCONFIRMED&product=%20Core&component=Layout&component=Layout%3A%20Block%20and%20Inline&component=Layout%3A%20Floats&component=Layout%3A%20Form%20Controls&component=Layout%3A%20HTML%20Frames&component=Layout%3A%20Images&component=Layout%3A%20Misc%20Code&component=Layout%3A%20R%20%26%20A%20Pos&component=Layout%3A%20Tables&component=Layout%3A%20Text&component=Layout%3A%20View%20Rendering

for example.

It could be useful to link to bugzilla searches that return the same results as a given set of filters.

The Automation & Tools team does a lot of work on mobile test frameworks. While the work isn't on Fennec itself, contributors could get a feel for working with mobile devices by helping out with some of our bugs, especially if they're interested in automation. Maybe we can have a whiteboard item like [mobile] and query on that as well as by product/component?

I tried to run bugsahoy locally but was not able to given that my account has 2fa enabled and the CGI script bails out:

192.168.123.3 - - [15/May/2014 15:03:00] "GET /cgi-bin/githubapi.cgi?url=repos%2Fmozilla%2Fnightlytt%2Fissues%3Flabels%3Dmentored HTTP/1.1" 200 -
192.168.123.3 - - [15/May/2014 15:03:01] CGI script exit status 0x100

Would be nice if we can get such support.

I have not performed any testing outside of Firefox nightlies. It would be good to check that this tool works in all other popular browsers (Chrome, IE 8-10, Firefox (release, Aurora, Beta), Safari, and Opera).

Currently searching all named subcomponents of Developer Tools. This could be easier by just matching all Developer Tools components.

Today I finally checked why some of our issues on github are not displayed on the bugsahoy website, even we tagged them as mentored. As it looked like my queries has the Python or Javascript filter activated, and all of our issues do not appear. Deselecting the language filter makes them appear.

I tried to add py for python, but that didn't help. So can we please add the handling of additional tags for the language to github related projects?

Here some examples of mentored issues:
https://github.com/mozilla/mozmill-ci/issues?labels=mentored&state=open

Either a wiki page on this project, or an actual wiki page on wiki.mozilla.org. Probably the latter is a better choice.