[Internal-cg] Fwd: Consensus call: Community comments handling

Thu Apr 16 00:14:35 UTC 2015

Thanks Joe...this makes sense to me.

- Keith Drazek

On Apr 16, 2015, at 12:10 AM, joseph alhadeff <joseph.alhadeff at oracle.com<mailto:joseph.alhadeff at oracle.com>> wrote:

Colleagues:

I think we are somewhat talking past each other.

We assemble the final proposal and do not draft the proposal parts.  If a proposal specific comment comes to us we have one action and 3 choices:

- The common action is to read what has been sent to us through some mechanism.  Not each person would need to read all messages or we may get them in digest form rather than real time or we may have a designated process of who reads what.  Para one of the text suggests that receipt of the comment be acknowledged.   That should not be very troubling.

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.

best-

Joe

On 4/15/2015 4:59 PM, Milton L Mueller wrote:
If the objection is to this:

ICG secretariat will acknowledge receipt through an automated receipt message that includes the steps ICG will follow to handle community comments directly submitted to its forum.

I really don’t see why there should be any controversy – from either side. It would be easy to just forward the comments, but even if the OC completely ignores the comments it gets or the ICG Forum, the ICG has the authority to agree to send questions to them based on its own reading of the comments.

So I don’t disagree with Kavouss, I don’t understand why we would not forward the comments, but it doesn’t really matter in my view.

--MM

From: Internal-cg [mailto:internal-cg-bounces at ianacg.org] On Behalf Of Alissa Cooper
Sent: Wednesday, April 15, 2015 3:48 PM
To: Kavouss Arasteh
Cc: internal-cg at ianacg.org<mailto:internal-cg at ianacg.org>
Subject: Re: [Internal-cg] Fwd: Consensus call: Community comments handling

Thanks Kavouss, your position is noted. Unless there are other objections that surface, I think we may have consensus with your position in the rough.

Alissa

On Apr 15, 2015, at 12:44 PM, Alissa Cooper <alissa at cooperw.in<mailto:alissa at cooperw.in>> wrote:

Begin forwarded message:

From: Kavouss Arasteh <kavouss.arasteh at gmail.com<mailto:kavouss.arasteh at gmail.com>>
Subject: Re: [Internal-cg] Consensus call: Community comments handling
Date: April 15, 2015 at 12:24:40 PM PDT
To: Alissa Cooper <alissa at cooperw.in<mailto:alissa at cooperw.in>>

Dear Alissa,
Thank you very much for the message.
I hope you are well and the baby also is well and does not cry frequently allows you to have some rest and deal with ICG which is is silent mode for mabny weeks.$
Comibng back to works
I strongly object to give such options to OC .
The first paragraph should be deleted
Delete

1.     Acknowledge – ICG Secretariat to Sender:

ICG secretariat will acknowledge receipt through an automated receipt message that includes the steps ICG will follow to handle community comments directly submitted to its forum.

1.     Forward – ICG to Operational Communities:Delete the first pasrt of the first line as shown

 ICG secretariat  (  replace the verb will with ) should   forward comments received to the relevant OC, ADD (  if so decideD by ICG, see below ,   , to be handled as if they were raised inside their process and inform the sender accordingly. ADD ( and copied to ICG)

ICG Internal Process:

As part of its ongoing proposal assessment process, the ICG will decide whether to direct any questions to the relevant operational community as a result of comments received and will consider responses received from the community during the assessment process.

1.     Alert – ICG Secretariat to ICG:

ICG secretariat will alert the ICG of any comments or input received on the ICG Forum<http://forum.icann.org/lists/icg-forum/>.

1.     Review – ICG Review Comments:

The ICG will review the comments received and may follow up with its own question(s) to the relevant OC, if the ICG deems necessary.

1.     Update – ICG Secretariat to ICG:

On periodic basis, ICG secretariat will create a summary digest of comments received.  The ICG requests that OCs, to whom the comments have been addressed, post any summary updates related to their responses or how they have dealt with the comments in general as they find appropriate.

Reasons

All decision should remain with ICG as responsible group for this process.OC is advised by ICG and not self selecting whether or not to react

Regards

Kavouss

2015-04-15 20:39 GMT+02:00 Alissa Cooper <alissa at cooperw.in<mailto:alissa at cooperw.in>>:
All,

We have had many rounds of discussion on the attached document <https://www.dropbox.com/s/r3vghlrn32ge8p4/Community%20Comments%20Handling%20-%2013Feb15.docx?dl=0> concerning community comments handling and I think we have consensus to publish it. Many thanks to Manal, Lynn, and everyone who worked on this. If there are any outstanding objections to publishing it, please send them to the list by April 20 at 20:00 UTC.

Thanks,
Alissa

_______________________________________________
Internal-cg mailing list
Internal-cg at mm.ianacg.org<mailto:Internal-cg at mm.ianacg.org>
http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org

_______________________________________________
Internal-cg mailing list
Internal-cg at mm.ianacg.org<mailto:Internal-cg at mm.ianacg.org>
http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org

_______________________________________________
Internal-cg mailing list
Internal-cg at mm.ianacg.org<mailto:Internal-cg at mm.ianacg.org>
http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org

_______________________________________________
Internal-cg mailing list
Internal-cg at mm.ianacg.org<mailto:Internal-cg at mm.ianacg.org>
http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20150416/87af37aa/attachment.html>