When I get a package in Racket or R they normally come from github automatically.
> I don't see how SourceForge will ever be dethroned due to the mind share and market share of Open Source projects.
Options help in keeping all actors sober and sane
History has proven time, and time again that any of the giants can and will fall.
IMO they continue to innovate quite quickly, on multiple fronts.
Are we that quick to forget articles like this: https://news.ycombinator.com/item?id=10904671
There are few faster ways for someone to ensure I cross their product off my list of things I consider production-ready than to do this.
Everything is relative and it isn't always a cardinal sin to tie some parts of ones product to github, but it's a common non-decision and overall I consider it a clear sign that the product developer lacks foresight. If they are short-sighted enough to design their system in a way that it will break if github goes away and supports no substitute workflow, I have to wonder what else they might be short-sighted enough to do.
Care to explain? You don't use Python or other languages where the libraries are built off code that is on github???? You want it hidden into some strange package management system that is closed to developers?
More importantly, the Pypi project is open source, which means I can set up a Pypi server inside my company to host private and/or critical packages and configure it to go upstream for anything I request but don't have locally.
The Python strategy is a considered strategy that provides acceptable business continuity options.
I don't give a shit where you store your source code, that's /your/ business continuity problem.
If you have any contributors you have it on github (normally) or any other git you want and then push it to pypi. THis is why any major library of Python is developed on Github.
I actually don't use github for anything except my public open source code, but almost every single Python library is on github and then pushed to pypi as a final step.