Difference between revisions of "ConCall-20070213"
WoodyBeeler (talk | contribs) |
WoodyBeeler (talk | contribs) |
||
| Line 1: | Line 1: | ||
T3F - Transitional Technical Task Force | T3F - Transitional Technical Task Force | ||
| − | |||
| − | |||
Tuesday Feb 13, 2007 12:00 PM (US Eastern Time, GMT -5) | Tuesday Feb 13, 2007 12:00 PM (US Eastern Time, GMT -5) | ||
| − | + | =Present= | |
| − | + | Beeler, Blobel, Buitendijk, Case, Lorenzi, Parker, Quinn, Walker | |
| − | + | :'''Future absences''' | |
| − | + | ::February 20, Blobel, Case | |
| − | + | ::February 27, Beeler, Quinn | |
| − | + | =Prior Homework= | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | = | ||
| − | |||
| − | :''' | ||
| − | =Homework= | ||
Prepare to continue advancing two documents in parallel: | Prepare to continue advancing two documents in parallel: | ||
#[http://www.hl7.org/documentcenter/public/wg/t3f/general/WorkingDraft-TD-Charts.ppt The draft TD structure charts] which includes Craig's chart and two of Virginia's charts. | #[http://www.hl7.org/documentcenter/public/wg/t3f/general/WorkingDraft-TD-Charts.ppt The draft TD structure charts] which includes Craig's chart and two of Virginia's charts. | ||
| − | |||
| − | |||
| − | |||
#[[CM_comments_on_TD_definition_from_Strategic_Recommendations|The list of TD responsibilities and relationships.]] | #[[CM_comments_on_TD_definition_from_Strategic_Recommendations|The list of TD responsibilities and relationships.]] | ||
| − | + | =Accepted Agenda= | |
| − | |||
| − | |||
| − | = | ||
#''(05 min)'' Roll Call & Accept agenda | #''(05 min)'' Roll Call & Accept agenda | ||
| + | #''(02 min)'' Status reports | ||
#''(50 min)'' Technical Directorate Discussions | #''(50 min)'' Technical Directorate Discussions | ||
#:''(25 min)'' Charts of TD hierarchy and relationships | #:''(25 min)'' Charts of TD hierarchy and relationships | ||
#:''(25 min)'' List of TD responsibilities | #:''(25 min)'' List of TD responsibilities | ||
#'' (05 min)'' Next Steps | #'' (05 min)'' Next Steps | ||
| + | =Status Reports= | ||
| + | Beeler reported that he discovered, belatedly, e-mails requesting T3F status reports to the Board which had not been forwarded. He will send this in. | ||
| + | =Technical Directorate Discussion= | ||
| + | ==[http://www.hl7.org/documentcenter/public/wg/t3f/general/WorkingDraft-TD-Charts.ppt Slide 1-TD Hierarchy diagram]== | ||
| + | There was a free ranging discussion of Organizational hierarchy begun at last weeks meeting. | ||
| + | |||
| + | We noted the strong preference of this group to seek an alternate title for the CTO --perhaps Technical Coordinating Officer. The concerns arise because of the role of CTOs in other standards bodies and because of the statement in one SI document that "CTO leads the Technical Directorate. While the CTO may seek consensus among the members of the TD, as the responsible party he or she holds the final decision making authority." An implied veto-power such as this sits very badly with the volunteer membership. We were advised to make this position known to the Transition Task Force as soon as possible. | ||
| + | |||
| + | Omissions: It was noted that the Security TC is not in the list of committees in third slide and should be. | ||
| + | |||
| + | Discussed the relationship of the various Board-appointed committees to the hierarchy. Must list all the Board-appointed committees. A number of these should report to the TD, including Electronic Services, Publishing, Architecture Review Board, Tooling, Implementation, Marketing, and Education. (Not exhaustive) While others like Legal Affairs, Finance, Bylaws, etc. will likely remain Board-appointed. | ||
| + | |||
| + | Discussed the relationship of these "appointed committees" to the TD and observed: | ||
| + | *Most of these are performing or overseeing "support" functions rather than "standards development" or policy functions | ||
| + | *These should each have a direct line relationship to the TD and a dotted line relationship to either the CTO/TCO, CEO or COO | ||
| + | *There should be at least one designated "staff" participant in each of these | ||
| + | *We need to add TD-appointed committee responsibilities to the TD list | ||
| + | *These groups need some form of representation in the TD | ||
| + | *These groups should expect to provide routine reports to the TD | ||
| + | |||
=[[T3F Agenda item list|Agenda item list (our sand box for future meetings)]]= | =[[T3F Agenda item list|Agenda item list (our sand box for future meetings)]]= | ||
=[[T3F Action item list|Click for T3F Action Item List]]= | =[[T3F Action item list|Click for T3F Action Item List]]= | ||
Revision as of 19:07, 13 February 2007
T3F - Transitional Technical Task Force
Tuesday Feb 13, 2007 12:00 PM (US Eastern Time, GMT -5)
Contents
Present
Beeler, Blobel, Buitendijk, Case, Lorenzi, Parker, Quinn, Walker
- Future absences
- February 20, Blobel, Case
- February 27, Beeler, Quinn
Prior Homework
Prepare to continue advancing two documents in parallel:
- The draft TD structure charts which includes Craig's chart and two of Virginia's charts.
- The list of TD responsibilities and relationships.
Accepted Agenda
- (05 min) Roll Call & Accept agenda
- (02 min) Status reports
- (50 min) Technical Directorate Discussions
- (25 min) Charts of TD hierarchy and relationships
- (25 min) List of TD responsibilities
- (05 min) Next Steps
Status Reports
Beeler reported that he discovered, belatedly, e-mails requesting T3F status reports to the Board which had not been forwarded. He will send this in.
Technical Directorate Discussion
Slide 1-TD Hierarchy diagram
There was a free ranging discussion of Organizational hierarchy begun at last weeks meeting.
We noted the strong preference of this group to seek an alternate title for the CTO --perhaps Technical Coordinating Officer. The concerns arise because of the role of CTOs in other standards bodies and because of the statement in one SI document that "CTO leads the Technical Directorate. While the CTO may seek consensus among the members of the TD, as the responsible party he or she holds the final decision making authority." An implied veto-power such as this sits very badly with the volunteer membership. We were advised to make this position known to the Transition Task Force as soon as possible.
Omissions: It was noted that the Security TC is not in the list of committees in third slide and should be.
Discussed the relationship of the various Board-appointed committees to the hierarchy. Must list all the Board-appointed committees. A number of these should report to the TD, including Electronic Services, Publishing, Architecture Review Board, Tooling, Implementation, Marketing, and Education. (Not exhaustive) While others like Legal Affairs, Finance, Bylaws, etc. will likely remain Board-appointed.
Discussed the relationship of these "appointed committees" to the TD and observed:
- Most of these are performing or overseeing "support" functions rather than "standards development" or policy functions
- These should each have a direct line relationship to the TD and a dotted line relationship to either the CTO/TCO, CEO or COO
- There should be at least one designated "staff" participant in each of these
- We need to add TD-appointed committee responsibilities to the TD list
- These groups need some form of representation in the TD
- These groups should expect to provide routine reports to the TD
