Hi Rusty,
Nope, not at all. It is in the queue - tickets https://tools.oasis-open.org/issues/browse/TCADMIN-1541 and https://tools.oasis-open.org/issues/browse/TCADMIN-1542 are tracking the work.
You're just in line behind an unusually long list of requests that we are crunching through as fast as we can. I expect to get started working on Virtio tomorrow or Thursday. If you all would like to have the first public review run a bit longer given the holiday impacts, just let me know. The 30 day is the minimum - we can always run it longer if you want.
Best,
/chet
On Mon, Dec 9, 2013 at 11:54 PM, Rusty Russell <> wrote:
Hi Paul, Chet,
I did this submission last week, the day after the meeting. Is
there anything else I need to do?
Cheers,
Rusty.
Paul Knight <> writes:
> Hi Michael,
>
> Waaay back at the beginning... the "transmittal message"...
> https://lists.oasis-open.org/archives/virtio/201311/msg00038.html
>
> .. had the basic info, below:
>
> [....] When the TC votes [5] to approve a Working Draft as a Committee
> Draft (CSD or CND), the Chair or other designated person must submit a
> "Committee Specification Draft Creation and Upload Request" accessible on
> the TC Administration Requests Page [6].
>
> [5] Approval of a WD as a CD (CSD or CND)
>
> https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft
> https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft
> [6] TC Administration Requests Page, see Committee Specification Draft
> Creation / Upload Request
> https://www.oasis-open.org/resources/tc-admin-requests
>
> Very briefly, ZIP up everything (one ZIP for csd01, one for csprd01) and
> load it to Kavi, and then have the TC vote to approve it. After that, fill
> out the forms in [6] and we'll get started on publishing it. By the TC
> Process, we can (if needed) adjust things on the front pages (through the
> TOC) after the TC approves it, but other changes are not allowed without
> re-approval.
>
> For the first publication using LaTeX, it's best to give us (Chet and me) a
> look before having the TC approve it.
>
> Best regards,
> Paul
>
>
>
> On Mon, Nov 25, 2013 at 2:05 PM, Michael S. Tsirkin <> wrote:
>
>> On Mon, Nov 25, 2013 at 12:43:39PM -0500, Paul Knight wrote:
>> > Hi Michael and all,
>> > Please see below..
>> >
>> > On Mon, Nov 25, 2013 at 12:13 PM, Michael S. Tsirkin <>
>> wrote:
>> >
>> > Some questions:
>> >
>> > I think we prefer the PDF version of the spec to
>> > be authoritative one and not the HTML one.
>> > Can we change the citation link to point to that?
>> >
>> > No, please don't... although the HTML may not be authoritative, we want
>> the
>> > citation link to point to HTML for easiest retrieval.
>>
>> Okay.
>> BTW in what way do we supply the files? Can chair just upload them?
>>
>>
>> > Please look at the
>> > "front pages" which I provided in the ZIP file, and you'll see that the
>> PDF
>> > format is already listed at the top under the "Specification URIs" as "
>> > (Authoritative)". As soon as someone retrieves the HTML, they will see
>> this,
>> > so they can get the PDF if desired. However, our approach is to
>> consider that
>> > many busy people just want to glance at the specification, and might be
>> > deterred by having to retrieve a PDF of unknown length.
>> >
>> > The "citation format" is intended to be included as a reference in some
>> other
>> > document, so we'd like people to be inclined to look at the OASIS
>> docs... Of
>> > course, if you are sending links to people, please feel free to send the
>> PDF
>> > link...
>> >
>> >
>> > I think we want to also mention the virtio-comment mailing
>> > list and not just the web form as a way to submit comments.
>> > Is that OK?
>> >
>> > I believe the link goes to the page
>> > (
>> http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=virtio)
>> > where they can first subscribe, then they can go to the comment page.
>> People
>> > can't comment until they subscribe. OASIS IPR rules require this...
>> (imagine
>> > a "patent troll" submits their patented idea as a nice addition to the
>> spec,
>> > then claims all kinds of damages, etc... the subscription process helps
>> > prevent this...) (very loooong story...)
>> > This is boilerplate info which we want to keep standard...
>> >
>> >
>> > Do we need to leave stubs for things we don't have?
>> > E.g.
>> > This specification is related to:
>> > Related speifications (list)
>> >
>> > can we just remove this until we have some related specifications?
>> >
>> > Yes, please remove any unwanted/unused sections completely (other than
>> the
>> > "Previous version").
>> >
>> > Hope that all makes sense...
>> >
>> > Best regards,
>> > Paul
>> > --
>> > Paul Knight - Tel: +1 781-861-1013
>> > OASIS - Advancing open standards for the information society
>> > Document Process Analyst
>> >
>>
>
>
>
> --
> Paul Knight <> - Tel: +1 781-861-1013
> OASIS <http://www.oasis-open.org/> - Advancing open standards for the
> information society
> Document Process Analyst<http://www.oasis-open.org/people/staff/paul-knight>
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
/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
