oship-dev team mailing list archive
-
oship-dev team
-
Mailing list archive
-
Message #01127
Re: Some thoughts about the future development of the OSHIP
Hi Diego,
Sounds like a nice solid plan to me. Keep up the good work.
Do you know when you will have the new pkg. structure committed?
If you do not use an IDE with Search and Replace across files. WingIDE
does that. So, if you need me to I can fix all of the import statements
pretty quickly.
Regards,
Tim
On Wed, 2010-07-07 at 15:55 -0300, Diego Manhães Pinheiro wrote:
> 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
> _______________________________________________
> Mailing list: https://launchpad.net/~oship-dev
> Post to : oship-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~oship-dev
> More help : https://help.launchpad.net/ListHelp
--
***************************************************************
Timothy Cook, MSc
Project Lead - Multi-Level Healthcare Information Modeling
http://www.mlhim.org
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
Skype ID == timothy.cook
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
Follow ups
References