There is still some code hosted on SourceForge that has no other public source. This is unsettling because I don't know how long SourceForge will continue operating and Wayback Machine captures of SF pages don't include tarballs. Download backups yourself whenever you find something like this.
I'm contributing to someone's software that started as an academic project. The current version is on GitHub with history back to 2014 but early releases back to 2008 (from before the author started using version control) are on SF in the form release_1.0.tgz, release_1.1.tgz, etc. I stumbled on these old versions this weekend while looking for related material. Once I decompressed them I found that they contained notes and old code that really helps to understand the current project's evolution and structure.
Yeah, what especially irks me with SourceForge is the common habit of projects regularly deleting all outdated releases (due to some per-project size limit? or just not to clutter up the list?). In old projects with messy releases, it can be very hard to piece together exactly which revisions went into a version "x.y.z" that everyone else depended on, except by actually looking into the released files. If those files don't get archived anywhere, they just get lost to the ether. (At least, short of a manhunt for anyone with the files in an ancient backup at the bottom of the sea.)
I'm contributing to someone's software that started as an academic project. The current version is on GitHub with history back to 2014 but early releases back to 2008 (from before the author started using version control) are on SF in the form release_1.0.tgz, release_1.1.tgz, etc. I stumbled on these old versions this weekend while looking for related material. Once I decompressed them I found that they contained notes and old code that really helps to understand the current project's evolution and structure.