Draft

Minutes of CGM Open Telecon/WebEX - 30 April 2003

Participants

Dave Cruikshank, Boeing
Stuart Galt, Boeing (with Dave)
Forrest Carpenter, SDI
Franck Duluc, Airbus
Dieter Weidenbruck, ITEDO
Lofton Henderson, Program Director
Beniot Bezaire, Corel
John Gebhardt, Corel
Andrew Moorhouse, Mod UK

Meeting Arrangements

• The telecon was hosted by Dave and the WebEX meeting was hosted by Franck

Agenda/Discussion

Public Interface for Problem Tracking S/W

• The public interface discussion centered around requirements of fields that need to be captured when a user reports a interoperability problem
  • Tool version
    This will probably be a field that is entered by hand and is not required
  • Platform
    When the user selects the platform is probably should be from a list (e.g. PC, unix). Identifying the actual unix platform (Sun, HP, SGI, etc.) should probably be captured in the problem description field as free text.
  • Operating system
    The user should pick from a list or have the option of entering free form text into the form. The list should include entries like: Windows 95, Windows 98, Windows 2000, XP, unix, etc.)
  • Keywords
    The field should probably be renamed categories and the user presented with a list of standard types of error categories (e.g. text, curve, attributes, raster, printing, viewing, etc.). This user will have to select the one that closest matches his problem.
  • File uploads
    There needs to be a facility for uploading files through the user interface so the user can provide samples to demonstrate the problem. Size of these uploads need to be a consideration and guidelines need to be noted on the upload function.
• In order to fulfill the notification function, the interface needs to capture an email address for the user. That email address should be associated with the bug and a profile generated that indicates that updates to the bug status generate a notification to the user who reported it.
• On the page that is the public interface there needs to be a method of contacting the administrator (webmaster?). This should be an email link.
• A disclaimer needs to be added to the "tool" area that CGM Open limits its responsibility for timely action in the case of problems reported concerning tools that are not products of CGM Open members.
• Dave proposed a phased implementation plan for introducing the problem tracker.
  1. Make it available to the CGM Open membership list only for a period of time.
  2. Announce its availability to the CGM Open mailing list and at the same time put a link to it on the home page of CGM Open
  3. Announce its availability through the oasis-announce mailing list
  4. Announce its availability through various conference and industry forums

Product Web Site

• By the deadline for submitting links to proformas, there were two still outstanding. Lofton will be unable to start working on this until May 9th at the earliest, so the vendors have a two-week reprieve. If the links are not provided to filled out proformas by the time Lofton submits them to the OASIS webmaster, the vendor products that have not submitted will be removed from the site until the next opportunity.
• In case of technical misstatements in the proformas or violations of standard conventions, Lofton will act as the temporary arbiter for resolution.

Next Meeting

• No decision was made on this. Dave will circulate a proposal for a potential meeting some where around the date of June 11th. Also, a proposal will be circulated for a standard monthly time for CGM Open telecons, so we can get them on everyone's calendar.