[Internal-cg] Consensus call: Community comments handling

Patrik Fältström paf at frobbit.se
Thu Apr 16 06:16:32 UTC 2015

> On 16 apr 2015, at 00:09, joseph alhadeff <joseph.alhadeff at oracle.com> wrote:
> Choices:
> a.  We decide that the comment we received is worthy of our own follow up and it inspires us to ask the same or related question(s) to the proposal drafters. This we have the ability to do at all times.
> b.  As the comment goes to a proposal as opposed to our process or the joint proposal, we are not in a position to properly answer the question.  As such we could forward the question to the correct community, on the chance that the asker of the question may not have also addressed the community.
> c.  Since we are working transparently, I assume all of the questions we receive will be available online.  If a community commits to keeping watch for relevant comments then we don't have to worry about forwarding comments.
> Options b and c in no way limit our rights and abilities under a.  b and c are merely concepts that assure the greatest transparency and assurance that comments are routed to those groups best able to address them.  It takes a no wrong door approach to comments and helps assure that those not familiar with the consultation process are also able to get their questions heard.

We also have d. various trolls and denial of service attacks that we can at point of inspection "just ignore". Specifically because of b. and c. And b. issues might be picked up by the OC themselves. Either because it was adressed to them as well as ICG, or because they saw it (according to c.).

I.e. we are inspired by whatever comments come in, and might ask/forward questions to the OC's. OC's can also watch the list and act themselves on whatever is sent in.

But I do not see us or OC be required to act on _every_ comment coming in. Specifically not having ICG send _every_ comment to the OC's for action.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20150416/10393af8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20150416/10393af8/attachment.asc>

More information about the Internal-cg mailing list