Theme pages now have a little “Theme SVN” link in their FYI box. This just gives a link to the theme’s SVN, for people that want to use it.
This is something several of the theme reviewers asked for, and it fits with the long term goal of allowing some theme authors the ability to directly update themes via SVN instead of using the ZIP file uploader. Encouraging SVN use is a good thing, I think.
Denis, 
Rich Pedley 6:52 pm on February 3, 2011 Permalink
That just lists all the versions, ala the ‘Other Versions »’ link on plugin pages. Shame it can’t be WordPress.org-ified rather than a simple listing though.
Otto 6:54 pm on February 3, 2011 Permalink
That’s what it’s supposed to do. The theme SVN isn’t organized like the plugin SVN, with trunk and tags and such. It just has one directory for each theme version.
Rich Pedley 7:28 pm on February 3, 2011 Permalink
So it could be pulled into a WordPress themed page then…
Dion Hulse (dd32) 1:13 pm on February 5, 2011 Permalink
Rich: Given it’s a SVN repo, I’m not really sure it’s possible to style it like WordPress.org. That aside, as it’s a SVN repo, it’s not designed to look like WordPress.org
Rich Pedley 8:09 pm on February 5, 2011 Permalink
On a site such as WordPress.org having unstyled pages like that is very un-professional. I still think the data could be pulled into a themed page, and even if it can’t I have seen better web front ends for SVN.
Peter Westwood 10:08 pm on February 5, 2011 Permalink
You can style the SVN web interface but I wouldn’t want to be the person writing the XSLT to do it – it’s not fun and you won’t make it look much better – I don’t see why it needs styling at all.
Alex M. 6:58 am on February 6, 2011 Permalink
If you want to look at a pretty version of the code, then use the plugins Trac instead of browsing the directory via SVN. Or even better just use a proper SVN client.
The SVN repository isn’t really meant for browsing with your browser.
Matt 6:14 pm on February 6, 2011 Permalink
I think it would be worth a little XSLT to just put a note at the top, like “This is blah blah blah for the plugin’s page please see LINK or visit WordPress.org.”
Radhe 6:45 am on February 4, 2011 Permalink
This is welcome addition,
but I do think “trunk” folder should be given, that will be helpful when author modify theme code in response to theme-users support request.
Dion Hulse (dd32) 1:13 pm on February 5, 2011 Permalink
Could we get the same thing for Plugins?
Otto 6:00 pm on February 5, 2011 Permalink
Plugins have had the SVN links in their Admin sections forever. Not sure it’s worth exposing them on the public side of things.
Dion Hulse (dd32) 10:34 pm on February 5, 2011 Permalink
Not everyone has access to the admin section of every plugin.
I personally see SVN access for Plugins as more useful than for Themes. Every task is common between them however (Other than Theme review team stuff, but thats a not a normal front end task anyway). Allowing easier access to the SVN repo from the plugins page will help people who are not aware of SVN get into it at well, encourage them to use svn..
One of the first thing I do, and I’d hope other Plugin developers do, is open the plugins SVN repo and take a glance at the code, it’s what tells me if I’m going to atttempt to use it or not. That’d be my main use for it for Plugins (as well as for Themes).
Rich Pedley 9:37 am on February 7, 2011 Permalink
erm plugins already have a link to the Development log in the FYI box. This was what I was referring to when I thought that the themes should match it.
Denis 6:00 am on February 12, 2011 Permalink
Slightly off topic, but… It just occurred to me that the default vote for compatibility was for 3.1 at a time where it was not released. As much as I like the idea that one can vote on works/broken for the latest beta/RC, it seems to me that the vote should apply to the latest and greatest *released* WP version by default. (Or maybe it already is the case, in which case it’s not clear at all…)
Denis 6:01 am on February 12, 2011 Permalink
i’m meaning for plugins, btw. But since you’re also worrying about that and I can only assume the same logic applies for themes, I figured I’d raise it here.