[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:=20
1. folks send issues directly to the issue editor (Peter and a backup)=20
2. folks send issues to the TC email list with "New Issue" in the
subject line. =20
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.=20
=20
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 =3D 1-484-630-9377, Password =3D 20061. =
I'll be
on vacation, so please let John know whether you can make this. If not,
please send comments beforehand. =20
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.=20
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=20
06/30/2003 10:55 PM=20
=20
To: bpel rqmts <wsbpel-reqts@lists.oasis-open.org>=20
cc: =20
From: Diane Jordan/Raleigh/IBM@IBMUS=20
Subject: Re: [wsbpel] Re: [wsbpel-reqts] A couple things
we need for WS BPEL TC issue process=20
This is the process we've discussed as I understand it: =20
- issue is sent to issue editor=20
- issue editor sends email to everyone "announcing" issue and adds to
the issues document which will include links to appropriate email
threads=20
- replies to the announcement email go to everyone=20
- other emails discussing the issue will be captured in the document if
the subject line is formatted correctly=20
- chair will find champion for each issue to help drive progress =20
- 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. =20
- 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.=20
- 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.=20
Have I got this straight? Do we still think this is ok, given the
emails of the last few days?=20
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. =20
=20
Regards, Diane
IBM Dynamic e-business Technologies
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123
------_=_NextPart_001_01C34193.2B24B500
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2>Having=20
noted the discussion on weekly summaries etc, I've been tweaking the =
scripts so=20
issues can have a field identifying when they were last changed, and =
also the=20
scripts can produce multiple tables sorted or selected on different =
fields - so=20
the top of the list and/or a separate document (or email) can have a =
table=20
of the new and recently changed issues (linked to the =
substance). =20
I'll put up a new, up-to-date list once I've got it all=20
together.</FONT></SPAN></DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2>On the=20
weekly summary question, I'd generally assumed that I would normally =
suppress=20
the document-uploaded message to the group when I put up a new =
issues list=20
edition. I could switch that back on once a week, or send a separate=20
announcement, perhaps containing a summary table.</FONT></SPAN></DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2>Having=20
seen Yuzo's new issue (link semantics in event handlers) come in, and =
the brief=20
discussion on it I think it will be tolerable, and may well be =
beneficial to=20
have the new request on an open list. I will often be able to =
start off=20
with links to the pre-discussion (if it doesn't get too large, and stays =
on=20
topic). </FONT></SPAN></DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2>Did=20
you get anywhere on the fixed URL issue ? (I noticed one of the =
other=20
groups had similar problems, though for a different reason - that was =
schemas=20
that needed to cross-refer to each other's location.) In my mind, =
there's=20
an interaction between a fixed URL and how up-to-date I keep the =
list. If=20
the url is always different, it would seem to be unhelpful to do very =
frequent=20
uploads, and better to batch up changes over a few days (and probably =
always=20
announce it). If the url can stay fixed, there's no downside in keeping =
it as=20
up-to-date as I get round to. (the mail-trolling updates can be made =
nearly=20
automatic)</FONT></SPAN></DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
should be ok for the discussion on (for me) Monday =
evening.</FONT></SPAN></DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2>Peter</FONT></SPAN></DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D630385011-03072003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Diane Jordan=20
[mailto:drj@us.ibm.com] <BR><B>Sent:</B> 03 July 2003 =
05:18<BR><B>To:</B> bpel=20
rqmts<BR><B>Subject:</B> [wsbpel-reqts] Issue process update - =
conference call=20
Monday July 7, 3pm eastern? <BR><BR></FONT></DIV><BR><FONT =
face=3Dsans-serif=20
size=3D2>From comments received, I think the outline of the issues =
process below=20
is ok, with the input that a weekly summary report of new issues would =
be=20
desirable. This seems ok, if someone is willing to volunteer to =
produce=20
one. If not, everyone will receive an email for each new issue =
and the=20
agenda for the bi-weekly calls will also include both those issues =
ready for=20
discussion in the next call and a link to the current issues list. =
=20
</FONT><BR><BR><FONT face=3Dsans-serif size=3D2>I've not sent a =
note to the=20
full TC on the process pending discussion with the Oasis staff. =
It=20
appears they cannot provide the type of email list we requested where =
everyone=20
could post, but only the issues editor and backup would receive. =
That=20
leaves us with two choices, I think:</FONT> <BR><FONT =
face=3Dsans-serif=20
size=3D2>1. folks send issues directly to the issue editor =
(Peter and a=20
backup)</FONT> <BR><FONT face=3Dsans-serif size=3D2>2. folks =
send issues to=20
the TC email list with "New Issue" in the subject line. =20
</FONT><BR><FONT face=3Dsans-serif size=3D2>In both cases, the issue =
editor would=20
then validate the formating, assign an issue number, add it to the =
issues list=20
and send an email announcing the new issue. With the first =
option, we=20
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=20
refrain from starting discussion until the announcement with the issue =
number=20
so that the email threads can be linked to the issue in the issue =
list. =20
I have a slight preference for 2 because of the visibility, but am =
willing to=20
go either way and, in particular, would defer to Peter's judgement as =
he's the=20
one who's stepped forward to act as editor. </FONT><BR><FONT =
face=3Dsans-serif=20
size=3D2> </FONT><BR><FONT face=3Dsans-serif size=3D2>I think =
it's worthwhile=20
to have another call to conclude this process before presenting to the =
full=20
TC. John has put this on the agenda for next week. =
We've=20
tentatively set up a call for 3pm eastern/12pm pacific on Monday July =
7.=20
Dial in info is: 888-711-4576, Toll/International Callers =
=3D=20
1-484-630-9377, Password =3D 20061. I'll be on vacation, so =
please let=20
John know whether you can make this. If not, please send =
comments=20
beforehand. </FONT> <BR><BR><FONT face=3Dsans-serif size=3D2>I'm =
really=20
hoping that we can get this settled soon so we can move on to working =
on the=20
issues themselves. Thanks for your help.</FONT> <BR><FONT=20
face=3Dsans-serif size=3D2><BR>Regards, Diane<BR>IBM Dynamic =
e-business=20
Technologies<BR>drj@us.ibm.com<BR>(919)254-7221 or 8-444-7221, Mobile: =
919-624-5123<BR></FONT><BR><FONT face=3Dsans-serif color=3D#800080 =
size=3D1>-----=20
Forwarded by Diane Jordan/Raleigh/IBM on 07/02/2003 11:40 PM =
-----</FONT> <BR>
<TABLE width=3D"100%">
<TBODY>
<TR vAlign=3Dtop>
<TD>
<TD><FONT face=3Dsans-serif size=3D1><B>Diane Jordan</B></FONT>=20
<P><FONT face=3Dsans-serif size=3D1>06/30/2003 10:55 PM</FONT> =
<BR></P>
<TD><FONT face=3DArial size=3D1> =
</FONT><BR><FONT=20
face=3Dsans-serif size=3D1> To: =
=20
bpel rqmts =
<wsbpel-reqts@lists.oasis-open.org></FONT>=20
<BR><FONT face=3Dsans-serif size=3D1> =
cc: =20
</FONT> <BR><FONT face=3Dsans-serif =
size=3D1> =20
From: Diane=20
Jordan/Raleigh/IBM@IBMUS</FONT> <BR><FONT face=3Dsans-serif =
size=3D1> =20
Subject: Re: =
[wsbpel]=20
Re: [wsbpel-reqts] A couple things we need for WS BPEL TC issue=20
process</FONT> <BR></TR></TBODY></TABLE><BR><BR><FONT =
face=3Dsans-serif=20
size=3D2>This is the process we've discussed as I understand it: =
=20
</FONT> <BR><FONT face=3Dsans-serif size=3D2>- issue is sent to =
issue=20
editor</FONT> <BR><FONT face=3Dsans-serif size=3D2>- issue editor =
sends email to=20
everyone "announcing" issue and adds to the issues document which will =
include=20
links to appropriate email threads</FONT> <BR><FONT face=3Dsans-serif =
size=3D2>-=20
replies to the announcement email go to everyone </FONT><BR><FONT=20
face=3Dsans-serif size=3D2>- other emails discussing the issue will be =
captured in=20
the document if the subject line is formatted correctly</FONT> =
<BR><FONT=20
face=3Dsans-serif size=3D2>- chair will find champion for each issue =
to help drive=20
progress </FONT> <BR><FONT face=3Dsans-serif size=3D2>- an =
issues meeting=20
will be held weekly to review issues and formulate proposed motions =
for the=20
full tc to consider. This will be open to all tc members but not =
an=20
official meeting. </FONT> <BR><FONT face=3Dsans-serif size=3D2>- =
chair will=20
look to output of issues meeting for input on which issues are ready =
to be=20
discussed at a TC meeting and will also take input from TC members.=20
Chair will include list of issues to be discussed in the agenda =
sent the=20
friday before the TC call. Agenda should include link to =
appropriate=20
info including the issues list. </FONT><BR><FONT face=3Dsans-serif =
size=3D2>-=20
motions to resolve issues will be covered in the official tc calls.=20
Motions may be brought by anyone, but "best practices" =
encourages use of=20
the issues team and circulating motions prior to the calls.</FONT>=20
<BR><BR><FONT face=3Dsans-serif size=3D2>Have I got this straight? =
Do=20
we still think this is ok, given the emails of the last few days?=20
</FONT><BR><FONT face=3Dsans-serif size=3D2>This provides regular =
"reminders" of=20
issues (new and those to be covered with the full TC) which I think =
could be=20
structured to include a link to the issues list. This does =
involve email=20
to everyone on every new issue, and everyone will be copied on the =
replies to=20
those issues. Note, I've sent this to the issues/requirements =
process=20
team only - I'm preparing the note for the full TC that we discussed =
last=20
week. </FONT><BR><FONT face=3Dsans-serif size=3D2> </FONT> =
<BR><FONT=20
face=3Dsans-serif size=3D2>Regards, Diane<BR>IBM Dynamic =
e-business=20
Technologies<BR>drj@us.ibm.com<BR>(919)254-7221 or 8-444-7221, Mobile: =
919-624-5123</FONT></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C34193.2B24B500--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]