This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Ballot Process Review"
Jump to navigation
Jump to search
(Added name of commenter) |
Bamarquard (talk | contribs) |
||
| Line 15: | Line 15: | ||
* Ioana Singureanu: We could create one tracker per product, one per release, one per ballot. What are the the pros and cons of each? | * Ioana Singureanu: We could create one tracker per product, one per release, one per ballot. What are the the pros and cons of each? | ||
* Ioana Singureanu: We could also use a tracker for "to do" items instead of a "todo.txt" file: http://gforge.hl7.org/gf/project/fhir/scmsvn/?action=browse&path=%2Ftrunk%2Ftodo.txt&view=log | * Ioana Singureanu: We could also use a tracker for "to do" items instead of a "todo.txt" file: http://gforge.hl7.org/gf/project/fhir/scmsvn/?action=browse&path=%2Ftrunk%2Ftodo.txt&view=log | ||
| + | * Brett Marquard: Is it possible to add custom metadata field to group comments? For example, the 'comment grouping' column in the existing spreadsheet is very helpful for categorizing comments and planned discussion dates. | ||
| + | * Brett Marquard: Is it possible to export proposed dispositions for block vote? | ||
| + | * Brett Marquard: Is it possible to record votes in gForge? Meeting meetings are an important backup. | ||
| + | * Brett Marquard: Will there be a way to assign vote counts to multiple comments at once? | ||
| + | * Brett Marquard: Is there a way to state comments are related to a specific project and resource? | ||
Revision as of 17:50, 10 March 2015
Instructions
3/9/2015 - Wiki based review of the draft FHIR Ballot Process
- This wiki based review of the draft FHIR Ballot Process is sponsored by the TSC as well as the following groups: FMG, FGB, EST and Publishing.
- The comments submitted during this review will be reviewed and acted on by FMG. The TSC will have final approval of the proposed process.
- The wiki review is one of the steps identified in the TSC's process for adoption of new process document found here: http://www.hl7.org/documentcenter/public/procedures/IntroducingNewProcessesToHL7.zip
- The comment period is open from 3/9/2014 through EOD 3/20/2015.
- The draft FHIR Ballot Process is here: FHIR Ballot Process
- During the comment period, please submit your comments below including at least your name, item, existing wording, proposed wording, and comment. Thank you.
Comments
Enter your comments below this line.
- Ioana Singureanu: We need to create a very specific type of tracker (regarding metadata) that ensures we have all the metadata required by ANSI/balloting. The current FHIR "Issues" tracker is not quite sufficient because it does not support the information in the ballot spreadsheet.
- Ioana Singureanu: We could create one tracker per product, one per release, one per ballot. What are the the pros and cons of each?
- Ioana Singureanu: We could also use a tracker for "to do" items instead of a "todo.txt" file: http://gforge.hl7.org/gf/project/fhir/scmsvn/?action=browse&path=%2Ftrunk%2Ftodo.txt&view=log
- Brett Marquard: Is it possible to add custom metadata field to group comments? For example, the 'comment grouping' column in the existing spreadsheet is very helpful for categorizing comments and planned discussion dates.
- Brett Marquard: Is it possible to export proposed dispositions for block vote?
- Brett Marquard: Is it possible to record votes in gForge? Meeting meetings are an important backup.
- Brett Marquard: Will there be a way to assign vote counts to multiple comments at once?
- Brett Marquard: Is there a way to state comments are related to a specific project and resource?
