It might be old news to the members of the Ontopia mailinglist, but we kinda forgot to update the rest of the world. So here it is.
As Google announced to shut down GoogleCode back in March 2015, we set out to find a new home for the Ontopia code base. GoogleCode would go into read-only mode in August, so we had to find a new home before this happened or we would loose the ability to commit new changes to Ontopia.
During the discussions on the mailinglist, we came to a option-limiting conclusion: the Subversion repository was broken. It seems that during the work on making Ontopia modularized with Maven we managed, among other issues, to modify non-existing files. These issues blocked us from synchronizing the repository into a new Subversion repository location. This also broke the Ohloh (now OpenHub) code analysis.
As GitHub was a favorite on the mailinglist and Google offered a migration tool, we decided to give GitHub a try. In April 2015 a first GitHub Ontopia repository was created, and after some minor obstacles the entire codebase, wiki’s and issues were migrated to GitHub successfully.
By June, no objections or problems had been reported regarding moving to GitHub. The final migration to GitHub was announced to the mailinglist on 17th of June 2015, and the GoogleCode site was put into project-moved status.
As of then, the Ontopia code is located at https://github.com/ontopia/.
The new location’s layout was changed during the migration:
- The main Ontopia code is in the ontopia repository. Releases and distributions are created from this code.
- Trunk, tags and branches were modified to Git equals.
- The Sandbox was split off into a new sandbox repository.
- The Ontopia maven-repository was NOT moved. GitHub could not directly host these files, and we were already looking for releasing Ontopia into the maven central repository.
- Migrated issues were anonymized, as the migration tool could not recreate the users that reported the issue on GoogleCode.