[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [members] OASIS member review of proposed revision of TC Process
In the proposed[1] revision[2], I find: TC Visibility All resources of the TC and its associated subcommittees, including web pages, documents, email lists and any other discussions, must be located only on facilities provided by OASIS; TCs and SCs may not conduct business or technical discussions, store documents, or host web pages on non-OASIS servers. By a strict interpretation of this clause, I am forbidden from mirroring the DocBook specifications and schemas on docbook.org. Is that the intent? Or is the intent merely that no TC content may appear solely on non-OASIS servers? Suppose a third party, unaffiliated with OASIS or the TC constructs such a mirror? Will OASIS pursue having those materials removed from the mirror? All web pages, documents, and email archives of all TCs and SCs shall be publicly visible. Mail Lists Each TC shall be provided upon formation with a general discussion email list and a means to collect public comments. Subscription to the general email list shall be required for Members, Voting Members, and Observers of the TC. The minutes of each TC meeting and a record of all decisions shall be published to that TC's email list. All communications and discussions of the TC must take place on the email list. All TC email lists shall be archived for the duration of the corporation, and all TC email archives shall be publicly visible. The purpose of the TC's public comment facility is to receive comments from the public and is not for public discussion. Comments will be publicly archived, and will be forwarded to one or more TC members including the TC Chair. TCs shall not be required to respond to comments. Comments to the TC made by TC members must be submitted via the TC email list, and comments made by non-TC members, including from the public, must be made via the TC's comment form. Are you saying that members of the public, subscribed to the docbook and docbook-apps lists may not make comments except via the TC's comment form? Is the TC forbidden from responding to comments made on those lists? Comments will not be accepted via any other means. What does that mean? If I bump into a DocBook user at a conference and that user describes a problem they are having, am I forbidden from raising that comment as an agenda item on some future meeting until such time as it's submitted by some official means? Are we foribidden from discussing TC work products with our friends and colleagues? Web Pages The OASIS TC Administrator shall provide the TC with a publicly accessible web page. Is this the Kavi page, or do you mean that the administrator now must provide a public web page for all TCs? The TC must keep the following information current on the TC web page: the TC name and charter; standing rules and other adopted procedures; meeting schedule; anticipated deliverables and delivery dates; list of TC members; the name and email address of the TC Chair or co-Chairs as well as other positions such as secretary, editor, etc. that may exist; list of subcommittees, their deliverables, and members; links to draft and completed TC documents with identification of the latest versions of the TC's specifications; and IPR declarations. Be seeing you, norm [1] http://lists.oasis-open.org/archives/members/200410/msg00004.html [2] http://www.oasis-open.org/apps/org/workgroup/members-only/download.php/9623/TC%20Process%2020041007.pdf -- Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc. NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]