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.
Kudos on this.
There seems to be another mirror: https://github.com/dxw/wordpress
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.
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 have a feeling that WordPress will begin to pull (even more) heavily skilled developers if they move to a structured SVN system like this.
Despite it being under Mark Jaquiths name, are you really going to trust what is still an unofficial git repository of wordpress?
This is great. I'd be doubly excited if they got the WP plugin repository on Github as well.
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.