oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi Gurpreet,

It's great to have you on the project.

We are beginning to gain some real momentum and are happy to have you be
part of it.

We are pressing for a 1.0 beta release soon but have some housekeeping
things in code review to do since there has been a new version of the
specs released since the original openEHR Reference Model portion was
written.  Plus some parts of it was never really complete.

So, since you seem eager; I'll dump you right into it with a little bit
of discussion first.

The core part of OSHIP is based on a solid, proven model that has
already been implemented in other languages.  

The step by step process for participating in OSHIP development is:

1. Install a branch of the trunk according to the FAQ for your OS:
   https://answers.launchpad.net/oship/+faqs 

2.  Create a workspace with yourself as the owner according to the FAQ:
    https://answers.launchpad.net/oship/+faq/392

3.  You will have likely been asked to work on a particular Blueprint:
    In your case GurPreet I am asking you to work on the code review
for datastructures
https://blueprints.launchpad.net/oship/+spec/codereview-datastructures
 
4.  On the Blueprint page you will see a link near the top left side
that says Read the full specification.  This link will take you to the
openEHR specification for that module.

5.  There have been one or more updates to the specs since some of this
code was written and in some cases the code was not completed anyway. 

6. Using the specification document as a guide; go through the code and
create a Launchpad Bug Report for each error you find.  As an example
you can see where I have started this with the datatypes module (except
I am doing it directly on the trunk which I will correct and create a
branch). 

7.  Then you can go back and begin to fix the bugs.  Using this 2 step
process; we get the reviews done sooner and if something happens or
there is a bug you need help with it is easier for someone else to
assist/replace you.

I know that sometimes people are shy about showing their lack of
knowledge about things.  ESPECIALLY in this case no one should be.  We
are working with a group of FOUR very complex components here:

a) distributed development is difficult by it's very nature
b) healthcare is a complex domain
c) openEHR concepts are unusual (but very effective and proven)
d) the Zope/Grok component stack is a living, growing group of Python
components

But PLEASE, PLEASE ask your questions on the mailing list.  By doing
this **everyone** gains and grows at the same time.

By each of you concentrating on one part of OSHIP it will free me up to
especially; write some good docs to help you and the application
developers, select the best components for us to use to accomplish our
goals and to hopefully teach you all something about the power of the
openEHR approach to health application development and interoperability.

GurPreet, thank you for giving me a reason to write this email to the
list.  I will turn most of it into an FAQ as well as try to clean some
of the existing ones.

Cheers,
Tim



On Mon, 2009-08-24 at 13:23 +0000, Gurpreet Singh wrote: 
> Hi Tim,
> 
> I am a budding python developer. As of now my tasks have been to
> automate testing in various projects using python scripting language.
> I am also well versed in implementation of Groovy scripts in SOAPUI for
> web service testing.
> 
> I want to be a part of the dev team and contribute/assist the on going
> development activities of this Open Project.
> 
> Please let me know if there is something that I can start with. I am
> really interested in FOSS and looking forward to contribute.
> 
> Also ready to take up tasks related to any new scripting language as the
> main motive here is the interest in contributing to the project by any
> means.
> 
> Thanks
> Gurpreet Singh
-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
***************************************************************
*You may get my Public GPG key from  popular keyservers or    *
*from this link http://timothywayne.cook.googlepages.com/home *
***************************************************************

Attachment: signature.asc
Description: This is a digitally signed message part