There will be a f2f of the Specifications Editorial Committee 
<http://www.openehr.org/programs/specification/editorialcommittee>(SEC) 
in Netherlands, 21/22 May. At this meeting, the SEC will try to process 
the existing Problem Reports 
<https://openehr.atlassian.net/issues/?jql=project%20%3D%20SPECPR%20ORDER%20BY%20created%20DESC>(PRs)
 
and convert them to Change Requests (CRs) on the various Specifications 
Trackers 
<https://openehr.atlassian.net/secure/Dashboard.jspa?selectPageId=10190>. The 
result will be a roadmap of specifications changes, expressed as CRs on 
those CR trackers, for approximately the next 2 years.

Of course this will not be fixed - anyone can raise a PR at any time, 
and in the steady state, the SEC will process it quickly thereafter. The 
current exercise is to get up to speed on the backed-up PRs and issues.


      What can I do?

The PR tracker 
<https://openehr.atlassian.net/issues/?jql=project%20%3D%20SPECPR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC>currently
 
contains 109 unresolved issues that many of you have reported over the 
last few months / years. There are another 19 older Change Requests for 
the Reference Model 
<https://openehr.atlassian.net/issues/?jql=project%20%3D%20SPECRM%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created%20DESC%2C%20priority%20DESC>.

The SEC's job is just to manage the problem reports, issues and 
determine appropriate changes to the specifications that address them. 
The issues come from everyone in the community.

What everyone can do is to look through those 109 PRs and 19 CRs

  * if there are any comments you want to make or any new PRs you want
    to raise.
  * If you were the original raiser of the PR, you can edit the main
    text to add detail etc.

All comments will be read by the SEC, and incorporated into the roadmap 
(i.e. the CRs that result from the analysis we are doing).

please report any problems with access, logging in etc to 
admin at openehr.org <mailto:admin at openehr.org>

- thomas beale

(Specifications Program)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150422/ca8a39f4/attachment.html>

Reply via email to