[wp-trac] Re: [WordPress Trac] #5117: WordPress (plugin) updates do not warn about unknown plugins

[WordPress Trac]

#5117: WordPress (plugin) updates do not warn about unknown plugins
----------------------------+-----------------------------------------------
 Reporter:  Quandary        |        Owner:  matt 
     Type:  defect          |       Status:  new  
 Priority:  high            |    Milestone:  2.3.1
Component:  General         |      Version:  2.3  
 Severity:  normal          |   Resolution:       
 Keywords:  admin, plugins  |  
----------------------------+-----------------------------------------------
Comment (by zamoose):

 Replying to [comment:6 jaredbangs]:
 > I additionally suggest (once Mark's "status unknown" mentioned above is
 in place), that there be a hook that plugin devs can use that fires only
 for "status unknown" responses.
 >
 > That way, if plugin devs want to roll their own update notification
 system, they can do so, but still have the core only check the official
 repository.

 I would actually suggest that ANY plugin that wishes to utilize the
 official WP update beacon create at least a stub README in the official
 repo.  There should be a portion of the file that allows developers to
 point to their own download location (hosted wherever they desire) and
 then pass that URL along to the end WP "client" installs.

 This has three distinct advantages, IMHO:

  1. A fairly comprehensive '''official''' listing of WP-sanctioned plugins
 can be maintained.
  1. Misbehaving plugins can easily be de-listed.
  1. End WP clients spend no extra time hitting other update beacons.

 There is a perceivable downside:  all plugins must be GPL-compatibly-
 licensed.

 What if only the README was GPL-licensed?  Might this get around this
 constraint?

-- 
Ticket URL: <http://trac.wordpress.org/ticket/5117#comment:7>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software