[wp-trac] [WordPress Trac] #22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)

[WordPress Trac]

#22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)
--------------------------+------------------------------
 Reporter:  Viper007Bond  |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Plugins       |     Version:  3.4.2
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |
--------------------------+------------------------------

Comment (by MikeSchinkel):

 Something else to consider about dependent plugins which I'd like to pose
 as somewhat rhetorical questions:

 - Are plugins that themes and other plugins depend on mostly things an
 end-user would install independently, or are they mostly things that an
 end-user would likely never install on their own?
 - If the former, what are some examples?  But if the latter would it make
 sense to treat these ''"depended on"'' plugins differently than existing
 plugins?

 Specifically, if these ''"depended on"'' plugins are mostly API/libraries
 would it not make sense to consider ''(also)'' pulling them from GitHub
 instead of the WordPress plugin repository where end-users go to search
 for plugins?  GitHub is emerging as the place developers post code to
 share and collaborate ''(note: I personally prefer Hg for version control,
 but GitHub has no peer in enabling collaboration.)''  The primary benefit
 to GitHub IMO is the fork/pull model that allows developers to more easily
 collaborate.

 The current plugin repository makes it very difficult to collaborate ''(I
 believe that issue was discussed at the summit, directly or indirectly
 regarding abandoned plugins?)''  If API/libraries are pulled from GitHub
 then these emergent APIs will likely be fewer in number but much better in
 depth and robustness. Rather than have every developer create yet another
 API/library for the same purpose it will be easier to make an enhancement
 to an existing API/library because of forking, and easier to get the
 original developer to accept the enhancement because of pull requests.

 Which brings up a corollary, should API/library plugins even be included
 in the WordPress plugin repository where end-users go looking for plugins
 to install?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/22316#comment:43>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software