Re: [tcproc-member-review] Comments on new TC process

[Michael Smith <smith@xml-doc.org>]

"Cruikshank, David W" <david.w.cruikshank@boeing.com> writes:

[...]

> Regarding the following paragraph:
> 
> 367 All resources of the TC and its associated subcommittees, including web pages, 
> 368 documents, email lists and any other discussions, must be located only on facilities 
> 369 provided by OASIS; TCs and SCs may not conduct business or technical discussions, 
> 370 store documents, or host web pages on non-OASIS servers. All web pages, documents, 
> 371 and email archives of all TCs and SCs shall be publicly visible. 
> 
> While I agree that all TC activities should be visible from the
> OASIS server environment, I strongly disagree that all
> information must be physically stored there.  In some cases a TC
> uses tools that rely on facilities that are not available on the
> OASIS servers.  I think the restriction should be that all TC
> materials must be "publicly visible" from OASIS server pages.

"Publicly visible from the OASIS site" seems like reasonable
language to me.

In the case of the DocBook TC, we use an external tool for
tracking Requests for Enhancements (RFEs). It works well, but I'm
sure the TC would be happy to consider instead using a tool
provided by OASIS, were one available. We also use an external CVS
repository for version control of the DocBook schemas. An OASIS
official CVS repository could be set up very easily, and that
content could be moved over (CVS is CVS...).

smime.p7s