[wp-meta] [Making WordPress.org] #3207: Contributors in plugins/update-check/1.1/

Making WordPress.org noreply at wordpress.org
Wed Oct 18 16:21:37 UTC 2017

#3207: Contributors in plugins/update-check/1.1/
 Reporter:  blobfolio     |       Owner:
     Type:  enhancement   |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  API           |  Resolution:  maybelater
 Keywords:  dev-feedback  |
Changes (by Ipstenu):

 * status:  new => closed
 * resolution:   => maybelater


 So this is _already_ documented in the info API (see
 https://api.wordpress.org/plugins/info/1.0/akismet for an example) and
 shouldn't be too hard to port over if we wanted.

 But that doesn't solve the tracking issue, which is not actually an API
 one, but ties back to a logging one. Really this should be tracked in the
 adult log - https://meta.trac.wordpress.org/ticket/2717

 Adding the contributors to the update information doesn't strike me as
 beneficial in the long run, since we also grab the readme for data on the
 update anyway and that already has the authors. And since the devs can't
 change the 'owner' of a plugin (only plugin team admins can at the moment)
 that wouldn't actually be changing in a way that would be useful.

 In the end, all this method would do is ''after'' the fact let people know
 there was a new author, which really they'd know by the changed from the
 readme, and could be grabbed, parsed, and stored in options if needed.

 Ultimately, I don't think this solves the root of the issue, which really
 is "We need to track ownership changes because some people are naughty
 developers." This just pushes that down the road and would require people
 to actually notice the change. As we increase the reliability of updates,
 the more people automate those things, and the less beneficial that would
 be :/

Ticket URL: <https://meta.trac.wordpress.org/ticket/3207#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list