Hi Michael,
I'd like to know more about the appeal of
groups.io. I'm not sure what it offers that leads you to want to do this but I'd certainly like to find out how it might be of use.
However, I must warn you all - Jamie is cc'ed and can provide more background - that soliciting feedback to the TC from a non-OASIS-approved channel like
groups.io would violate the OASIS TC Process rules and quite possibly put your deliverables at risk. I understand that the subscribe requirement of virtio-comment@ is off-putting. We have heard the objection before. However, it is by the act of subscribing that your commenters contributions are bound to the TC's IPR mode and the OASIS copyright. By replying to the confirmation message, they make that commitment. By taking in feedback through a side-channel, you leave yourselves open to later claims against the work.
This is not hypothetical. While uncommon, we've had several incidents where TCs skirted these rules and OASIS received outside claims asserted against their work products. In one I was directly involved with, we had to take a work product down.
If you want a less top-heavy way for non-material feedback - typos or observations on how clear some text may be - the TC GitHub is certainly an option. You can offer people the option to open issues or add comments to issues there; that is one of its expected uses.
And again, we are happy to talk about the features of
groups.io that are appealing. On a quick scan, it does look like there are features there that I personally would find attractive.
Let me know if you'd like to further discuss.
Also, thanks for checking first. I really appreciate that.
Best,
/chet