cvs commit: src/sys/ufs/ufs ufs_acl.c

[Garrett Wollman]

[Moving this discussion to a more appropriate mailing-list.  Please Cc
me on any relevant replies.]

<<On Sat, 27 Oct 2001 16:59:51 -0400 (EDT), Robert Watson <rwatson at FreeBSD.org> said:

> Could you say a little more about any standards processes that might
> be accessible through or sponsored by USENIX, which I have had more
> dealings with in the past?

USENIX has a liaison, Nick Stoughton, who participates in the ANSI,
IEEE, and ISO standards processes and represents the interests of the
community on relevant standards committees.  He is well-up on the
process of bootstrapping the process, and when I spoke with him a year
ago at LISA he seemed willing to assist in negotiating the hurdles for
this particular effort.  USENIX has taken a particular interest in
ensuring that open-source operating systems have a seat at the table
when standards are created.  You'll need one person to volunteer as
document editor, and possibly another person to actually turn the
crank on the process (e.g., circulating drafts, calling for votes).

I felt that the Austin Group process, which was managed by The Open
Group, worked relatively well.  There were two mailing-lists, and the
document went through seven drafts.  At each circulation, the public
was invited to point out problems and inconsistencies in the current
draft, which were resolved in batches at regular physical meetings.
Each time around, the rules were tightened about what sort of changes
were in-scope.  By the time I started participating, new interfaces
were already out-of-scope, unless the omission was an oversight from
the merging of the original base documents.  (If you can get a
document through the process by 2005, then it will be in-scope for
1003.1-2006. :-)  The Austin Group was set up to create a revision of
POSIX that could serve simultaneously as an IEEE, ISO, and Open Group
standard.

> Also, we reached informal agreement that I would be the editor of a
> new "revision" to "POSIX.1e", attempting to capture our
> modifications, but I haven't had the opportunity to work on that as
> yet.

You probably *need* to do this under IEEE auspices for legal reasons,
since IEEE normally owns the copyright on the text.  IEEE also carries
liability insurance for approved standards activities.

-GAWollman

To Unsubscribe: send mail to majordomo at cyrus.watson.org
with "unsubscribe posix1e" in the body of the message