FWIW, Mark Jaquith is a lead developer for WordPress.
I hope this is an indication they're considering a switch to Git for the future. It makes a lot of sense to me consider the distributed nature of Automattic's workforce and the large number of contributors to the codebase.
WordPress has a lot invested in SVN, so it wouldn't be a trivial switch. I imagine we'll switch eventually, but there are no concrete plans at this time. I actually use Git and git-svn to do all my WordPress core development:
Drupal made the switch to git (from CVS) not too long ago and it's worked wonders for them. It's still a challenge, but they should have an easier time coming from svn, if they were to make the switch. The tools for conversion are quite mature.
One of the pain points I have in freelancing is automatically updating a Wordpress installation without having to check whether it is up to date. Automating these updates via Chef/Puppet would be great, as it would also allow me to include patches into Wordpress where necessary, as well as alleviate the need for me to remind the bloggers to update.
Believe it or not, just because there is a notice that a new version of free software is out, doesn't mean any non-technical person will follow through with the notice.
I quite literally just got access to the "wordpress" account on GitHub within the last 48 hours. I'll be working to get that one update automatically again.
Would there be any problems (aside from the people who've cloned this git repo already) if you got rid of the -branch in branch names? Seems awfully redundant in git. If not, I think it would be an improvement and the sooner the better!
Is this just the Wordpress code on Github or is it a variation of Wordpress that implements some sort of DVCS system? I am thinking the former. I ask because of the title.
I think you mean VCS (version control system)? I say this because they already to use SVN at this point.
But to your point, indeed. The open-source community does pay attention to what's on Github. I'd love to see Wordpress move over to github - It would certainly make me follow the development closely and probably fix outstanding issues. Git (and pull requests on Github) make contributing so easy, it just makes sense.
[+] [-] calvin|14 years ago|reply
I hope this is an indication they're considering a switch to Git for the future. It makes a lot of sense to me consider the distributed nature of Automattic's workforce and the large number of contributors to the codebase.
[+] [-] markjaquith|14 years ago|reply
http://markjaquith.wordpress.com/2011/05/26/developing-on-wo...
[+] [-] timdorr|14 years ago|reply
[+] [-] josegonzalez|14 years ago|reply
Believe it or not, just because there is a notice that a new version of free software is out, doesn't mean any non-technical person will follow through with the notice.
Kudos on this.
[+] [-] jpetazzo|14 years ago|reply
And, most disturbingly, there is also https://github.com/wordpress/wordpress, which looks more "official" but wasn't updated since about 1 year.
It would be awesome if WordPress would publish the official stuff under the wordpress github account - there would be less confusion, IMHO.
[+] [-] markjaquith|14 years ago|reply
[+] [-] benatkin|14 years ago|reply
[+] [-] mmuro|14 years ago|reply
[+] [-] yariang|14 years ago|reply
[+] [-] nbpoole|14 years ago|reply
> WordPress, Git-ified. Synced via SVN every 30 minutes, including branches and tags!
[+] [-] jhawk28|14 years ago|reply
[+] [-] zachshallbetter|14 years ago|reply
[+] [-] fredoliveira|14 years ago|reply
But to your point, indeed. The open-source community does pay attention to what's on Github. I'd love to see Wordpress move over to github - It would certainly make me follow the development closely and probably fix outstanding issues. Git (and pull requests on Github) make contributing so easy, it just makes sense.
[+] [-] _hnwo|14 years ago|reply
[+] [-] jsdalton|14 years ago|reply