P.s. Software interested tech-list subscribers, make sure you are also
subscribed to...
openehr-implementers@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
...since that is where the "software program" of openEHR is going to
host discussion according to board decisions.
yep, it’s me, I forgot to set anything up. For the moment I am sole member and admin. We might need a little bit of planning about how to use the openEHR space I think - I am just thinking of how to make sure we have a fairly comprehensible (to outsiders) Github presence, while of course allowing open use.
Once the software group gets a plan together, let me know and I will add some other admins etc.
Excellent. I was just thinking yesterday that as well as regularly
outputting CKM to a Git repository, we also ought to bring together
other legacy material e.g the NHS and any other artefacts people want
to share e.g some of the vendor-developed archetypes that I have been
working on but which are very suitable for wider use.
We will need to clearly differentiate repositories which are inert,
from those which are active but uncontrolled, and those which are
tightly governed - the latter will not really exist until we have
proper namespacing established.
As far as the openEHR CKM repository is concerned, given current
development schedules, an automated update to Github is unlikely to
appear any time soon but I will commit to doing so manually on a
regular basis or when any significant changes occur e.g new uploads or
publications.
GitHub is very good site to incubate source codes.
Anyone can fork source codes, commit and merge them.
As Ian mentioned, I have thought GitHub could be a incubation
repository for archetypes, which were premature than CKM repository.
However, license issue must be fixed to do, at first. Apache 2.0 license
is very good.