Re:Introducing the new SourceForge
by kbumsik on Tuesday January 09, 2018 @03:11PM
(#16109527)
Out of curiosity, what is the benefit of hosting binaries on SF over GH releases?
[ Parent
| on HN ]
Re:Introducing the new SourceForge
by loganabbott on Tuesday January 09, 2018 @03:16PM
(#16109573)
We get over a million users per day looking to download OSS. If you have binaries on SF you can reach these people through our very robust discovery tools and strength of our search results in Google. We also give project admins detailed download statistics.
Re:Introducing the new SourceForge
by NCommander on Tuesday January 09, 2018 @03:30PM
(#16109727)
Are there any plans to push this code back upstream to Apache? My understanding is SF.net abandoned the legacy alexandria (the PHP code from VA Linux) source code, built the current version, and then sent to the Apache Foundation, but I'm not clear if this is a fork, or what sf.net's relation is with it's upstream.
Also, since I'm on the topic, any chance slashdot will go back to an open source code model?
Re:Introducing the new SourceForge
by john_moscow on Tuesday January 09, 2018 @03:21PM
(#16109624)
I'm sorry to be the party pooper here, but it looks like the relevance war to Github was lost ~7 years ago:
https://trends.google.ca/trends/explore?date=all&q=github,so...
Re:Introducing the new SourceForge
by loganabbott on Tuesday January 09, 2018 @03:26PM
(#16109679)
GitHub is much larger by traffic, but that doesn't mean we are going to abandon the million users we get every day and the 430,000 projects hosted at SourceForge. It's not a zero sum game. Some people like using GitHub's suite of tools, while also taking advantage of SourceForge mailing lists, project website hosting, detailed download statistics, and distribution/discovery capability. Our GitHub Sync Tool lets project owners use both with ease.
Keep competing! Alternatives are good!
I agree. After Github recently locked my private repos and demanded payment to unlock them, with no option to simply make them public instead, I'm 10,000% supportive of getting new (or, in this case, refreshed) competitors in that space, whether I plan to use them or not.
Settings -> Danger Zone -> Make Repo Public
Just did it, it works just fine.
Re:Introducing the new SourceForge
by greenhouse_gas on Tuesday January 09, 2018 @04:32PM
(#16110315)
How did you create a free private repo to begin with?
Re:Introducing the new SourceForge
by joatmon-snoo on Tuesday January 09, 2018 @09:26PM
(#16112109)
Expiration of a student license, maybe?