oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi All,

Well, while has not seemed to be too much happening on the mailing list
nor on the Launchpad site.  There really is a lot going on, onboard the
OSHIP.

First of all we had a great time at Python Brasil [5].  Meet some great
new people, some people we already knew, and even some people we knew
that we didn't know we knew.  Yep, we have some lurkers on the project
that were at the conference and they are very interested but just very
busy at the moment.  

While we were at the conference we spread the rumor, we say rumor
because we haven't seen an official announcement from the Ministry of
Health, but we do have sources inside the Ministry of Health that have
confirmed that the decision has been made to use the openEHR
specifications as the national healthcare data standards for Brasil.
This is very exciting for the OSHIP community and the openEHR community
at large.

We can confirm that there will be a 5 day course during the Summer
program on OSHIP/openEHR/EpiS3 at the National Laboratory for Scientific
Computing (LNCC) in January.  See:
http://www.lncc.br/ingles/eventoSeminario/cursos.php?idt_tipo_atividade=12&idt_evento=723&descAtiv=Mini%20Courses#1852 for details.

Among those we met at Python Brasil were a number talented web designers
and graphic artists.  They have volunteered to put together a website
for us that will be more inviting than the front page of Launchpad.
This should help attract new comers.  Then we can point to the specific
areas of Launchpad from there.  We already own OSHIP.org and believe
that we have a nice high speed hosting place for it.  This will
hopefully start to materialize early next month.

Work has been slower than hoped for during these alpha phases and code
reviews have kind of lagged.  But one of the major things that has held
us back from moving to a beta 1 phase is the fact that Grok was still
alpha.  Grok is now at beta2 coming out of their week long sprint and
there are a number of changes.

My initial thoughts are that I will be taking all code branches that are
part of the core OSHIP and merging them into the trunk if they do not
break the server.  This does not include branches like erickmartins
project or EpiS3 that are projects on top of OSHIP.  

I will then refocus existing bugs onto the beta1 blueprint. Closeout all
of the alpha blueprints as obsolete.  Upgrade OSHIP to Grok beta2.

This will put us at a feature freeze on the 1.0 branch and we will only
be filing bug reports.  A major focus will then be to create as many
Python based archetypes as possible so that we can see just how good/bad
the AM/RM really are.  This includes the building some of the test
archetypes with known failure points in them.  

I expect to have this transition completed NLT Saturday evening BST (UTC
-0300) 26 September.  If anyone thinks that this is too radical then
please speak up.  I believe it will put us in an easier to manage
situation where we are simply filing bug reports (though likely lots of
them) against one version (beta1) in one branch.  It should be less
confusing for everyone.

I know there was lots more to say but it has slipped my mind for
now. :-)


--Tim

PS.  The Amazon Basin was wonderfully relaxing........  


-- 
***************************************************************
Timothy Cook, MSc

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == (upon request)
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

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