std-unix@uunet.UU.NET (Moderator, John S. Quarterman) (01/12/88)
[The following was copied to std-unix in reply to a message of inquiry that went to another list. -mod] Thanks for the communication requesting information on how to participate in POSIX workshops.. Could I ask you instead to direct it to isaak@decvax.UUCP? Jim Isaaks is the chair of the POSIX working group, so should be able to tell you exactly what's happening. Alternatively, ahby@meccts.UUCP (Shane McCarron) is secretary to the group, so he may be able to help. In fact, a summary of germane information is posted periodically to the newsgroup comp.std.unix, which you can see if you're on the news network. Unfortunately, the last posting has expired, and we don't have a backup here -- except on paper, and I'm afraid I'm not going to type it in again... This invaluable information is posted by the moderator of the newsgroup, John S Quarterman, who can be reached at std-unix@uunet.uu.net. By copy of this mail, may I shall suggest that, in future, a long expiry date is put on the postings? Dominic Dunlop, R&D Director, Sphinx Ltd. Volume-Number: Volume 12, Number 29
jsq@longway.tic.com (John S. Quarterman) (01/15/88)
>Thanks for the communication requesting information on how to participate >in POSIX workshops.. A possible source of confusion is that there were two POSIX-related workshops last year, but none scheduled for this year, that I know of. The part of the POSIX committee that writes the standards is called the working group, and meets four times a year. >Could I ask you instead to direct it to isaak@decvax.UUCP? Also reachable as isaak@decvax.dec.com. > By copy of this mail, may I shall suggest that, in future, a long expiry > date is put on the postings? Good idea. I don't want it to be too long, because the information changes. But I will attempt to guess when I will next have an update ready, and put an expiration on it for that interval. The next posting of the access message follows in comp.std.unix. It includes the schedule for POSIX working group meetings. Volume-Number: Volume 12, Number 30