SDO TC Status

hi bryan,
thx,
As i think i said before, privately, if the TC wants to shut
down, there is a simple and straightforward way to do that in the TC
Process.
All it takes is a Full Majority Vote of the TC (see section 2.15)
Note: the other 2 methods, TC admin and Board, are meant to
take care of TCs that have either "disappeared" or "gone rogue".  cheers,
jeff  On Jan 27, 2011, at 6:42 AM, Bryan Aupperle wrote:
> That is indeed the case. >
> Bryan Aupperle, Ph.D.
> STSM, WebSphere Enterprise Platform Software Solution Architect
> WW Center of Excellence for Enterprise Systems & Banking Center of
> Excellence Application Integration Architect >
> Research Triangle Park,  NC > +1 919-254-7508 (T/L 444-7508)
> Internet Address:  > > >
>
From:
Jeff Mischkinsky <>
>
To:
"Patil, Sanjay" <>
>
Cc:
Bryan Aupperle/Raleigh/IBM@IBMUS, "  > " <>, ""
> <>
>
Date:
01/26/2011 07:11 PM
>
Subject:
Re: [opencsa-liaison] SDO TC Status > > >
> hi,
>
Actually, based upon what i've seen. I think the "real" proposal is
> to close the TC.
>
The way I understand it, they haven't completed any of the
> deliverables, and have no desire to do so. >
>
Please correct me, if i got that wrong.
>
cheers,
>
jeff
> On Jan 26, 2011, at 2:02 PM, Patil, Sanjay wrote: > > > >
> Hi Bryan, > > >
> If stopping the SDO 3.0 work is final (that is, the TC does not >
> intend to pick up the work later), then I think it will amount to >
> changing the chartered deliverables of the TC, in which case the TC >
> might want to re-charter itself! On the other hand, if stopping the >
> SDO 3.0 work reflects just a temporary pause in the TC’s operations > > (for the SDO 3 work) due to the current resource/commitment >
> situation, then that is a different issue and might not warrant re- >
> chartering, etc, IMO. > > >
> Best wishes, >
> Sanjay > > >
>
From: Bryan Aupperle [ mailto: ] >
> Sent: Wednesday, January 26, 2011 1:37 PM >
>
To:  >
>
Cc:  >
>
Subject: [opencsa-liaison] SDO TC Status > > >
> Due to changing priorities of the companies currently represented by >
> voting members of the SDO TC, the TC has concluded that it is >
> appropriate to stop work on SDO 3.0. > > >
> While much work has been done on the 3.0 specifications, it is clear >
> that there are insufficient commitments to complete these >
> specifications and work on a test suite has not even started. > > >
> This decision is solely based on the current lack of resources and >
> commitments. > > >
> By now, internal communications should have taken place so this news >
> should not be a surprise to anyone, but it is appropriate for me to >
> notify the liaison subcommittee as the representative from the SDO
> TC. > > >
> Bryan Aupperle, Ph.D. >
> STSM, WebSphere Enterprise Platform Software Solution Architect >
> WW Center of Excellence for Enterprise Systems & Banking Center of >
> Excellence Application Integration Architect > > >
> Research Triangle Park,  NC > > +1 919-254-7508 (T/L 444-7508) >
> Internet Address:  > > --
> Jeff
> Mischkinsky
>
jeff  > .
> Sr. Director, Oracle Fusion
> Middleware  >
> +1(650)506-1975
>
and Web Services
> Standards
>
500
> Oracle Parkway, M/S 2OP9
> Oracle
>
Redwood
>
Shores, CA 94065 > > > > > > > > > >

--
Jeff Mischkinsky
		
Sr. Director, Oracle Fusion Middleware 				+1(650)506-1975 	and Web Services Standards
			500 Oracle Parkway, M/S 2OP9 Oracle								Redwood
Shores, CA 94065