Re: [virtio-comment] can we do better than text?

["Michael S. Tsirkin" <mst@redhat.com>]

I'm just curious why did you move the discussion
to virtio@lists.oasis-open.org .

On Tue, Aug 27, 2013 at 08:46:46AM -0400, Chet Ensign wrote:
> Oh, and also ... "I think we prefer open lists
> for most discussions." 
> 
> Agree 100%. That is why every TC email list on OASIS is public. If you go to
> lists.oasis-open.org/archives, you'll see the entire collection and they are
> all publicly visible plus indexed on Markmail for searchability. 
> 
> /chet
> 
> On Mon, Aug 26, 2013 at 7:51 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> 
>     On Mon, Aug 26, 2013 at 05:16:50PM -0400, Chet Ensign wrote:
>     > Hi Michael, 
>     >
>     > Moving this off the -comment@ list to the main TC mailing list. 
> 
>     Hmm can we keep -comment Cc'd? I think we prefer open lists
>     for most discussions.
> 
>     > Several TCs are using DocBook XML to author their specs if you want to
>     look at
>     > that approach. And the CMIS TC used Tex to publish their specification
>     (see 
>     > http://docs.oasis-open.org/cmis/CMIS/v1.1/CMIS-v1.1.html). 
>     >
>     > /chet
>     >
>     >
>     > On Mon, Aug 26, 2013 at 4:56 PM, Michael S. Tsirkin <mst@redhat.com>
>     wrote:
>     >
>     >     I'm editing the spec in text format, and keeping numbering and
>     >     cross-references consistent is a huge pain.
>     >
>     >     for now I'm just avoiding any numbering changes
>     >     and adding cross-references, but I'm not sure we can
>     >     keep going like this.
>     >
>     >     Unless we want to go back to lyx, or latex, any
>     >     better ideas on how to do this?
>     >
>     >     This publicly archived list offers a means to provide input to the
>     >     OASIS Virtual I/O Device (VIRTIO) TC.
>     >
>     >     In order to verify user consent to the Feedback License terms and
>     >     to minimize spam in the list archive, subscription is required
>     >     before posting.
>     >
>     >     Subscribe: virtio-comment-subscribe@lists.oasis-open.org
>     >     Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
>     >     List help: virtio-comment-help@lists.oasis-open.org
>     >     List archive: https://lists.oasis-open.org/archives/virtio-comment/
>     >     Feedback License: https://www.oasis-open.org/who/ipr/
>     feedback_license.pdf
>     >     List Guidelines: https://www.oasis-open.org/policies-guidelines/
>     >     mailing-lists
>     >     Committee: https://www.oasis-open.org/committees/virtio/
>     >     Join OASIS: https://www.oasis-open.org/join/
>     >
>     >
>     >
>     >
>     >
>     > --
>     >
>     > /chet 
>     > ----------------
>     > Chet Ensign
>     > Director of Standards Development and TC Administration 
>     > OASIS: Advancing open standards for the information society
>     > http://www.oasis-open.org
>     >
>     > Primary: +1 973-996-2298
>     > Mobile: +1 201-341-1393 
>     >
>     > Check your work using the Support Request Submission Checklist at http://
>     > www.oasis-open.org/committees/download.php/47248/
>     > tc-admin-submission-checklist.html 
>     >
>     > TC Administration information and support is available at http://
>     > www.oasis-open.org/resources/tcadmin
>     >
>     > Follow OASIS on:
>     > LinkedIn:    http://linkd.in/OASISopen
>     > Twitter:        http://twitter.com/OASISopen
>     > Facebook:  http://facebook.com/oasis.open
> 
> 
> 
> 
> --
> 
> /chet 
> ----------------
> Chet Ensign
> Director of Standards Development and TC Administration 
> OASIS: Advancing open standards for the information society
> http://www.oasis-open.org
> 
> Primary: +1 973-996-2298
> Mobile: +1 201-341-1393 
> 
> Check your work using the Support Request Submission Checklist at http://
> www.oasis-open.org/committees/download.php/47248/
> tc-admin-submission-checklist.html 
> 
> TC Administration information and support is available at http://
> www.oasis-open.org/resources/tcadmin
> 
> Follow OASIS on:
> LinkedIn:    http://linkd.in/OASISopen
> Twitter:        http://twitter.com/OASISopen
> Facebook:  http://facebook.com/oasis.open