Eye Care Change Proposal (CP)
Revision as of 13:00, 10 August 2009 by Ksilva (talk | contribs) (New page: = Introduction = The EYECARE CP process follows the general IHE CP process described on the Change Proposal process page. The following sections give more detail on ...)
Introduction
The EYECARE CP process follows the general IHE CP process described on the Change Proposal process page. The following sections give more detail on the general process for EYECARE participants involved in the CP process.
The EYECARE specific CP Process
The following text explains what the process used by the EYECARE commitee in processing submitted CPs. It is consistent with the general IHE CP process and is informative only.
- Submission into the Incomingin directory. This is typically done via an email to the EYECARE Technical Committee co-chair or staff directory if you have access to the ftp write password.
- First consideration by the committee. If CP is accepted it is given a CP #, assigned an editor, renamed to CP-ITI-xxx-00.doc and placed in Assigned. If CP is rejected it is moved to Rejected and submitter is informed of explanation for rejection. Likely reasons for rejection are: duplicate, merged, withdrawn or not enough information to understand the request. Rejected CPs can be resubmitted with more information for reconsideration.
- Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
- Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
- Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
- Ballot is released to the general community for voting
- Votes and comments are collected. All yes votes means the CP passed ballot and moved to FinalText. No votes are resolved by the committee. Sometimes CP is withdrawn, sometimes NO voter changes to yes vote after explanations. CP may be updated in this process. If updates are insignificant (clarification only) the CP is considered passed. If updates are significant the CP is submitted for another ballot.
- CP approved in ballot are put in FinalText and scheduled to be integrated into the Technical Framework or Supplement.
Directory Structure
As CPs are processed through various statuses they move from one directory to another. The directories invoved are:
- Assigned
- contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned status
- Ballots
- contains Ballots that have been released for voting by the general community
- Canceled
- contains CPs that have been canceled, i.e. Canceled status
- Completed
- contains the last version of a CP that is in Completed status. It is waiting to be put in a ballot
- FinalText
- contains the last version of a CP that is in FinalText status. It is has been approved by ballot and is waiting to be integrated into the TF.
- FinalText/Integrated
- contains the version of the CP that was integrated into the TF.
- Incoming
- contains CPs which have been submitted but have not been assigned a CP number or an editor. This is the place that new incoming CPs are placed prior to the first stage of processing by the committee.
- old_versions
- Contains old versions of Completed and FinalText CPs
- Rejected
- CPs that have been submitted by rejected by the committee
- Status
- contains spreadsheets describing the status of CPs.
Archived Change Proposal pages
Ongoing work on CPs is placed on the current year CP page.