oship-dev team mailing list archive

[Diego Manhães Pinheiro <dmpinheiro@xxxxxxxxx>]

HI all!

I'd like to do some considerations about the next steps of the OSHIP:

The package directory structure I'll change to a more closed way to the
openEHR specifications. After that, the team focus target will be a 1.5
version of the OSHIP. This version will contains all the features and bugs
related to the core of reference model solved(support, datatypes and
datastructures).
The package structure will change a to a more simple way:

All modules from the reference model, will change to the rm module of the
OSHIP directory. For instance: The actual *oship.openehr.datatypes* will
turn on *oship.rm.datatypes*. The module will have all submodules defined by
the openEHR specifications, so all modules will follow the openEHR module
structure recomendations as close as possible .

At the moment, let stay focused only in the *SUPPORT* module. It's the most
low-level module of the OSHIP. When all issues was finished in the support
module, we can go to the datatypes modules and so on until all modules are
OK. When we fix the core modules(*support, datatypes, datastructures*),
we'll release a new version of the OSHIP. This version'll be packaged and
available using the setuptools system, generating a egg file[1] and
available at the PyPI[2] system.

A remind: all blueprints related to the datatypes, support and datastructure
modules have to be related to the 1.5 milestone on the launchpad. From now,
I'll checkout all bug and blueprint entries to make this true. Everbody is
free to assign yourself to a blueprint or a bug report via launchpad
system and solve it.

[1] - http://peak.telecommunity.com/DevCenter/EggFormats
[2] - http://pypi.python.org/pypi


-- 
http://dmpinheiro.net
-----------------------------------
Diego Manhães Pinheiro