In reply to Alec Kinnear.

First off, GitHub is not the only managed git repository service out there. There are many self-hosted options (even GitHub offers one), and there are many completely free ones (for example GitLab). If you think the reason WordPress doesn't use git is because of price or somehow related to licensing concerns, neither of those have anything to do with it. As I'm sure you're aware, pricing has nothing to do with GPL compliance when done in accordance with the license.

Nor does WordPress core really care about git vs svn. Both are version management systems, and frankly they're both roughly equivalent to learn. It just so happens many people in WordPress are familiar with git because of GitHub. That doesn't make git easier to learn. Just as there are 1 button push GUIs for git, there are many of the same equivalents for SVN. You don't even need to know how to use SVN on a terminal, the same way you don't need to know how to use git on a terminal.

There are many actual considerations, some of which may never be satisfied with GitHub. For all the talk there is about how WordPress should just switch, or how easy it is, it's one thing to be a person saying it, and its quite another to be the person doing that. That being said I have no desire to start some lengthy tack on discussion to a completely unrelated article, so I won't be monitoring this post for replies.