search

ansible / galaxy-issues

This repository exists solely for the tracking of user issues with Ansible Galaxy.
20 stars 3 forks source link

Show role download count #20

Open gregdek opened 9 years ago

gregdek commented 9 years ago

Ambivalent about this one. This creates a "first to the post" mentality; a role doesn't have to be "good" to get to the "top" position in a particular category. Still, in the absence of other better quality metrics, people want it, and maybe something is better than nothing.

geerlingguy commented 9 years ago

Note that this was debated in the Drupal community for ages, and ultimately it was decided that it would be added to project pages, but with minimal priority/importance in relation to other elements on the page. See, for example: https://www.drupal.org/project/honeypot

Since Ansible can't track 'reported installs' like Drupal.org does, it might be good to give a little more prominence to things like "Github issue count (total/closed)", "Oldest issue" and things like that.

Agreed that it's hard to show one or two metrics while mitigating the 'first to the post' problem.

gregdek commented 9 years ago

We won't have any historical data here, but we need to start somewhere. Two things we'll need:

  1. A distinct endpoint for downloads (maybe use the same one and change the web UI endpoint? That way we don't have to change clients in the field. Or maybe we make this a new 2.0 client feature; )
  2. A place in the database to store the data.

Maybe just add a request header in the Galaxy client so we know that's it a hit?

wenottingham commented 9 years ago

... is this better/worse than just proxying watch/star/fork?

geerlingguy commented 9 years ago

I still like having that metric available, as downloads are an indicator of actual (and ongoing) use, whereas stars are an indication of interest/intrigue.

gregdek commented 8 years ago

Slipping to 1.2