[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: groups.io mailing list
Do you mean this one:
Each TC shall be provided with a public comment facility, the purpose of
which is to receive comments from the public and is not for general
discussion. Comments shall be publicly archived and must be considered
by the TC.. TCs are not required to respond to comments. Comments to the
TC made by non-TC Members, including from the public, must be made via
the TC's comment facility, and shall not be accepted via any other
means.
as well as the virtio-comment web form
Unfortunately typos isn't the big issue. The issue is ability to CC a
virtio list on technical discussions that take place on other forums,
such as hypervisor or emulator lists.
An ideal contribution flow would be for contributor to send mail to list
and to get back a link to agree to IPR rules, contributor clicks it,
contribution gets forwarded.
The flexible moderation is mostly what I was looking at, but a working
search is also a big plus: right now finding a message in an archive is
a manual process. Archiving of attachments is also nice since some
people edit the PDF and send comments this way.
> On Thu, May 31, 2018 at 5:03 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
>
> Hello!
> After much consideration, I'm seriously thinking about creating
> an groups.io mailing list for the virtio TC feedback.
>
> The main issue I'm trying to address is the subscriber-only nature of
> the list which is a big problem for casual commenters: when one sends
> email to the list, message is bounced back. One has to subscribe
> and resend.
>
> groups.io seems to handle this in a more reasonable way.
>
> But API access with things like tags allowing better automation
> with e.g. the voting process would also be welcome.
>
> --
> MST
>
>
>
>
> --
>
> /chet
> ----------------
>
> Looking forward to Borderless Cyber 2018, 3-5 Oct, Washington, D.C.
> Organized by The World Bank, OASIS, and Georgetown University
>
> Chet Ensign
> Chief Technical Community Steward
> OASIS: Advancing open standards for the information society
> http://www.oasis-open.org
>
> Primary: +1 973-996-2298
> Mobile: +1 201-341-1393
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]