[xte]

Of course, like the trend "hey if it does not work for you write down your code"...

On git only: what is another remote? A GitHub concurrent company? A personal dyndns from a single developer with a fable ADSL?

On GitHub: many use it's proprietary characteristics like PR, wikies, pages etc. That's not "portable" to any other remote if you do not count site-scraping...

No, we need to focus on distributed/decentralized solution now.

In the past at least we use tons of different hosting most of them offered by ISP that actually use hosted projects, universities that actually participate in many FOSS project so while not distributed we are decentralized on "friendly" systems. Not nearly all FOSS project is on a super-big-corp server. Without any viable alternative ready to use.

[mroche]

> On git only: what is another remote?

A remote is a URL location of a repository. A local git repo can point to multiple remotes by using the git remote <opts> functionality. For instance, you can point your local repo to GitHub, GitLab, and BitBucket and choose which to push to using the command git push <branch> <remote>.

[xte]

Hem, no perhaps is my poor English but you do not understand: I know what a git remote is. My point is what kind of "other remote" a typical FOSS project have these days?

In the past we have tons of hosters so we can easily spread our code in many "mirror", now there is GitHub and few others, mostly on the very same "cloud".

I mean you have no damn viable remote. Single devs can share code P2P but nothing that can work instantly out of the box.