All,
Deadline for issues and PRs: Wednesday Feb 12 Discussion: Thursday Feb 13 RFC Target: Friday Feb 21
We want to publish the first draft of the virtio-msg changes to the virtio spec list as an RFC. We want to make sure:
1) It describes what we are doing 2) Is complete enough for virtio knowledgeable people to understand 3) _We_ don't need big changes*
* Reviewers may ask for big changes and we need to be prepared for that. But we need to have our thinking on the same page collectively as much as possible.
The work-in-progress spec is here: https://github.com/Linaro/virtio-msg-spec
The most recent rendered pdf is here: https://github.com/Linaro/virtio-msg-spec/releases
In addition there is pull request #5 that adds most of the things we spoke of in our Dublin sprint: https://github.com/Linaro/virtio-msg-spec/pull/5
All changes are in the file transport-msg.tex (There is one change to content.tex to include the new file)
Providing feedback:
Unlike the upstream spec, we can use github issues and github pull requests to manage changes within this group. Then one of us (myself or Bertrand most likely) will send to upstream virtio spec mailing list.
To provide your feedback please create an issue or a PR.
For small changes it is probibly easier to just create a PR with the exact wording you want. You can bundle a number commits into one PR but try to keep each commit to one topic or one section.
After the RFC most of the interaction will move to virtio-comment@lists.linux.dev so please subscribe now.
See the upstream README for details: https://github.com/oasis-tcs/virtio-spec/blob/master/README.md
Thanks, Bill