Dear Mukul,

Thank you also from me for your interest in the IPT, and your offer to contribute.

The IPT has recently undergone a huge refactoring effort recently, with the latest IPT 2.0 in the trunk/gbif-ipt directory. It is this codebase that we are all working towards.

We have just announced 2.0RC3 and are shortly going to release version 2.0GA, but following this there is likely to be some exciting new developments on the IPT during 2011. I think it could be a great time to be involved; The IPT development team is widespread (Colombia, US, Denmark, Germany and I am in Kiribati currently and there are active testers in Sweden, France, Argentina, Italy, Australia, Korea, Taiwan, Madagascar, India etc etc) - we anticipate worldwide installations.

Like Markus says, and similar to the way Apache runs open source projects, the best way to get into the project would be to indicate that you are working on an issue, and then submit a patch (eclipse right click, create patch) which will be verified by a developer before being applied to the truck. I would suggest doing a couple of very small ones, before tackling something more sizable - there are things like setting eclipse to use the correct coding conventions (http://rs.gbif.org ) that need to be respected, and with appropriate JUnit coverage where applicable before code will be accepted. After a few contributions, you would then become a committer. There are some issues in there to build some good unit test coverages - this could be a good place to learn the code, which will make a great addition to the continued stability of the software, especially as the development team expands.

Best wishes and thank you for your interest Tim

On Jan 9, 2011, at 6:33 AM, Markus Döring (GBIF) wrote:

Dear Mukul, as the IPT is an open source project we always welcome contributions. Before you dive into the codebase though be aware that we use struts2, google guice instead of spring and only a very slim persistency layer around XStream using xml files.

Issues targeted at the next 2.0.1 release might be candidates to work on: http://code.google.com/p/gbif-providertoolkit/issues/list?q=milestone=Releas...

If you are interested in working on any of these issues please drop us a line. As a start please send us patches before we will make you a committer.

Developer documentation is on its way, but as a start we have this FAQ and some more wiki pages: http://code.google.com/p/gbif-providertoolkit/wiki/DeveloperFAQ

Thanks for getting in touch,

Markus

-- Markus Döring Senior Developer ECAT GBIF Secretariat mdoering@gbif.org

On Jan 8, 2011, at 15:59, ipt-owner@lists.gbif.org wrote:

...

As list administrator, your authorization is requested for the following mailing list posting:

List: IPT@lists.gbif.org From: mukul.kapur@gmail.com Subject: Fwd: Enquiry for volunteer contribution to gbif project Reason: Post by non-member to a members-only list

At your convenience, visit:

http://lists.gbif.org/mailman/admindb/ipt

to approve or deny the request.

From: Mukul Kapur mukul.kapur@gmail.com Date: January 8, 2011 15:59:45 GMT+01:00 To: ipt@lists.gbif.org Subject: Fwd: Enquiry for volunteer contribution to gbif project

Hi

I am a junior software developer from New Delhi India.

I was looking for some hands on experience on Struts/Spring/ Hibernate framework .

I wished to enquire whether the gbif project is currently looking for any volunteer developers..

Looking forward to hearing from you..

Thanks and Regards

Mukul

From: ipt-request@lists.gbif.org Subject: confirm cd6bce1f1071cc4a876301519cc087bd7e7a791a

If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply.