Also, the OASIS TC Process specifically says not to hold discussions on -comment@. It is hard to prevent it from happening occasionally. However, it looks like you all have lots to talk about which is why I am setting up a virtio-dev@ mailing list for the TC's use as well.
/chet
On Tue, Aug 27, 2013 at 6:45 AM, Rusty Russell <
> wrote:
"Michael S. Tsirkin" <
> writes:
> On Mon, Aug 26, 2013 at 05:16:50PM -0400, Chet Ensign wrote: >> Hi Michael, >> >> Moving this off the -comment@ list to the main TC mailing list. >
> Hmm can we keep -comment Cc'd? I think we prefer open lists
> for most discussions.
Chet pointed out that virtio-comment is really for public commentry on the spec, esp. when we release a public draft.
He suggested creating a virtio-dev (public posting a-la virtio-comment), which I think would work better for us. The bug-tracker is tied into virtio@, so anyone following will want to subscribe to both.
I've added this to the agenda...
Thanks, Rusty.
--
/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
