[wp-hackers] Plugin Version Control & Source Code Hosting?

Beau Lebens beau at dentedreality.com.au
Thu Mar 19 22:28:49 GMT 2009

You should be able to just do the following (using my own as an
example, although don't know for sure that's always the case).

Plugin page: http://wordpress.org/extend/plugins/sparkplug/
SVN URL: http://svn.wp-plugins.org/sparkplug/

So just replace "wordpress.org/extend/plugins" with
"svn.wp-plugins.org" and you have the URL (although in my case, you
also need /trunk/ on the end).

You're right though, it would make sense (and make life easier) to
just have the corresponding URL appear on that page so you could
easily copy-paste. Perhaps even have an automatically generated page
that describes the checkout/externals details for using that plugin
(could be linked under the Download button?)

+1 for this.

On Thu, Mar 19, 2009 at 3:14 PM, Eric Marden <wp at xentek.net> wrote:
> On Mar 19, 2009, at 5:24 PM, Peter Westwood wrote:
>> My recommendation, use subversion externals.
> It would be great if you could see the read-only svn URLs for plugins in the
> extend db on the plugin page. I know right now its on the admin tab of
> plugins you manage, but being able to easily get the svn URL for power users
> would be the most amazing thing ever. You can kind of guess the URLs but
> since many addresses and plugin names aren't exact (including with some of
> my own) it is an error prone process. I'm a big fan of svn:externals and
> would love to be able to pull the source of plugins directly into my svn
> managed WordPress sites, just like I do for the WordPress core files
> themselves.
> - Eric Marden
> http://xentek.net/code/wordpress/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

Beau Lebens
Dented Reality
beau at dentedreality.com.au

More information about the wp-hackers mailing list