[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: No Subject
I've not sent a note to the full TC on the process pending discussion with
the Oasis staff. It appears they cannot provide the type of email list we
requested where everyone could post, but only the issues editor and backup
would receive. That leaves us with two choices, I think:
1. folks send issues directly to the issue editor (Peter and a backup)
2. folks send issues to the TC email list with "New Issue" in the subject
line.
In both cases, the issue editor would then validate the formating, assign
an issue number, add it to the issues list and send an email announcing
the new issue. With the first option, we eliminate an extra email to the
whole group, but lose some visibility. With the second option, we ask
people to ignore the new issue mail and refrain from starting discussion
until the announcement with the issue number so that the email threads can
be linked to the issue in the issue list. I have a slight preference for
2 because of the visibility, but am willing to go either way and, in
particular, would defer to Peter's judgement as he's the one who's stepped
forward to act as editor.
I think it's worthwhile to have another call to conclude this process
before presenting to the full TC. John has put this on the agenda for
next week. We've tentatively set up a call for 3pm eastern/12pm pacific
on Monday July 7. Dial in info is: 888-711-4576, Toll/International
Callers = 1-484-630-9377, Password = 20061. I'll be on vacation, so
please let John know whether you can make this. If not, please send
comments beforehand.
I'm really hoping that we can get this settled soon so we can move on to
working on the issues themselves. Thanks for your help.
Regards, Diane
IBM Dynamic e-business Technologies
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123
----- Forwarded by Diane Jordan/Raleigh/IBM on 07/02/2003 11:40 PM -----
Diane Jordan
06/30/2003 10:55 PM
To: bpel rqmts <wsbpel-reqts@lists.oasis-open.org>
cc:
From: Diane Jordan/Raleigh/IBM@IBMUS
Subject: Re: [wsbpel] Re: [wsbpel-reqts] A couple things we need for WS BPEL TC
issue process
This is the process we've discussed as I understand it:
- issue is sent to issue editor
- issue editor sends email to everyone "announcing" issue and adds to the
issues document which will include links to appropriate email threads
- replies to the announcement email go to everyone
- other emails discussing the issue will be captured in the document if
the subject line is formatted correctly
- chair will find champion for each issue to help drive progress
- an issues meeting will be held weekly to review issues and formulate
proposed motions for the full tc to consider. This will be open to all tc
members but not an official meeting.
- chair will look to output of issues meeting for input on which issues
are ready to be discussed at a TC meeting and will also take input from TC
members. Chair will include list of issues to be discussed in the agenda
sent the friday before the TC call. Agenda should include link to
appropriate info including the issues list.
- motions to resolve issues will be covered in the official tc calls.
Motions may be brought by anyone, but "best practices" encourages use of
the issues team and circulating motions prior to the calls.
Have I got this straight? Do we still think this is ok, given the
emails of the last few days?
This provides regular "reminders" of issues (new and those to be covered
with the full TC) which I think could be structured to include a link to
the issues list. This does involve email to everyone on every new issue,
and everyone will be copied on the replies to those issues. Note, I've
sent this to the issues/requirements process team only - I'm preparing the
note for the full TC that we discussed last week.
Regards, Diane
IBM Dynamic e-business Technologies
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123
--=_alternative 00179DCF85256D58_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">From comments received, I think the outline of the issues process below is ok, with the input that a weekly summary report of new issues would be desirable. This seems ok, if someone is willing to volunteer to produce one. If not, everyone will receive an email for each new issue and the agenda for the bi-weekly calls will also include both those issues ready for discussion in the next call and a link to the current issues list. </font>
<br>
<br><font size=2 face="sans-serif">I've not sent a note to the full TC on the process pending discussion with the Oasis staff. It appears they cannot provide the type of email list we requested where everyone could post, but only the issues editor and backup would receive. That leaves us with two choices, I think:</font>
<br><font size=2 face="sans-serif">1. folks send issues directly to the issue editor (Peter and a backup)</font>
<br><font size=2 face="sans-serif">2. folks send issues to the TC email list with "New Issue" in the subject line. </font>
<br><font size=2 face="sans-serif">In both cases, the issue editor would then validate the formating, assign an issue number, add it to the issues list and send an email announcing the new issue. With the first option, we eliminate an extra email to the whole group, but lose some visibility. With the second option, we ask people to ignore the new issue mail and refrain from starting discussion until the announcement with the issue number so that the email threads can be linked to the issue in the issue list. I have a slight preference for 2 because of the visibility, but am willing to go either way and, in particular, would defer to Peter's judgement as he's the one who's stepped forward to act as editor. </font>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">I think it's worthwhile to have another call to conclude this process before presenting to the full TC. John has put this on the agenda for next week. We've tentatively set up a call for 3pm eastern/12pm pacific on Monday July 7. Dial in info is: 888-711-4576, Toll/International Callers = 1-484-630-9377, Password = 20061. I'll be on vacation, so please let John know whether you can make this. If not, please send comments beforehand. </font>
<br>
<br><font size=2 face="sans-serif">I'm really hoping that we can get this settled soon so we can move on to working on the issues themselves. Thanks for your help.</font>
<br><font size=2 face="sans-serif"><br>
Regards, Diane<br>
IBM Dynamic e-business Technologies<br>
drj@us.ibm.com<br>
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123<br>
</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Diane Jordan/Raleigh/IBM on 07/02/2003 11:40 PM -----</font>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Diane Jordan</b></font>
<p><font size=1 face="sans-serif">06/30/2003 10:55 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: bpel rqmts <wsbpel-reqts@lists.oasis-open.org></font>
<br><font size=1 face="sans-serif"> cc: </font>
<br><font size=1 face="sans-serif"> From: Diane Jordan/Raleigh/IBM@IBMUS</font>
<br><font size=1 face="sans-serif"> Subject: Re: [wsbpel] Re: [wsbpel-reqts] A couple things we need for WS BPEL TC issue process</font>
<br></table>
<br>
<br><font size=2 face="sans-serif">This is the process we've discussed as I understand it: </font>
<br><font size=2 face="sans-serif">- issue is sent to issue editor</font>
<br><font size=2 face="sans-serif">- issue editor sends email to everyone "announcing" issue and adds to the issues document which will include links to appropriate email threads</font>
<br><font size=2 face="sans-serif">- replies to the announcement email go to everyone </font>
<br><font size=2 face="sans-serif">- other emails discussing the issue will be captured in the document if the subject line is formatted correctly</font>
<br><font size=2 face="sans-serif">- chair will find champion for each issue to help drive progress </font>
<br><font size=2 face="sans-serif">- an issues meeting will be held weekly to review issues and formulate proposed motions for the full tc to consider. This will be open to all tc members but not an official meeting. </font>
<br><font size=2 face="sans-serif">- chair will look to output of issues meeting for input on which issues are ready to be discussed at a TC meeting and will also take input from TC members. Chair will include list of issues to be discussed in the agenda sent the friday before the TC call. Agenda should include link to appropriate info including the issues list. </font>
<br><font size=2 face="sans-serif">- motions to resolve issues will be covered in the official tc calls. Motions may be brought by anyone, but "best practices" encourages use of the issues team and circulating motions prior to the calls.</font>
<br>
<br><font size=2 face="sans-serif">Have I got this straight? Do we still think this is ok, given the emails of the last few days? </font>
<br><font size=2 face="sans-serif">This provides regular "reminders" of issues (new and those to be covered with the full TC) which I think could be structured to include a link to the issues list. This does involve email to everyone on every new issue, and everyone will be copied on the replies to those issues. Note, I've sent this to the issues/requirements process team only - I'm preparing the note for the full TC that we discussed last week. </font>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">Regards, Diane<br>
IBM Dynamic e-business Technologies<br>
drj@us.ibm.com<br>
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123</font>
--=_alternative 00179DCF85256D58_=--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]