One key point that I think this article missed is the activation energy required to create a new project. On SourceForge, at least when I last used it, it was a

One key point that I think this article missed is the activation energy required to create a new project. On SourceForge, at least when I last used it, it was a very involved, explicit process, where you created a new project and went through several screens of populating license, status, etc., and then you finally had a place where you could stick code. Whereas github lets you get a repo up and running with just about a single click and a 'git push', and then add on features and information as you grow. So it became the place to stick all of your one-off, throwaway, or experimental code, which got developers in the habit of using it, and it also had the room to grow if once of those things grew into a "real" project.