Minutes of the 14th October 2019 Teleconference     Austin-976 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 15th October 2019

Attendees:
    Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
    Andrew Josey, The Open Group
    Don Cragun, IEEE PASC OR
    Geoff Clare, The Open Group
    Joerg Schilling, FOKUS Fraunhofer
    Eric Blake, Red Hat, Open Group OR
    Mark Ziegast, SHware Systems Dev.

* General news 
Andrew reported that the project to move the document sources to
gitlab with support for building inside a docker container was
now completed. We will demo the system on the next call.

* Outstanding actions

(Please note that this section has been flushed to shorten the minutes -
to locate the previous set of outstanding actions, look to the minutes
from 13th June 2019 and earlier)

Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR list" OPEN
http://austingroupbugs.net/view.php?id=1254
Action: Joerg to investigate how his shell behaves.

Bug 700 - Nick to raise this issue with the C committee
Bug 713 - Nick to raise with the C committee.
Bug 739 - Nick to raise with the C committee.
Bug 1216 - Eric to ask if The Open Group is willing to sponsor this interface, referencing bug note 4478.


* Current Business


Bug 1292: Add pthread_setname, pthread_getname        Rejected
http://austingroupbugs.net/view.php?id=1292

This was discussed on the 2019-10-14 call. The sentiment was that within the
confines of a single process, thread local storage already exists as a portable
way to get the same effect. Outside of a single process, accessing the ID or
name of a thread (or for that matter, any other details), is already an
implementation-specific extension; we would feel more comfortable first
standardizing a way for the ps utility to output thread-specific information
before adding a pthread_setname() that would affect ps output in a way that
makes sense, but altering ps is a much more complex task. Thus, at this time,
this proposal is being rejected, although implementations should still feel
free to provide it as an extension.

We also note that some implementations limit the string to 16 bytes, some to
32-bytes, and some to 2048 bytes. Some implementations truncate longer
strings, some error on overlong strings, while others do not specify what
happens with longer strings. And, since truncation could result in a split on
a non-character boundary, we are even less inclined to accept this function
without a clear specification on what a function to add a thread name should
do if the given string is too long.


Next Steps 
----------
The next calls are on:


October 17 2019 (Thursday)
This call will be for 90 minutes.

October 21 2019 (Monday)
This call will be for 60 minutes.

Apologies in advance:
    Nick Stoughton, 2019-10-21, 2019-10-24

Calls are anchored on US time. (8am Pacific) 

Please check the calendar invites for dial in details.
http://austingroupbugs.net

An etherpad is usually up for the meeting, with a URL using the date format as below:

https://posix.rhansen.org/p/201x-mm-dd
username=posix password=2115756#