Open findleyr opened 6 days ago
It'd be nice to stick to static content, so I'd avoid the download form. People can script downloads easily enough. The others all sound good. I agree with the minimum requirements, and let's focus on doing those before anything else. Thanks!
It would be nice if this page prominently displayed how to opt in/out of telemetry collection, or at least linked directly to https://go.dev/doc/telemetry#config. Right now it is a bit circuitous to figure out: first decide to click the "learn more" link to https://go.dev/doc/telemetry, and then decide to go to the "Configuration" section.
We should show a summary of recent data. For example, we could choose a selection of charts, and generate them based on data merged from the last week of reports. This may require some pre-processing on the worker.
will require merging of data and extra work.
It the work seems like a Stretch goal, an easier way would be Filter on date range and provide Next pagination on individual date page.
It the work seems like a Stretch goal, an easier way would be Filter on date range and provide Next pagination on individual date page.
@ansaba just to make sure I understand the suggestion: you mean rather than merge the last week of charts, just show the most recent day's chart, with a pagination to go back/forward in time. Agree we can do that if we don't have time to merge data. Longer term it would be nice to see the prior week's data, since the upload happens once a week and so the past week of data represents active users.
The front page of https://telemetry.go.dev is still largely a placeholder. We should improve it prior to the Go 1.23 release, which includes support for opt-in telemetry. At that time, people will want to know more about telemetry, as well as view telemetry data that has been collected thus far.
There is a lot of room for improvement, since the page is currently just a bunch of links. We discussed this in our team meeting, and had a few ideas for how it could be improved. More ideas are welcome.
Minimum requirements
Other ideas
CC @golang/telemetry @ansaba @h9jiang