Moving PSI-MI and PSICQUIC projects to GitHub?

[mar...@ebi.ac.uk]

Dear PSI-MI/PSICQUIC community,

As we have had more cooperative efforts in the past few years (PSICQUIC
hackathon, sharing code and libraries, etc..), I realise that our current
projects structure in google code/sourceforge is not very well adapted for
sharing code and development effort.

We have just created an organisation in GitHub called MiCommunity :
https://github.com/MICommunity. It has been originally created for sharing
the development of some molecular interaction tools (complex viewer, etc.)
between three different groups but I was thinking that it could be a good
thing to move our existing PSI-MI projects such as PSICQUIC, psi-mi format
specifications, ontologies and java/perl libraries to Github under the
same organisation.

The idea would be to freeze the existing SVN code in sourceforge and
google code (so previous links still work) and move everything to GitHub.
We would create several repositories for each project, all under the same
organisation to give them more visibility. The wiki and documentation
would also be copied from the previous repositories.

I created a doodle poll to know what the community thinks here :
http://doodle.com/whvnsus39wve74a6.

I will leave it open until then end of October so if you are a developer,
please fill out the doodle poll (and add your e-mail address somewhere so
we can contact you)!

Using Git over SVN has many advantages for big community projects and
sharing code. However, for people having used only centralised system such
as svn in the past, it may take some time to learn Git and I would
perfectly understand if the community prefers to stay with the current
system.

You can have a look here for more information about git :
http://git-scm.com/ and here for GitHub: https://github.com/.

Regards,

Marine

[Lukasz Salwinski]

This is not a problem of 'community' vs 'centralized' system but rather
a problem of 3rd party/community sites becoming unusable. Note that
sourceforge (hupo-psi-related mailing lists in particular) were (mostly ?)
abandoned due to spam; googlecode uploades folds due to service abuse.
Projects hosted by any 3rd party providers are at the whim of the 3rd
party and any potential abuser of entire service.
It's sort of surprising that a project that is quite well embedded
within organizations maintaining a rather robust and public Internet
infrastructure strives, over all these years, to use freebies. What's
good for gazillions of personal/community projects run by people
without access to stable, public server infrastructure is not
necessarily best for institutional projects. Setting up a site based
on trac (http://en.wikipedia.org/wiki) or any other project management
system is rather simple.

lukasz

[Bruno Aranda]

Not sure what you are comparing there...

- GitHub is not free for all. To hosts private repos you have to pay, and it is a actually a very profitable business for a company just focused on this.

- GitHub does not have mailing lists. Spam in emails is altogether a different problem, you pay or not.

- GitHub has more than 10 million projects on it

- Every project I have worked in the past years (since I left the EBI, actually) uses GitHub, sometimes the main public repository (at github.com), and sometimes private installations of the enterprise version of that if the code is commercially sensitive.

- We are not talking about project management, but source code versioning and repositories!

But obviously this means moving to Git, which I think the focus of all this should be fist. By the amount of commits and the size of the "community" I don't think it is much better than SVN and it has a learning curve if you don't know it. I would understand that there are more concerns on that area. Once you do get it, it is the best tool ever for source code management.

Other advantages about GitHub, for PSI for instance, is that you can have an Organisation and see all the projects at a glance, even if the permissions for each project are different. That is a nice thing.

Cheers,

Bruno

--
--
You received this message because you are subscribed to the Google
Groups PSICQUIC group.
To post to this group, send email to psic...@googlegroups.com
To unsubscribe from this group, send email to
psicquic+unsubscribe@googlegroups.com

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

[Lukasz Salwinski]

On 09/22/2014 07:31 AM, Bruno Aranda wrote:
> Not sure what you are comparing there...

Bruno,
personally I don't particularly care - cvs, svn, github, mercurial, ...
whatever. Another versioning system, another couple of days to get hang
of it. Not a big deal. But note that the move is to happen not because of
the technical superiority of the new solution but because the old one gets
discontinued. And thus dragging around not only repository contents but
also wiki pages and documentation - vide:

>The wiki and documentation would also be copied from the previous
>repositories.

Sourceforge mailing lists had to be replaced by new ones. But at least some
issue trackers stayed on sourceforge. In effect some of the psi-mi/psimex
stuff still sits on sourceforge, some lives in googlecode, some on the
imex consortium web site and now there's going to be yet another site to
visit on github. this is as disorganized as it gets :o/

lukasz

>> psicquic+u...@googlegroups.com

>>
>> http://psicquic.googlecode.com
>> --- You received this message because you are subscribed to the Google
>> Groups "psicquic" group.
>> To unsubscribe from this group and stop receiving emails from it, send an

>> email to psicquic+u...@googlegroups.com.

>> For more options, visit https://groups.google.com/d/optout.
>>
>

--
-------------------------------------------------------------------------
Lukasz Salwinski PHONE: 310-825-1402
UCLA-DOE Institute for Genomics & Proteomics FAX: 310-206-3914
UCLA, Los Angeles EMAIL: luk...@mbi.ucla.edu
-------------------------------------------------------------------------

[Samuel Kerrien]

Nicely summarised Bruno, totally agree !

Download could always be hosted on a Wiki provided it is clearly linked from Google Code (if you decide to stay there).

Cheers

Sam

psicquic+u...@googlegroups.com

 
http://psicquic.googlecode.com
---
You received this message because you are subscribed to the Google Groups "psicquic" group.

To unsubscribe from this group and stop receiving emails from it, send an email to psicquic+u...@googlegroups.com.

[Marine]

Dear PSI-MI/PSICQUIC community,

We now had plenty of time to collect feedback about moving the projects
to GitHub. From the doodle poll results, a big majority wants to move
the projects to GitHub and as nobody is against it, we will proceed with
migrating the projects from google code and sourceforge to GitHub.

As we had several requests already for PSICQUIC, I propose we start the
migration with PSICQUIC project.

The plan is to :

- freeze any development/wiki documentation in google code project
- migrate the source code to a new repository under GitHub/MICommunity
organisation
- migrate the code history as well
- update the pom files so the maven release plugin can use git instead
of svn
- migrate/update the wiki
- choose how to provide the libraries/packages in GitHub
- update the google code wiki to alert users of the repository change
- update the PSI website so the links point to the new repository and wiki

I propose we keep the PSICQUIC google mailing list active and all the
active mailing lists should be listed in the PSI website.

If you want to help with the migration, please contact me as soon as
possible so we can split the tasks.

Regards,

Marine

[Bruno Aranda]

Good morning!

It seems that Google has accepted defeat and it will close Google code soon. Where are we with this?

There is an exporter tool to GitHub provided by them that we can use.

Cheers,

Bruno