Do you really need a separate CKM instance to be able to share archetypes, though?
In the Norwegian CKM, we’ve been quite liberal in handing out (public or private) incubators w/ editor rights to anyone (in Norway; non-profit or commercial) who wants one. We had an initial lapse where we handed out projects, but luckily we were able to rein that in before it became impossible to manage. (To those of you who may not know the difference between CKM projects and incubators, archetypes in projects are counted as part of that CKM’s “canon” and can be reviewed and published, while incubators are basically sandboxes for collaborating and sharing archetypes and templates.)
This approach is working relatively well, with the main criticism being that uploading archetypes to the CKM is more cumbersome than syncing them to GitHub. I’m sure this can be worked on in the future, though. J
Also, as others have pointed out before, the CKM has much more very specialised functionality than just versioning and sharing. We would not have been able to do what we’re doing with the national governance here in Norway were it not for the review functionality of the CKM.
Kind regards,
Silje Ljosland Bakke
Special Adviser, RN
R&D dept, E-health section, Bergen Hospital Trust
Coordinator, National Editorial Board for Archetypes, National ICT Norway
Tel. +47 40203298
Web: http://arketyper.no / Twitter: @arketyper_no