Martin van den Bemt wrote: >Hi everyone, > >When answering a question from Tony Austin, I ended up at this link : >http://www.openehr.org/repositories/spec-dev/latest/publishing/CM/CM_plan/REV_HIST.html >(pick the latest version) > >The question I have is about Chapter 7 & 8 (from now on called >document). > >Is the description of the documennt what will be used for every >subproject of openEhr (with subproject in this case I mean project where >actually programming takes place) and is this considered a manual for >people who want to start programming openEHR like stuff under the >umbrella of openehr.org ? > > not necessarily. This CM plan was originally written mainly for the specification project, and will be adapted for more programming-oriented projects. But implementation projects won't have a very different plan - this plan I wrote based on plans used at a number of companies I have worked at, including banks, British Telecom, and large engineering companies in Australia.
>What is the goal of the openehr project ? Does it want to something like >how Apache works (see >http://www.apache.org/foundation/how-it-works.html) >or does the openehr project want a different direction ? > > this page is more or less Apache Software Foundation's change process definition. >If it is meant as the apache way and(which is what I read between the >lines) and the chapters are the "official way", you should probably >change chapter 7 & 8 to be the text of the how it works html file (with >some changes of course). Or point to a simple (html) file from the web >site describing the process within openehr.org and refer from there for >the people interested in reading the chapters 7 & 8. > > this plan is under modification right now actually, and some details will change. We will also publish a simple, clear set of web pages so that people can understand what the process is. The ASF page seems like a good model. >Describing how something should work (related to a community, in this >case an open source community), must, in my view be kept simple. >If you skim through the document (what I did in the first place, since >there was a lot of text), people like me (= who likes to program and >never RTFM, unless really necessary) get scared and draw wrong >conclusions. > >Too much formality is scary (at least for people like me) :) > >Hope no one (esp. Thomas) feels offended, since it is not meant that >way. (I admire the way you guys can write specs, if people ask me where >my specs are "Read the code" will be my answer). > > ah, well, you will discover there are limitations to that approach in the long run (as I am sure you are aware;-) The openEHR community may well get quite large, and we do need to write good quality documents. But we are also dedicated to making things simple and understandable as well - this doesn't mean throwing out our base documents, it means writing short & shart summaries on the website. We need people in the community to tell us what to write (and offer to write things themselves if so motivated), so this is good feedback. - thomas - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
