Issue 994 in gbif-providertoolkit: Migration to GitHub

[gbif-provi...@googlecode.com]

Status: New
Owner: ----

New issue 994 by tigre...@gmail.com: Migration to GitHub
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=994

Hi all. I am currently working at the development of the Brazillian GBIF
node.

We have been under a mentoring process with Colombia, and within our
debates we have come to agree that IPT is a tool particularly likely tobe
customized for many different institutions in a single country.

For that reason, and believing to have a best developing and versioning
environment under GigHub, I'd like to propose a migration of the IPT code
to GitHub so that we may start forking it from the current version and
customize it in different ways more easily.

Cheers,

Pedro Guimarães



--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[gbif-provi...@googlecode.com]

Updates:
Status: Accepted
Owner: kyle.br...@gmail.com
Cc: daniel.amariles88
Labels: Type-Other

Comment #1 on issue 994 by kyle.br...@gmail.com: Migration to GitHub
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=994

Dear Pedro, thank you for your issue.

Moving to GitHub is something under consideration at the moment. We just
want to understand all the advantages that would make it worth the effort
of migrating not only the code, but issues and documentation also.

When you say customizing it in different ways more easily, are you talking
style only, or additional features?

As of 2.0.5, it has been made increasingly easy to customize the style of
the IPT as explained in this guide:
https://code.google.com/p/gbif-providertoolkit/wiki/IPT2Customization

Talking about new features, anyone is welcome to submit a code patch for
SVN, albeit the process is a bit more laborious than GitHub. I don't
suspect, however, that anyone would permanently fork the current version,
never to merge back the bug fixes and new features that happen with each
new release.

I look forward to hearing more from you on this subject. Kyle

[gbif-provi...@googlecode.com]

Comment #2 on issue 994 by tigre...@gmail.com: Migration to GitHub
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=994

Hi, Kyle. Indeed, in case of migration, it would be excelent to migrate the
issues and all documents as well. I'm afraid there is no straightforward
solution about that, as Git connects commits with issues in a different
manner from Google Code, I believe.

Anyways, about the customization, here in Brazil, for instance, being the
GBIF node is only a part of the entire Brazillian System for Biodiversity.
We have a lot more information from research institutions other than
occurrence records and taxonomy lists. We are considering perhaps adapting
IPT and HIT in order to support these other information.

Besides, maybe consider changing all the DBMS in the GBIF (HIT+IPT+Portal)
environment to a NoSQL database. I believe it is likely the next version of
the GBIF portal has already something like this going on, but as far as the
moment, we can't confirm that.

[gbif-provi...@googlecode.com]

Comment #3 on issue 994 by kyle.br...@gmail.com: Migration to GitHub
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=994

Dear Pedro,

Thanks for your further explanation.

Indeed, GBIF is moving to some NoSQL technologies for its new portal. You
can read about the new infrastructure here:
http://blog.cloudera.com/blog/2011/06/biodiversity-indexing-migration-from-mysql-to-hadoop/

In the meantime, we are at your service should you need to adapt these
existing tools as Colombia has. The HIT and Portal are no longer in
development, but the IPT remains in active development . I would kindly
advise you to plan any adaptation of this tool very careful, to continue to
take advantage of future bug fixes and enhancements. Cheers

[gbif-provi...@googlecode.com]

Comment #4 on issue 994 by daniel.amariles88: Migration to GitHub
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=994

Hi, just to say that I'm agree with Pedro's proposal to move it ti GitHub

Here it is some reason why it woulbe better if the code is in GitHub:

1. It would be easier for us and any node to make fork to the project.

Currently we are using another google code project, but it is an effort to
move GBIF code to our repository when there is a new version release,
beside the revision history is lost when it is moved. With GitHub it is
just one click to fork and we can keep history of revisions.

That also means that if finally the code is moved, the history in
subversion should be moved too. That was what we did with data portal.


2. Suggest patches from other parties is easier

For example changes that we have made attaching files to issues or sending
emails, now with GitHub we can shared them with just one click in "pull
request"


I really think that with GitHub it would be even more easier to make this
collaborative work with IPT that all have made for years.


Actually i think Canadensys has a copy if IPT in GitHub, so they also may
be agree with this.

[gbif-provi...@googlecode.com]

Comment #5 on issue 994 by kyle.br...@gmail.com: Migration to GitHub
http://code.google.com/p/gbif-providertoolkit/issues/detail?id=994

Thanks Daniel for your additional comments.

I have heard from Canadensys on this subject also, and I know that they are
also strong advocates of moving the IPT to GitHub.

In the last couple years, the majority of collaborative development has
been around translation of the interface and wiki. We do receive code
patches, but there isn't a constant stream of them. For now, asking
contributors to submit patches for review works fine.

Another reason not to switch right now, is that we don't want to lose all
the project history.

To close, we're still open to the idea, but we just don't have resources to
make this switch for some months still until after the new portal is out.
Thanks guys

[gbif-provi...@googlecode.com]

Comment #6 on issue 994 by s.cozijn...@gmail.com: Migration to GitHub
https://code.google.com/p/gbif-providertoolkit/issues/detail?id=994

The announcement of Google to close Google code puts this Issue on the
radar again.
http://google-opensource.blogspot.nl/2015/03/farewell-to-google-code.html

Google build a tool to migrate your project to GitHub:
https://code.google.com/export-to-github/

Maybe that can be of some help?

[gbif-provi...@googlecode.com]

Comment #7 on issue 994 by kyle.br...@gmail.com: Migration to GitHub
https://code.google.com/p/gbif-providertoolkit/issues/detail?id=994

Thanks Sijmen,

I estimate we'll have a window of opportunity to do the migration in
May/June. We'll surely be making use of the migration tool to make life
easy on ourselves.

[gbif-provi...@googlecode.com]

Updates:
Status: Started

Comment #8 on issue 994 by kyle.br...@gmail.com: Migration to GitHub
https://code.google.com/p/gbif-providertoolkit/issues/detail?id=994

The IPT source code and issue tracking is now managed in GitHub? and
available at the following address: https://github.com/gbif/ipt

The IPT User Manual and Wiki is still in the process of being migrated.