Open uazo opened 8 months ago
ArthurSonzogni
commented
8 months ago Thanks!
So you are proposing:
Interesting. What would the data be used for on the website? What can we display?
uazo
commented
8 months ago Thanks!
But of course! I can imagine how long it took to do it...
What would the data be used for on the website?
I think it might be interesting to see what components the chromium team is working on. because, changes on blink side are well tracked, as opposed to those on the browser.
What can we display?
Some time (ehm.. years :) ago I had investigated how to do the scraping of bug.chromium.org, but unfortunately it was not easy, I do not know whether now with issues.chromium.org it is different, nor whether there are specific endpoints available for data acquisition. so, I think it is based on what can be retrieved, probably eliminating what is susceptible to change, such as status or priority, or keep track of it until the bug is closed. perhaps only features (component + os + milestone) and are interesting to trace... I personally would also like to know which bugs are googlers only, because I have noticed lately that many ui-related bugs are closed and I do not understand why.
ArthurSonzogni
commented
8 months ago I would love it. If you know a way to retrieve all the data from https://issues.chromium.org, we can probably do something interesting with it.
uazo
commented
8 months ago well, I like challenges. obviously without any ETA.
If you know a way to retrieve all the data
no, I don't know. i can only imagine that the best method is to drive a browser from outside and retrieve the information via css rules (or ad-hoc interventions on blink, i think i can do that). but I wouldn't know how to ensure that the data is acquired correctly.
Beautiful work, well done. Would it be possible to allow grouping by bugid and/or for other id-related information such as the component tag?