Agree with both. Probably we should go review the mailing lists to identify which kind of questions are usually asked by newcomers.
Also, we should use stackoverflow more, with dedicated tags to openEHR. 2015-05-25 11:57 GMT+02:00 Thomas Beale <[email protected]>: > > We appear to be getting more and more newcomers to the openEHR website and > wiki - and on the wiki, they are faced with a somewhat chaotic place! I > think we should slowly start to clean it up. > > First suggestion: There are two spaces for developers - 'Developers', > which has a lot of pages, and needs some re-organisation, and > 'Implementation Guidance' which is small and not used much. > I propose to put the pages from the latter under the 'Developers' space > and remove the latter space. > > Second suggestion: I think we need a 'getting started' page for each > manor development technology - Java, Python, C# etc. There are bits and > pieces all over the place but nothing coherent. > > Would people like to see something like the following structure: > > - Developers space > - Getting started > - Java > - C# > - Python > - Ruby > - .... > > thoughts? > > - thomas > -- > [image: Ocean Informatics] <http://www.oceaninformatics.com> > *Thomas Beale Chief Technology Officer* > +44 7792 403 613 Specification Program, *open*EHR > <http://www.openehr.org/> > Honorary Research Fellow, UCL <http://www.chime.ucl.ac.uk/> > Chartered IT Professional Fellow, BCS <http://www.bcs.org.uk/> > Health IT blog <http://wolandscat.net/category/health-informatics/> [image: > View Thomas Beale's profile on LinkedIn] > <https://uk.linkedin.com/pub/thomas-beale/0/217/68a> > > _______________________________________________ > openEHR-technical mailing list > [email protected] > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
