# openEHR Subversion => Github move progress **Category:** [Technical (archive)](https://discourse.openehr.org/c/technical-archive/156) **Created:** 2013-03-21 23:13 UTC **Views:** 9 **Replies:** 7 **URL:** https://discourse.openehr.org/t/openehr-subversion-github-move-progress/15231 --- ## Post #1 by @thomas.beale The last of what I think are the active Subversion repositories on the old openEHR.org server has been converted to GitHub now (the Archetype Editor). Repositories which appear to be inactive but could be converted if anyone wants: - liu_knowledge_tools (Linkoping has a more recent version of this AFAIK) - the original 'knowledge' repository containing a lot of old NHS archetypes - knowledge_tools_java - not sure about this one. - ref_impl_python For those who have links, checkouts or other pointers to any openEHR SVN repositories, please now refer to the [Github openEHR repositories](https://github.com/openEHR). Any questions like 'where did xxx go?', feel free to post them here. - thomas beale --- ## Post #2 by @system Hi! Apache as something called "The Apache Attic" for unmaintained old projects in order to keep the code/assets somewhere, see [http://attic.apache.org/](http://attic.apache.org/) Perhaps we could simply have an openEHR attic project at github where each unmaintained previous project gets a sub-directory-tree. Would creating an "attic" be an OK plan? I am cross-posting this suggestion to the openehr-implementers mailing list where we can continue the discussion and qualified members could cast a formal vote as described on... [http://www.openehr.org/programs/software/governance](http://www.openehr.org/programs/software/governance) ...and... [http://www.apache.org/foundation/voting.html](http://www.apache.org/foundation/voting.html) If no major objections or counter-proposals are seen within a week from now I'll assume lazy consensus and create an "Attic" project. I think an attic is where things like the "liu_knowledge_tools" could go for example. Future web-policies at universities and other places are not always guaranteed to maintain old URLs and content. Best regards, Erik Sundvall [erik.sundvall@liu.se](mailto:erik.sundvall@liu.se) [http://www.imt.liu.se/~erisu/](http://www.imt.liu.se/~erisu/) Tel: +46-13-286733 --- ## Post #3 by @thomas.beale Erik, will the LiU tools project never be touched again? After all the code isn't exactly last century\.\.\. maybe it should just have a real project\. \- thomas --- ## Post #4 by @system Hi\! Tom wrote: > will the LiU tools project never be touched again? Apache has a "Process of leaving the Attic again" see http://attic.apache.org/ I assume we could have something similar for openEHR\. > After all the code isn't > exactly last century\.\.\. maybe it should just have a real project\. Regarding the archetype editor, it contains many workarounds to deal with the then immutable openEHR Java reference implementation of the AOM\. We tried to argue for changing it to mutable at the time, but without sucess then\. Nowadays the Java AOM is mutable and that should be considered in any new development, also the LinkEHR project has interesting pieces that any new java editor should consider\. The more recently maintained LinkEHR editor probably fits many of the use\-cases that once motivated the LiU Archetype Editor\. That said, I think a web based collaborative editor \(using javascript etc\) would be more interesting to do rather than picking up the old LiU Archetype Editor code if there would be any new development efforts\. HTML5 also provides good support for offline mode operation\. The LiU archetype editor also contains javacode for TermViz \(disabled by default\), but if anybody is interested in such functions I would suggest looking at and extending the more recent https://github.com/ErikSundvall/TermViz instead\. So, I'd suggest we currently put the LiU Archetype editor in the "attic" and if anybody ever wants to revive it they can fork it, update it and then suggest opening a new active project once they have something interesting running and a small community of comitting developers\. Best regards, Erik Sundvall erik\.sundvall@liu\.se http://www.imt.liu.se/~erisu/ Tel: \+46\-13\-286733 --- ## Post #5 by @thomas.beale it seems that in practical terms, the 'attic' is . This is prbably the condition that matters: So would our attic be something like following the rest of the items on the above list, plus create a physical storage location? If the project was already on openEHR@Github then maybe we move it to openEHR-attic@Github? For others which are/were in SVN, what do we do? Maybe the easiest thing is to put the zipped SVN backups on the server, with a page pointing to those archives? one of the problems with LinkEHR (which does have many good features) is that it is driven off XSD. In principle, XSD is already a deformation of any but the most trivial object model, due to its non-OO semantics. As time goes on, it is clear that the XSD expression of data models like openEHR, 13606 etc will be more and more heavily optimised for XML data. This guarantees such XSDs will be a further deformation of the original object model - the view that programmers use. So now if you build archetypes based on the XSD, you are not defining models of object data that software can use (apart from the low layer that deals with XML data conversion). I am unclear how any tool based on XSD can be used for modelling object data (and that's nearly all domain data in the world today, due to the use of object-oriented programming languages). I'm going off the point here a bit ;-) so - what's your preferred practical version of the attic? SVN archives like above - thomas --- ## Post #6 by @system Hey guys, now that openEHR is on github, have you realised that WE'RE ALL REALLY WRITING HISTORY? See, e.g. [http://starlogs.net/#openEHR/gdl-tools](http://starlogs.net/#openEHR/gdl-tools) Now that's gonna baffle them at Medinfo! Cheers, --- ## Post #7 by @system Coool!! /Rong Rong Chen, MD, PhD CMIO, Director of Health Informatics +46 8 691 49 81 cid:image001.png@01CE14CE.DC7B4E10 **Cambio+** **Healthcare Systems AB** Stockholm: Ringvägen 100. SE-118 60 Stockholm Vx: +46 8 691 49 00 | Fax: +46 8 691 49 99 Linköping: Brigadgatan 14. SE-587 58 Linköping Vx: +46 13 20 03 00 | Fax: +46 13 20 03 99 Epost: [info@cambio.se](mailto:info@cambio.se) | Hemsida:www.cambio.se --- ## Post #8 by @Koray_Atalag Hey that’s really awesome! Cheers, -koray --- **Canonical:** https://discourse.openehr.org/t/openehr-subversion-github-move-progress/15231 **Original content:** https://discourse.openehr.org/t/openehr-subversion-github-move-progress/15231