In many cases, it probably depends on the workflow that a project uses. You don't get mailling lists on GitHub. Don't laugh at mailing lists--they're important to a lot of projects, including the Linux kernel. Also, Subversion support is still experimental on GitHub. If I had an older, mature project, based around these two things, I'd want to stay on Sourceforge. For example, there are probably lots of libraries dating back to the days when Sourceforge was the best of few choices, and that are nice and stable, get the job done, and require only maintainance. Why fix it if it isn't broke? Infrastructure doesn't have to be cool to be very, very useful.
Sourceforge also provides a means of distributing or completely elliminating download bandwidth needs. http://scipy.org/ is the Web site for important numeric Python stuff (scipy and numpy). But the download links point to Sourceforge. They also use GitHub; for some a mix of services is best.
So, yeah, I'd say Sourceforge is still important to a lot of people. Not all of whom are aware of it.
I don't expect _any_ future president to disband TSA. At least not until the world become a Provably Safe Place (TM), or massive public resistance develops. Any politician skilled enough to be up for the job (or a Senate seat, etc.) is going to see that as accepting a lot of risk. There would certainly be an outcry from those who want the government to protect them from _everything_. If there were another attack afterwards, the politician(s) who were involved in dismantling it would then be toast.
Evidence for progress seems a bit thin. Even a very senior Cardinal has said that the Catholic Church is 200 years behind the times.
http://www.bbc.co.uk/news/world-europe-19453974
In less than a century, computers will be making substantial progress on ... the overriding problem of war and peace. -- James Slagle