All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Cornelia Huck <cohuck@redhat.com>
Cc: virtio-dev@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [RFC PATCH  0/8] some tweaks to the document build process
Date: Fri, 27 Mar 2020 11:58:02 +0000	[thread overview]
Message-ID: <87pncym2lx.fsf@linaro.org> (raw)
In-Reply-To: <20200327115338.57a79ac4.cohuck@redhat.com>


Cornelia Huck <cohuck@redhat.com> writes:

> On Fri, 27 Mar 2020 10:37:55 +0000
> Alex Bennée <alex.bennee@linaro.org> wrote:
>
>> Hi,
>> 
>> I was reviewing someones virtio-spec and realised that I wasn't quite
>> sure what it had been built from. Seeing as the standard is hosted in
>> git I've tried to clean up some of the automation to make it clearer
>> what a particular rendering was built from. Going forward it would be
>> nice to use signed annotated tags for the final build version but I
>> don't know how much of the boilerplate is down to OASIS requirements.
>
> OASIS requirements are my concern here as well.

I've tried to do some digging although the Oasis website has a lot of
policy documents. I think the most relevant one is:

  https://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html

which as far as I can make out is mostly concerned that the final work
product meets the naming standard by version and stage. Although ZIP
files are mentioned a couple of times it is in the context of a file
containing work products for local use. My personal interpretation is
that if the final work products are correctly named and have the version
information in them the rest is just ephemera. However I could be wrong
so defer to anyone more familiar with the policies.

An random sampling of ZIP files on https://www.oasis-open.org/standards
has shown them all to just contain the individual work products without
any extraneous REVISION/REVISION-DATE files.

Anyway I defer to those with more experience of the process and I'll
leave the question of tex vs rst for another day ;-)

-- 
Alex Bennée

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/


  reply	other threads:[~2020-03-27 11:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 10:37 [virtio-comment] [RFC PATCH 0/8] some tweaks to the document build process Alex Bennée
2020-03-27 10:37 ` [virtio-comment] [RFC PATCH 1/8] README.md: convert html to proper Markdown format Alex Bennée
2020-04-30  7:39   ` [virtio-comment] Re: [virtio-dev] " Michael S. Tsirkin
2020-03-27 10:37 ` [virtio-comment] [RFC PATCH 2/8] CONTRIBUTING.md: convert to proper MarkDown Alex Bennée
2020-03-27 10:37 ` [virtio-comment] [RFC PATCH 3/8] LICENSE.md: convert html " Alex Bennée
2020-03-27 10:37 ` [virtio-comment] [RFC PATCH 4/8] makeall.sh: add explicit shebang to script Alex Bennée
2020-03-27 10:47   ` Cornelia Huck
2020-03-27 10:38 ` [virtio-comment] [RFC PATCH 5/8] Cleanup old changelog files Alex Bennée
2020-03-27 10:38 ` [virtio-comment] [RFC PATCH 6/8] Remove all mentioned of subversion Alex Bennée
2020-03-27 10:38 ` [virtio-comment] [RFC PATCH 7/8] make*: remove reliance on REVISION-DATE and use git Alex Bennée
2020-04-30  7:46   ` [virtio-comment] [mst@redhat.com: Re: [virtio-comment] [RFC PATCH 7/8] make*: remove reliance on REVISION-DATE and use git] Michael S. Tsirkin
2020-03-27 10:38 ` [virtio-comment] [RFC PATCH 8/8] Makefile: add simple make automation with clean target Alex Bennée
2020-04-30  7:50   ` Michael S. Tsirkin
2020-03-27 10:53 ` [virtio-comment] [RFC PATCH 0/8] some tweaks to the document build process Cornelia Huck
2020-03-27 11:58   ` Alex Bennée [this message]
2020-04-06 11:14 ` [virtio-comment] " Alex Bennée
  -- strict thread matches above, loose matches on Subject: below --
2020-03-24 18:28 [virtio-comment] " Alex Bennée
2020-03-24 17:54 Alex Bennée

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pncym2lx.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.