Minutes of the 20 November 2008 Teleconference Austin-444 Page 1 of 1 Submitted by Andrew Josey, The Open Group. November 21 , 2008 Attendees Andrew Josey, The Open Group Don Cragun , Sun, PASC OR Mark Brown, IBM, TOG OR Nick Stoughton, USENIX, ISO/IEC OR Mats Wichman , Intel Geoff Clare, The Open Group Apologies Ulrich Drepper, Red Hat * Draft Status The pdf draft is finished pending final comments from IEEE on the frontmatter. Primarily the comments to date have been related to adding the TM symbol to various IEEE standard designations. We are aiming for a December 1st publication by IEEE and The Open Group. The html version of the specification is now in active development. We hope to have a beta version available for December 1st for a preview. * Aardvark We picked up on the aardvark reports, which are located at http://www.opengroup.org/austin/aardvark/latest/ * D5.1R aardvarks We had a discussion about Aardvark, and possible thoughts on a move to Bugzilla. We agreed that its now a quiet period in the development cycle so we could trial it in parallel for a while. We would need to clearly define the requirements. Andrew will talk internally at The Open Group regarding what infrastructure we have in place that we might be able to use. We had a discussion on requirements for aardvark processing: We need fields in the database for all the items we have in the current aardvark, page, line number, section, categorization, reference etc also a URL reference (for those entering against the online specification, for these we would need to be able to update the data to add the official pdf page and line numbers) We'd like to investigate both import and export to bugzilla, to generate similar reports to todays documents, by page and line number. Access control needs to be considered, who can change a bugs status Anyone can submit a bug, anyone can view status, anyone add a comment. Core team to resolve. We had some discussion about where email should go. We do not want every state change generating email and do not wish to add to the email burden. We'd need to adopt a way of working, whether discussions be on the reflector or in the bugzilla. Mark agreed to investigate bugzilla further and report back at the next meeting. xshbug3.txt ERN 13 Accept as marked below In sigwait() RATIONALE > == > After some consideration, threads were allowed to use semaphores > and sem_post() was defined to be async-signal and async-cancel-safe. > == Remove " and async-cancel", so that the resulting text ends up with: "...was defined to be async-signal-safe." This problem seems to date back to the original .1c threads standard. At least, the same rationale appears in POSIX.1-1996 in section B.11.4.3 (Page 527 Line 6994). > And again there seems to be contradictory text in XRAT lines 118498 to > 118499: > > == > IEEE Std 1003.1-2001/Cor 1-2002, item XSH/TC1/D6/6 is applied, adding the > abort() function to the list of async-cancel-safe functions > == Change async-cancel-safe functions to async-signal-safe functions to This one is a mistake in the wording of 1003.1-2001/Cor 1-2002, item XSH/TC1/D6/6. It added abort() to the table of async-signal-safe functions in 2.4.3, but somehow the word "cancel" got into the description of the change instead of "signal". Next meeting ------------ The next call will be on either Jan 8/15th at 16:00 UK time to carry on with the aardvark. (Andrew will check the proposed date with Ulrich first) See the calendar for the extensive list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freestandards.org #austin ICAL: http://www.google.com/calendar/ical/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic XML: http://www.google.com/calendar/feeds/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic