[wp-meta] [Making WordPress.org] #1155: Plugin API should include active installs

[Making WordPress.org]

#1155: Plugin API should include active installs
-------------------------+-------------------------------
  Reporter:  McGuive7    |      Owner:
      Type:  defect      |     Status:  closed
  Priority:  normal      |  Component:  api.wordpress.org
Resolution:  worksforme  |   Keywords:
-------------------------+-------------------------------

Comment (by McGuive7):

 Thanks for the reply, definitely helpful to hear a more in-depth
 explanation of the methods at play behind the scenes. A few more
 questions/comments:

 1. I respectfully disagree that rounding to the first significant digit is
 an appropriate method here. For plugin developers attempting to
 improve/optimize thing, more granular growth data may have less to do with
 ego and more to do with reaching a wider audience for whom a plugin may be
 beneficial. In light of your explanation (which was great, thanks), I
 still fail to see the downside of maxing out rounding at, say, the nearest
 1,000. Is there a downside to showing 15,000 instead of 10,000?

 2. Documentation - again, is full documentation available anywhere for
 this API? I'm able to piece together some of the params that are passable
 to `plugins_api()` from looking into core source (e.g. /wp-admin/includes
 /plugin-install.php), however it'd be helpful to see a list of ''all''
 possible params, or even better yet, is it possible to look at the source
 code for the API itself?

 3. Is there a doc/page that outlines what sections of the meta side of
 things are and aren't available for patches? I've been pretty confused
 trying to track down ways to submit patches to the .org/meta side of
 things. Thanks!

 Thanks for your time and assistance!

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1155#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org