Contents:
- Gitorious' announcement
- Google Code's announcement
- Getting in contact with developers
Gitorious' announcement
Gitorious had from March 3rd, 2015 a banner on their site saying:
System notice: Gitorious is being acquired by GitLab and gitorious.org will shut down end of May. Please import your repositories to GitLab.com - Read about it
The following can be found in the link labeled "Read about it":
Apparently Gitorious ran into the predicament that they in a foreseeable future not be able sustain having the free Gitorious.org service:
Rolf Bjaanes, Gitorious CEO wrote:At Gitorious we saw more and more organizations adopting GitLab. Due to decreased income from on-premises customers, running the free Gitorious.org was no longer sustainable. GitLab was solving the same problem that we were, but was solving it better.
Gitorious will be available until the end of may and there is tools available to import Gitorious repositories to GitLab:
Starting [March 3rd 2015], Gitorious.org users can import their existing projects into GitLab.com by clicking the “Import projects from Gitorious.org” link when creating a new project. Gitorious.org will stay online until the end of May 2015 to give people time to migrate their repositories.
Google Code's announcement
Only a few days later, March 12th, 2015, Google announced that they would shut down Google Code in steps.
Beginning [March 12th, 2015], we have disabled new project creation on Google Code. We will be shutting down the service about 10 months from now on January 25th, 2016. Below, we provide links to migration tools designed to help you move your projects off of Google Code. We will also make ourselves available over the next three months to those projects that need help migrating from Google Code to other hosts.Google will continue to provide Git and Gerrit hosting for certain projects like Android and Chrome. We will also continue maintaining our mirrors of projects like Eclipse, kernel.org and others.
- March 12, 2015 - New project creation disabled.
- August 24, 2015 - The site goes read-only. You can still checkout/view project source, issues, and wikis.
- January 25, 2016 - The project hosting service is closed. You will be able to download a tarball of project source, issues, and wikis. These tarballs will be available throughout the rest of 2016.
Google have tools available for export to a few repository hosts:
The simplest way to migrate off of Google Code is to use the Google Code to GitHub exporter tool, which provides an automated way to migrate a project’s source, issues, and wikis to a new GitHub repo. Please note: GitHub’s importer will convert any Subversion or Mercurial Google Code projects to use Git in the process.
We also offer stand-alone tools for migrating to GitHub and Bitbucket, and SourceForge offers a Google Code project importer service.
Getting in contact with developers
FlightGear itself have taken some measures such as migrating to SourceForge[1].
Many small development repositories may not have migrated yet, in particular if the developers/maintainers have been absent from FlightGear for a while. Most of them would probably be happy that someone cared to tell them that there is a need for them to migrate their repositories. (Please use a meaningful subject line and consider linking to the relevant announcement or this post.)
In those cases where contact can not be made with the maintainers (email addresses can often be found somewhere), one of the upsides with open source software is that a repository can be cloned and forked (do mind the licenses though).
Edit: Now, how do I make this a sticky?