RE: [bpel4people] 4/16 BPEL4People TC Meeting - Cancelled

["Martin Chapman" <martin.chapman@oracle.com>]

I strongly disagree with cancelling and with giving the editing sub-committee any powers to analyse issues.
Until an issue is opened by a full TC committee vote, no one should really spend any time on an issue.
Aside from the Issues editor entering the issue into JIRA, there is no defined role of the editing SC prior to an issue being opened
by the TC.

Please re-consider re-instating the meeting, and letting the TC formally open issues and get started.

Martin.

>-----Original Message-----
>From: Dave Ings [mailto:ings@ca.ibm.com] 
>Sent: Monday, April 14, 2008 2:15 PM
>To: bpel4people@lists.oasis-open.org
>Subject: [bpel4people] 4/16 BPEL4People TC Meeting - Cancelled
>
>
>
>Hi,
>
>Acting upon the recommendation of the editing subcommittee, 
>I'm cancelling this week's BPEL4People TC meeting. As we've 
>gone to bi-weekly meetings, the next scheduled meeting will be 
>Wednesday 4/30.
>
>Given our large team size, full TC meetings are very expensive 
>time-wise. Therefore IMHO it makes sense to hold our next 
>meeting when a critical mass of issues has been assembled and 
>analyzed by the editing subcommittee - and the SC needs more 
>time to complete their first pass.
>
>As an aside, there are a couple of reportedly simple issues we 
>could have used to test/practise our process, had we kept the 
>meeting - and there would have been value in this - but given 
>the large size of the team I think it best to batch them up 
>for later. The email list can always be used to discuss any 
>pressing issues in advance of the next scheduled meeting.
>
>Feedback and comments are always welcome ... Dave.
>
>Regards, Dave Ings,
>Emerging Software Standards
>Email: ings@ca.ibm.com
>Yahoo Messenger: dave_ings
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS 
>TC that generates this mail.  You may a link to this group and 
>all your TCs in OASIS
>at: 
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>
>