I hate Subversion

Pull Requests make Open Source Software.

GitHub makes Pull Requests easy.

When Pull Requests are easy, it encourages tinkering and sharing your changes upstream.

WordPress insists on using Subversion for the plugins repository.
This makes tinkering and sharing changes quite difficult, as it has to be done through some external means of communication.

What I would love would be if WordPress.org started using GitHub for the plugins repository.

Short of that, I would like to host my plugin on both GitHub and the WordPress Subversion beast. I would like both repositories to always be in sync.

This is far easier said than done.

I have been able to import my WordPress plugin’s Subversion repo to Github, but I still don’t really have a way to push to both locations at the same time.

Yes, I have tried git-svn. What a mess.

I guess I will probably end up using GitHub for development, and just publishing to WordPress Subversion when something is ready for release.

Like some glorified beast of an FTP server.


Update: To give credit where credit is due, Andrew Nacin has been doing a ton of work to imrpove WordPress Core Trac.

This isn’t exactly what I was most upset about, and I still don’t think it is nearly as simple as GitHub, but it is clear that I am not the only one who craves more from WordPress.org.


Update: It seems WordPress is taking my advice and trying to make Git a first-class citizen of WordPress development. For the moment, commits will still only be accepted via SVN, but they mention that they are looking into ways to change this, as well as mirroring the projects on GitHub in a way that makes more sense for contributers.

 
6
Kudos
 
6
Kudos

Now read this

WebVTT Observations

Update The WebVTT Draft Spec has been updated to allow metadata headers. This corrects all the issues outlined in this post. :) According to the WebVTT Draft Spec, a WebVTT file must start with the string “WEBVTT” followed by some text... Continue →