Difference between revisions of "Public Comment Process"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
Public comment should be considered the prelude to publication. A committee should be largely satisfied with the contents of a document before it is sent out for Public Comment. | Public comment should be considered the prelude to publication. A committee should be largely satisfied with the contents of a document before it is sent out for Public Comment. | ||
| + | Note in the description below that the "secretariat" is understood to be the RSNA. Specific tasks may be assigned to staff and/or contractors of RSNA in performance of the function. | ||
Period: 30 days | Period: 30 days | ||
| − | * [[Review Process|Approve for public comment]] (''' | + | * [[Review Process|Approve for public comment]] ('''Technical Committee''') |
| − | * Post PC draft of Document on the Wiki (''' | + | * Post PC draft of Document on the Wiki ('''editor/secretariat''') |
* Send announcement to mailing lists ('''secretariat''') | * Send announcement to mailing lists ('''secretariat''') | ||
** detail location of document to be reviewed, deadline for comment submission, method of submission | ** detail location of document to be reviewed, deadline for comment submission, method of submission | ||
** provide a link to the [[:Media:QIBA_Public_Comment_Template-2011.01.doc | QIBA Public Comment Template]] | ** provide a link to the [[:Media:QIBA_Public_Comment_Template-2011.01.doc | QIBA Public Comment Template]] | ||
* Email comments to secretariat ('''Commenters''') | * Email comments to secretariat ('''Commenters''') | ||
| − | ** commenters include committee members, other QIBA | + | ** commenters include committee members, other QIBA people, external bodies |
** this is the key point for asynchronous engagement | ** this is the key point for asynchronous engagement | ||
** please use the provided comment form, it saves the author having to transcribe your comments | ** please use the provided comment form, it saves the author having to transcribe your comments | ||
* Collate all comments into a spreadsheet ('''secretariat/author''') | * Collate all comments into a spreadsheet ('''secretariat/author''') | ||
** sort by line number and priority (Low/Med/High) | ** sort by line number and priority (Low/Med/High) | ||
| − | * Resolve comments with priority Low (''' | + | * Resolve comments with priority Low ('''editor''') |
** if any Low comments prove problematic, elevate to Med | ** if any Low comments prove problematic, elevate to Med | ||
| − | * Review Med & High comments (''' | + | * Review Med & High comments ('''Technical Committee''') |
** walk through document | ** walk through document | ||
** each comment may be: | ** each comment may be: | ||
| Line 25: | Line 26: | ||
*** rejected = committee does not agree with issue (document reason, e.g. out of scope, ) | *** rejected = committee does not agree with issue (document reason, e.g. out of scope, ) | ||
*** resolved = issue accepted but resolved differently than proposed | *** resolved = issue accepted but resolved differently than proposed | ||
| − | * Record resolution in spreadsheet (''' | + | * Record resolution in spreadsheet ('''editor''') |
| − | * Post resolution spreadsheet and updated Document on the Wiki (''' | + | * Post resolution spreadsheet and updated Document on the Wiki ('''editor/secretariat''') |
Revision as of 13:24, 22 June 2011
Public Comment is intended to allow both regular participants in QIBA Activities and also those who don't have the time to dedicate to regular participation a chance to contribute their thoughts on proposed specifications before they are formally released. Comments are accepted from all.
Public comment should be considered the prelude to publication. A committee should be largely satisfied with the contents of a document before it is sent out for Public Comment.
Note in the description below that the "secretariat" is understood to be the RSNA. Specific tasks may be assigned to staff and/or contractors of RSNA in performance of the function.
Period: 30 days
- Approve for public comment (Technical Committee)
- Post PC draft of Document on the Wiki (editor/secretariat)
- Send announcement to mailing lists (secretariat)
- detail location of document to be reviewed, deadline for comment submission, method of submission
- provide a link to the QIBA Public Comment Template
- Email comments to secretariat (Commenters)
- commenters include committee members, other QIBA people, external bodies
- this is the key point for asynchronous engagement
- please use the provided comment form, it saves the author having to transcribe your comments
- Collate all comments into a spreadsheet (secretariat/author)
- sort by line number and priority (Low/Med/High)
- Resolve comments with priority Low (editor)
- if any Low comments prove problematic, elevate to Med
- Review Med & High comments (Technical Committee)
- walk through document
- each comment may be:
- accepted = proposed text accepted as is
- rejected = committee does not agree with issue (document reason, e.g. out of scope, )
- resolved = issue accepted but resolved differently than proposed
- Record resolution in spreadsheet (editor)
- Post resolution spreadsheet and updated Document on the Wiki (editor/secretariat)