A new model for source control

Years before Github (or git, for that matter) existed, I was publishing my open source software on my own websites. However, larger projects (and eventually some of mine) used a website called SourceForge, which was a reliable source — you could trust downloads from that website. At some point, SourceForge offered CVS and/or Subversion support — for the youngsters, CSV and Subversion were other version control systems that predate git. Around 2007, Github launches and popularized Git and having a web-interface to manage your code and, more importantly, Pull Requests. Pull requests lowered the barrier to contributing to open-source projects for the first time. Traditionally, you would have to send a patch, or request write access to the repo. With GitHub, you can create a copy, work on your copy and use the web interface to request the maintainer to accept your change, with a nice-enough interface to do it without having to open the terminal or IDE. I am very surprised that this model…