9-volt / bug-life Goto Github PK

Follow https://9-volt.github.io/bug-life/?repo=streetcomplete/StreetComplete

Try to open one of links

It generates listing for StreetComplete

Implement caching feature.

When rendering a repo, the semicircles that display how long each bug lived is gone.

I can reproduce this issue on Chrome 51, Firefox 47 and Edge 38 All on Windows 10 preview

We do use Bootstrap and Boostrap docs theme. It is 130kb of data. Fonts take ~150kb of data.
Getting rid of unnecessary data may save a lot. giakki/uncss may be used for some tasks.

Research into cleaning unused JS parts (JS taker ~1Mb). Or at least use CDN for biggest libs (D3, jQuery).

Right now clicking on a region in stackedArea will display only that label in stackedArea. This does not affect semicircles. Both visualisations should be synchronised.

Either remove ability to select a label either make them change both visualisations.

When I use a token and enter whatwg/html, I get a graph that caps out at 338 on the right-hand side (i.e. at the present day). However, there are only 261 open issues on whatwg/html. Even if you were erroneously including pull requests, there are only 17 of those.

Any ideas?

Based on #2 .
We need to select few (3?) examples and add them to showcase (this section can be renamed).

Each example should have a screenshot (for those who'll not manage to see real graphs) and a description. Description may contain interesting facts like "it may be seen that in June many issues were closed because it was a release deadline" or "after May 2013 the project lost developers attention and issues grew up 3 times".

In order to reproduce:

1. Change repo input to something valid (but different from what is now)
   *. Change token (to a valid one)
   *. Submit token change

New visualisation will be loaded.

It is a desired behaviour, but I have no idea how it is triggered.

We need to find some interesting examples.
I would keep ruipgil/scraperjs, NYTimes/backbone.stickit and jashkenas/backbone.

It would be great if each example will have a charming, simple and clear description.
Examples can be ordered (by some parameter such as awesomeness).

Right now 'no label' is always added to list of labels.

It rises an error:
Uncaught TypeError: Cannot read property 'hasOwnProperty' of null somewhere in parser.js

Be aware that loading such a big amount of data with open inspector may crash entire tab.

Time scale

When clicked on them, nothing happens.

On window resize graphs adjust. With graphs that have 1 year of data it loads a powerful machine to 100% CPU for few seconds.
Research if it is caused primarily by animation and if yes then remove it.

It would be nice to have unique permanent URLs for sharing graphs.
For example: http://9-volt.github.io/bug-life/?username=deanmalmgren&repo=textract

Otherwise there is no way to share a specific graph.

Right now SVGs are emptied right before drawing on them.
If a SVG contains an old graph then there will be a small amount of time in which old graph will be visible. With huge data graphs this delay may take seconds.

I'm running this tool for ClickHouse/ClickHouse but the resulting graph is basically unusable: it renders very slowly and due to the "stacked" visualization I cannot see the dynamics of open issues with bug label.

Filtering by label will solve both problems.

When I graph the whatwg/html repo, only about the right 1/8th of the graph area is used. Could it instead spread out so that the earliest date is at the left side?

When I try it gets stuck on "Redirecting..." The URL is:

http://9-volt.github.io/bug-life/redirect.html?error=redirect_uri_mismatch&error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application.&error_uri=https%3A%2F%2Fdeveloper.github.com%2Fv3%2Foauth%2F%23redirect-uri-mismatch&state=%7B%22client_id%22%3A%22baf32f7bbb8d975e64f3%22%2C%22network%22%3A%22github%22%2C%22display%22%3A%22popup%22%2C%22callback%22%3A%22_hellojs_9xd5nzkc%22%2C%22state%22%3A%22%22%2C%22oauth_proxy%22%3A%22https%3A%2F%2Fauth-server.herokuapp.com%2Fproxy%22%2C%22scope%22%3A%22basic%22%2C%22oauth%22%3A%7B%22version%22%3A2%2C%22auth%22%3A%22https%3A%2F%2Fgithub.com%2Flogin%2Foauth%2Fauthorize%22%2C%22grant%22%3A%22https%3A%2F%2Fgithub.com%2Flogin%2Foauth%2Faccess_token%22%2C%22response_type%22%3A%22code%22%7D%7D

About section should be rewritten. It should contain:

• This project was done for GitHub data challenge
• Which data is targeted in this project (issues)
• Which data parameters are taken into account:
  • Issues labels
  • Issues lifespan (open - close time)
  • Issues agglomeration (how many issues are open at the same time)
  • Other?
• Interesting data that can be found
  • Bigger are semicircles - longer it takes to close issues. So big semicircles are bad
  • There are periods of times when many issues are closed. It may be related to releases
  • Different issues proportions
  • Other?
• If an issues has few labels - each label weight one unit in stackedArea chart
• Other?

If a user is not authenticated and tries to load a large project (like backbone), then the error "rate limit reached" is not displayed.