Migration from Google code

[Quintin Siebers]

Dear Ontopia users, developers,

Recently, Google announced that they will be shutting down Google code per Januari 2016. Committing changes will be shut down per August 2015. This means we have to find a new location to host the Ontopia project. I’d like to start a discussion on this list regarding alternative hosting locations along with pro’s and cons.

For starters:

- Git Hub
- SourceForge
- Bitbucket

With regards,

Quintin Siebers

--
q.si...@mssm.nl


Morpheus Kennistechnologie BV
<URL: http://www.mssm.nl >
postbus 69
3500 CD Utrecht
KVK 30 26 04 30

[Stig Lau]

My preferences shouldn’t weigh much since I’m not an active developer. However:

* personally I have a preference for Github due to the functionality (code analysis, work done, simple issue tracker, wiki) and active community. Downside being GIT.

* "Sourceforge is where open source projects go to die” But don’t let that cloud your judgement :)

* BitBucket has an ok toolchain, supports mercurial and git, but is costly for open source projects

This discussions among coworkers and github vs bitbucket hints towards github for a free open-source hosting. It should be fairly easy to test out exporting a simple project from google code to both bitbucket and github with Google Code Exporter, and see what fits and whats missing. 

When exporting to github/bitbucket, the commit history and everything should follow. However, I’m not sure if the issues and wiki will follow.

I will be testing the export-functionality with a couple other smaller projects of mine in a while.

 -Stig,

--
You received this message because you are subscribed to the Google Groups "ontopia" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ontopia+u...@googlegroups.com.
To post to this group, send email to ont...@googlegroups.com.
Visit this group at http://groups.google.com/group/ontopia.
For more options, visit https://groups.google.com/d/optout.

[Dan Speck]

Quintin,

I think Git Hub is the logical place these days.

-dan

[marijane white]

There's GitLab, too.
https://about.gitlab.com/gitlab-com/

[Motomu Naito]

Dear Siebers-san,

I found the following site.

Comparison of source code software hosting facilities:

http://en.wikipedia.org/wiki/Comparison_of_source_code_software_hosting_facilities

I am not a developer so I can't judge which one is suitable for Ontopia project.But as a big user of Ontopia, I prefer the site that is easy to use for users.

By the way, concerning this matter, do we have to get the permission from Bouvet?

Best regards,

Motomu Naito

[Quintin Siebers]

Dear Naito san,

I found the following site.

Comparison of source code software hosting facilities:

http://en.wikipedia.org/wiki/Comparison_of_source_code_software_hosting_facilities

Very helpful, thanks!

I am not a developer so I can't judge which one is suitable for Ontopia project.But as a big user of Ontopia, I prefer the site that is easy to use for users.

For end-users of Ontopia, we still have the ontopia.net website. It has been moved to one of the Morpheus servers so we can better maintain it. I have plans to upgrade the site for coming releases, as we might need a new download location and the site is way behind on current events.

By the way, concerning this matter, do we have to get the permission from Bouvet?

No. 

With regards,

Quintin Siebers

--

q.si...@mssm.nl

(+31) (0)6 - 11 06 16 27

Morpheus Kennistechnologie BV

<URL: http://www.mssm.nl >
postbus 69
3500 CD Utrecht
KVK 30 26 04 30

[Quintin Siebers]

Dear Ontopia users, developers,

It’s been a few weeks since our last discussion about a new code location for Ontopia. Although there was not much communication on the mailing list, I have not been sitting still. 

I’ve come across a major issue that will determine our options: There are consistency errors in our Subversion repository. Around the time that we made the massive changes to implement the maven modularization several commits try to add/modify/remove files that are not yet or no longer present. I have no clue how we managed to commit those changes, but they are preventing us from doing a full automated sync. I’ve tried to manually fix some of these, but eventually get stuck with mismatching checksums. 

This means that migrating to another location that uses Subversion as source control might be impossible. 

Which brings us to the next issue: The automated migration-to-github tool that google code provides. This tool can migrate issues, wikis and code to a new github project if the project is not to big. Ofcourse, Ontopia is to big and the tool fails on the code migration. Issues succeed, and wikis are never done because of the failing code import. 

But there is also good news: I’ve successfully migrated the Ontopia code to a local git repository and managed to push this to the github server: https://github.com/ontopia/migrate-test . I’ve merged this repository with the issues that were imported already. The only thing missing is the wikis.

Personally I think Github is the way to go, all of the features we now use are present and many more available. Also, Github allows us to host the release files and keep track of download statistics, all without a real limit:

We don't limit the total size of your binary release files, nor the bandwidth used to deliver them. However, each individual file must be under 1GB in size.

Please let us know if you have objections, comments or suggestions for a better location before the end of April, as I indent to put the final decision up for voting by the developers in May.

With regards, 

Quintin Siebers

--

q.si...@mssm.nl

(+31) (0)6 - 11 06 16 27

Morpheus Kennistechnologie BV

<URL: http://www.mssm.nl >
postbus 69
3500 CD Utrecht
KVK 30 26 04 30

[Motomu Naito]

Dear Siebers-san,

I understand the situation.

Thank you very much for your efforts.

I look forward to hearing good news from you.

Best regards,

Motomu Naito