Difference between revisions of "ConCall-20071029"

From HL7 TSC
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
TSC - Technical Steering Committee  
 
TSC - Technical Steering Committee  
  
Monday, October 15, 2007 11:00 AM (US Eastern Time, GMT -5)
+
Monday, October 29, 2007 11:00 AM (US Eastern Time, GMT -5)
  
 
To participate, dial 702-894-2444 and enter pass code 1244667#
 
To participate, dial 702-894-2444 and enter pass code 1244667#
Line 12: Line 12:
  
 
=Attendance=
 
=Attendance=
 +
== Actual ==
 +
* Chair: Charlie McCay
 +
* CTO:
 +
* Domain Experts:  Jim Case (primary), Austin Kreisler (alternate)
 +
* Foundation & Technology: Ioana Singureanu (primary)
 +
* Structure & Semantic Design: Calvin Beebe (primary)
 +
* Technical & Support Services: 
 +
* Affiliate:  Charlie McCay
 +
* ARB Chair:  Charlie Mead
 +
 
== Expected ==
 
== Expected ==
 
* Chair: Charlie McCay  
 
* Chair: Charlie McCay  
Line 20: Line 30:
 
* Technical & Support Services:   
 
* Technical & Support Services:   
 
* Affiliate: Frank Oemig, Charlie McCay  
 
* Affiliate: Frank Oemig, Charlie McCay  
* ARB Chair:  
+
* ARB Chair: Charlie Mead
* TSC appointed member:
+
 
== invited ==  
 
== invited ==  
 
* Charles Jaffe (CE); Chuck Meyer (HL7 Chair); Ed Hammond (HL7 Chair Elect)
 
* Charles Jaffe (CE); Chuck Meyer (HL7 Chair); Ed Hammond (HL7 Chair Elect)
Line 29: Line 39:
 
* Technical & Support Services:  Ken McCaslin (primary), Helen Stevens Love (alternate)
 
* Technical & Support Services:  Ken McCaslin (primary), Helen Stevens Love (alternate)
  
 +
= notes =
 +
The meeting was not quorate, so discussion was informal.
 +
 +
We discussed The formation of the ARB, and the question of whether being vice-chair of the ARB was a role that it was reasonable to ask JQ to do in addition to his role as CTO.   
 +
 +
Charlie Mead explained his vision for an ARB that is recast to set the architecture for the organisation, as well as respond to questions about it.  Need to ensure that it is proactive, and that the remit is clear.  The relationship between ARB, TSC, And CTO is to be clarified -- which is responsible for what, and along with responsibility must go authority -- ie the ability to make determinations.
 +
 +
The need for timeliness was raised, and it was agreed that an ARB that does not provide timely responses is not working.
 +
 +
Calvin asked how an appointed ARB would achieve authority, which must come from the membership.  Charlie McC observed that the ARB will be appointed bythe TSC, and so it is the TSC responsibility to ensure that the ARB membership is right.  If the wider membership are unhappy, then they can always change the TSC.  The ARB appointments are only for a fixed 2 year (renewable) term -- so the TSC can make changes to switch in new faces each year if there is seen to be a need for change.
 +
 +
Ioana stated that the ARB has in the past had a very hard job of determining on architectral decisions without an underlying architecture to reference as a basis.
 +
 +
There was discussion on the issue tracking mechanism to use -- Charlie McC stated that we need a version controlled issue tracking solution, and that he would use wiki is is done by INM/MnM unless there were objections, and a better solution that had activce support on the TSC.  Ioana stated that gForge was a tool build for the job.  Austin stated that Lab were using gForge happily. Ioana dropped off the call before the discussion closed, and we left with a veiw from all that either solution would be ok - so Charlie McC statedthat he would setup the wiki  (after the call Ken and Ioana confirmed that they would support the gForge approach -- C.McC has stopped the wiki effort, and the gForge solution is being progressed)
 +
 +
   
 
=Agenda=
 
=Agenda=
 
#''(10 min)'' '''Meeting Admin'''
 
#''(10 min)'' '''Meeting Admin'''
Line 36: Line 62:
 
## '''Approve Minutes''' [[ConCall-20071015]] - McCay
 
## '''Approve Minutes''' [[ConCall-20071015]] - McCay
 
## '''Approve Minutes''' [[ConCall-20071008]] - McCay
 
## '''Approve Minutes''' [[ConCall-20071008]] - McCay
 +
## [[process for minutes approval]] - McCay
 
#''(10 min)'' '''Standing Committee Reports
 
#''(10 min)'' '''Standing Committee Reports
 
## CEO Report - Jaffe  
 
## CEO Report - Jaffe  
 
## CTO Report - Quinn  
 
## CTO Report - Quinn  
 +
## ARB report - Mead
 
## Affiliates Report - McCay/Oemig
 
## Affiliates Report - McCay/Oemig
 
## Domain Experts - Case
 
## Domain Experts - Case
Line 46: Line 74:
 
#''(5 mins)'' '''The SOA TC charter''' http://hssp.wikispaces.com/TC_Charter01 - Singureanu
 
#''(5 mins)'' '''The SOA TC charter''' http://hssp.wikispaces.com/TC_Charter01 - Singureanu
 
#''(30 min)'' '''issue review and processing''' - McCay
 
#''(30 min)'' '''issue review and processing''' - McCay
## [[tsc issue review process]]
+
## tsc issue review process -- http://lists.hl7.org/read/messages?id=117190
 
### issue tracking with version control - http://lists.hl7.org/read/messages?id=116050
 
### issue tracking with version control - http://lists.hl7.org/read/messages?id=116050
 
### issues must include a recommendation - http://lists.hl7.org/read/messages?id=115983
 
### issues must include a recommendation - http://lists.hl7.org/read/messages?id=115983

Latest revision as of 19:22, 2 November 2007

TSC - Technical Steering Committee

Monday, October 29, 2007 11:00 AM (US Eastern Time, GMT -5)

To participate, dial 702-894-2444 and enter pass code 1244667#


GoToMeeting at https://www.gotomeeting.com/join/822618174

GoToMeeting ID: 822-618-174


Attendance

Actual

  • Chair: Charlie McCay
  • CTO:
  • Domain Experts: Jim Case (primary), Austin Kreisler (alternate)
  • Foundation & Technology: Ioana Singureanu (primary)
  • Structure & Semantic Design: Calvin Beebe (primary)
  • Technical & Support Services:
  • Affiliate: Charlie McCay
  • ARB Chair: Charlie Mead

Expected

  • Chair: Charlie McCay
  • CTO:
  • Domain Experts: Jim Case (primary), Austin Kreisler (alternate)
  • Foundation & Technology: Ioana Singureanu (primary), Woody Beeler (alternate)
  • Structure & Semantic Design: Calvin Beebe (primary), Gregg Seppala (alternate)
  • Technical & Support Services:
  • Affiliate: Frank Oemig, Charlie McCay
  • ARB Chair: Charlie Mead

invited

  • Charles Jaffe (CE); Chuck Meyer (HL7 Chair); Ed Hammond (HL7 Chair Elect)

Apologies

  • CTO: John Quinn
  • HQ: Karen Van Hentenryck
  • Technical & Support Services: Ken McCaslin (primary), Helen Stevens Love (alternate)

notes

The meeting was not quorate, so discussion was informal.

We discussed The formation of the ARB, and the question of whether being vice-chair of the ARB was a role that it was reasonable to ask JQ to do in addition to his role as CTO.

Charlie Mead explained his vision for an ARB that is recast to set the architecture for the organisation, as well as respond to questions about it. Need to ensure that it is proactive, and that the remit is clear. The relationship between ARB, TSC, And CTO is to be clarified -- which is responsible for what, and along with responsibility must go authority -- ie the ability to make determinations.

The need for timeliness was raised, and it was agreed that an ARB that does not provide timely responses is not working.

Calvin asked how an appointed ARB would achieve authority, which must come from the membership. Charlie McC observed that the ARB will be appointed bythe TSC, and so it is the TSC responsibility to ensure that the ARB membership is right. If the wider membership are unhappy, then they can always change the TSC. The ARB appointments are only for a fixed 2 year (renewable) term -- so the TSC can make changes to switch in new faces each year if there is seen to be a need for change.

Ioana stated that the ARB has in the past had a very hard job of determining on architectral decisions without an underlying architecture to reference as a basis.

There was discussion on the issue tracking mechanism to use -- Charlie McC stated that we need a version controlled issue tracking solution, and that he would use wiki is is done by INM/MnM unless there were objections, and a better solution that had activce support on the TSC. Ioana stated that gForge was a tool build for the job. Austin stated that Lab were using gForge happily. Ioana dropped off the call before the discussion closed, and we left with a veiw from all that either solution would be ok - so Charlie McC statedthat he would setup the wiki (after the call Ken and Ioana confirmed that they would support the gForge approach -- C.McC has stopped the wiki effort, and the gForge solution is being progressed)


Agenda

  1. (10 min) Meeting Admin
    1. Roll Call - McCay
    2. Accept Agenda - McCay
    3. Approve Minutes ConCall-20071022 - McCay
    4. Approve Minutes ConCall-20071015 - McCay
    5. Approve Minutes ConCall-20071008 - McCay
    6. process for minutes approval - McCay
  2. (10 min) Standing Committee Reports
    1. CEO Report - Jaffe
    2. CTO Report - Quinn
    3. ARB report - Mead
    4. Affiliates Report - McCay/Oemig
    5. Domain Experts - Case
    6. Foundation & Technology - Singureanu
    7. Structure & Semanic Design - Beebe
    8. Technical & Support Services - McCaslin
  3. (5 mins) The SOA TC charter http://hssp.wikispaces.com/TC_Charter01 - Singureanu
  4. (30 min) issue review and processing - McCay
    1. tsc issue review process -- http://lists.hl7.org/read/messages?id=117190
      1. issue tracking with version control - http://lists.hl7.org/read/messages?id=116050
      2. issues must include a recommendation - http://lists.hl7.org/read/messages?id=115983
      3. Authority of the CTO / Chair of the TSC to close issues
    2. looking at current issues
      1. issue 15:
      2. issues list:
  5. (5 min) Other Business

Agenda item list (our sand box for future meetings)

Click for TSC Action Item List