[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [business-transaction] BTP issues list
Peter - It's useful to have several issues lists; you've started one for technical open issues. I suggest at least one other, for "document issues," which would reflect structure, expression, and content issues as raised. bill cox Peter Furniss wrote: > I've set up a start of an issues list on the Choreology website. Modelled > approximately on the OMG issues lists, with a few starter issues we've > noticed in 0.9, it's at http://www.choreology.com/~btp/issues.html > > As spec co-chair, I'm offering to maintain this list, and especially to > assign the numbers so there is an single sequence. Proposed procedure is : > > anyone with a new issue sends to me. I give it a number, mangle text to > html, add to list and announce it on the bt-spec mailing list, with the > issue number in the subject field. I will then add a link from the web-page > to that announcement message in the mail archive on the oasis server. > > comment on the issue, if sent in reply to the announcement or replies to > that (etc) will be traversable as a thread on the oasis server. > > At an appropriate stage (which might be initial submission, or when someone > produces the text) I'll add a proposed solution entry, and when this is > approved by the committee, the resolution. > > I should be able to cope with a modicum of variant behaviour (e.g. issues > that get chased around on the list before they are identified as such, > issues that split, issues where the discussion ends up on the main list), > but the closer we stick to the pattern, the easier it should be. I'm working > on some scripts to make the maintenance easy (and thus quick). It should > work just to send issues direct to me - I should be able to get them up and > announced quickly most of the time (but remember I'm on GMT, so it will be > next-day for an issue from California). Obviously people can cc: the list > directly if they want, but that won't have the issue number in the subject. > > If this is acceptable (i.e. is approved at today's call), I'll send out the > announcements for those starter issues and get it going. > > Peter > > ------------------------------------------ > Peter Furniss > Technical Director, Choreology Ltd > web: http://www.choreology.com > email: peter.furniss@choreology.com > phone: +44 20 7670 1679 > direct: +44 20 7670 1783 > mobile: 07951 536168 > 13 Austin Friars, London EC2N 2JX > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl>
begin:vcard n:Cox;William tel;cell:+1 908 385 7855 tel;fax:+1 908 580 3060 tel;work:+1 908 580 3458 x-mozilla-html:FALSE url:http://www.bea.com/ org:BEA Systems, Inc.;Architecture and Standards adr:;;140 Allen Rd;Liberty Corner;NJ;07938;USA version:2.1 email;internet:William.Cox@bea.com title:Technical Director fn:William Cox end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC