[PATCH v3 00/18] admin: reconfirming the TC charter

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

As previously reported
https://lists.oasis-open.org/archives/virtio/202101/msg00000.html
the latest revisions to the TC Process and the OASIS
Committee Operations Process include new requirements to periodically confirm
the TC charter and appoint or reappoint the TC chair(s).

Our current charter can be found here:
https://www.oasis-open.org/committees/virtio/charter.php

Also included as patch 1 in the series.
Some of it is a bit out of date. E.g. it talks of 1.0 in a future
tense. There is nothing major though.

I therefore propose the following clarifications to the charter.
I did my best to address previous comments by Cornelia.

As the only change here is a minor comment by Halil, I am going to go on
and start the process for the TC charter clarification (Section 1.8).

changes from v2:
	address a comment by Halil to patch 06/17: ("charter: drop attempts to list all devices")
changes from v1:
	address comments by Cornelia


Michael S. Tsirkin (18):
  import the current TC charter
  charter: update historical notes
  charter: 1.0 is history
  charter: mention 1.x series in the background section
  charter: add channel I/O to list
  charter: drop attempts to list all devices
  charter: reserved id/feature list has nothing to do with 2.0
  charter: explain what legacy is in the background section
  charter: update on deliverables
  charter: add motivation for changes made since 1.0
  charter: update to mention 1.X instead of 0.9, 2.0
  charter: document our focus on compatibility
  charter: TC as registrar for device IDs/features
  chater: document what we care about in changes
  charter: driver/device terminology
  charter: legacy mode terminology
  charter: audience terminology
  charter: rearrange the deliverables section

 charter.html | 152 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 152 insertions(+)
 create mode 100644 charter.html

-- 
MST