Ian, Adding to the list of requirements for issues tracking, we also need a way to: - capture the input date and source - assign a number, category, level of criticality, and status to each issue - capture / reference related discussion and resolution - establish guidelines to clearly identify emails as relevant to a particular issue (consistent format for subjects, not combining discussion of several issues in one email making threads difficult to follow, etc.) The w3c XMLP group issues list is well organized - maybe we could use some of their techniques:
http://www.w3.org/2000/xp/Group/xmlp-issues.html Colleen
ian.c.jones@bt.com wrote: > Ralph, > > thank you very much for offering to help. Yes, you are correct I > was trying to show the tasks that need to be done and someone need to do > them, the only formal title required is Chair, all the others are just tasks > that OASIS recommends are done. Several of the tasks are lightweight > (membership, web master) but when all added together the total is > significant. I also hoped that people would agree to take on a task even if > it was only for a fixed time say 3 months or until the next release. > > I can see no problem in rotating the minutes as long as they are in > a standard format, it has been suggested that the should in future be in > HTML, I think it is a good idea, but someone must write the template/pro > forma to be used. > > Once again thanks Ralph without you I do not know how we would have > continued. Now all we need is a simple process, standard comment form and > rules. Here are some (in no order) to start everyone thinking. > 1) The version being commented on must be stated e.g. Version 2 January 4 > 2002 > 2) The section number must be identified. > 3) The line number if used must be against the published PDF version. (We > must agree that a PDF version is posted to the website for this to work, it > avoids all the page/paper size and word/star office problems.) > 4) The context must be stated (esp. if the issue is grammar or clarification > of a point) > 5) A proposed change or replacement text must be included. > 6) It is the posters responsibility to ensure their comment/issue is in the > log. > 7) The log of issues will be updated at least weekly on the web site. > 8) All resolutions must be voted on in accordance with OASIS rules. > 9) if a solution is not suggested it MUST be raised on the list prior to > submission to the comments/issues process. > > Ian Jones > Chair OASIS ebXML Messaging Services TC > > Tel: +44 (0)29 2072 4063 > Fax: +44 (0)29 2072 4137 > Email:
ian.c.jones@bt.com > >