Menu

I talked to a number of developers about at this year’s WordCamp SF about where best to publish WordPress code as a developer.

We definitely want to use the SVN repositories on WordPress.org so that released plugins can be easily available to the community, but there is very little developer community there. We’ve also used Google Code hosting in the past. It’s nice to have issue tracking, etc. but again there is not much community there. GitHub has a vibrant developer community and great collaboration tools, but it’s Git and the WordPress developer community infrastructure runs on SVN.

After a good bit of discussion within our team and discussion with other WordPress developers, we’ve decided to move everything to GitHub. We’ll still push the code to the WordPress SVN repos as a packaging step, and will occasionally have to maintain mirrored SVN repositories for specific projects; but the active development will happen in GitHub.

We have a few different projects that I think will really benefit from wider community involvement. In particular, we’ll be moving over our Carrington Core theme platform, our CF Revision Manager plugin, and our CF Post Formats code (which I moved earlier this week). Over time, we’ll get everything moved over – I’m hoping that we’ll start seeing forks and pull requests for these projects on GitHub.

Personally I’m going to be putting more and more code snippets on GitHub so that I can make code more generally available to the community without needing to package it up a plugin.

This post is part of the project: Revision Manager. View the project timeline for more context on this post.

Nice. So far it’s been pretty easy to just copy the files over by hand when it’s time for a release and commit in SVN (or put the .git folder into the SVN trunk and commit both from the same changes for more active development).

I’ve been using Git for my Drupal development at work, and I was on a train without Wifi one day wondering why I wasn’t taking advantage of a DVCS for my WordPress projects.

I’m following the opposite approach from you. As long as the plugin repo officially supports SVN, that’s where the official trunks live. But, I’m manually checking changes into Git as well so I have code I can mess around with on the road.

Drupal’s Git migration earlier this year went smoothly. I really ink WordPress should follow suit.