[wp-meta] [Making WordPress.org] #6511: Provide helpful plugin stats and insights

[Making WordPress.org]

#6511: Provide helpful plugin stats and insights
------------------------------+-----------------------
 Reporter:  markzahra         |       Owner:  (none)
     Type:  feature request   |      Status:  reopened
 Priority:  high              |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by Cybr):

 Instead of processing all data whenever requested, a caching strategy
 could have been implemented via middleware or other means. Launch a new
 server to offload this heavy processing. If the processes crash, simplify
 them into manageable chunks. Set a flag once a plugin's data is ready to
 be publicized. WordPress also comes with a transient API that makes much
 of this easy. A disclaimer could've been added to inform us that the data
 is not real-time but from three days ago. Anything could've been done; we
 never asked for something perfect, only something at all.

 It's unfair to leave us in the dark for so long and then present excuses
 to a room full of senior developers. These issues should have been
 communicated months ago when they were first encountered. We are not
 business assets or churning users — we're contributors to the WordPress®
 project, the ones who breathe life into it. The process matters to make us
 at least pretend like we're part of it.

 Feel free to use my plugins and publish their aggregated data. I'm
 intrigued to see what I never before had access to.

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