ICANN ICANN Email List Archives

[gnso-igo-ingo]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [gnso-igo-ingo] IGO-INGO Final Report v1.7.1

  • To: <gnso-igo-ingo@xxxxxxxxx>
  • Subject: RE: [gnso-igo-ingo] IGO-INGO Final Report v1.7.1
  • From: "Berry Cobb" <mail@xxxxxxxxxxxxx>
  • Date: Sat, 9 Nov 2013 09:34:20 -0700

Chuck,

 

Thank you for catching the errors.  The extra eyes are a necessity.  I made
the updates to the master version of the report.  We've also forwarded your
suggestion internally to have the developer of the attendance tool evaluate
you suggestion.

 

Thank you again, and see you next week.

 

B

 

Berry Cobb

Internet Corporation for Assigned Names & Numbers (ICANN)

720.839.5735

 <mailto:mail@xxxxxxxxxxxxx> mail@xxxxxxxxxxxxx

@berrycobb

 

 

From: Gomes, Chuck [mailto:cgomes@xxxxxxxxxxxx] 
Sent: Saturday, November 09, 2013 08:12
To: Berry Cobb; gnso-igo-ingo@xxxxxxxxx
Subject: RE: [gnso-igo-ingo] IGO-INGO Final Report v1.7.1

 

Berry,

 

On page 10 of the redline document under Minority Statements, I note that
only the RCRC statement is shown.  I think that that is supposed to be a
reference to the general supplemental document A instead of the RCRC
statement.  That correction was made on page 3 but not on page 10.

 

In footnote 27, it would be helpful, although not essential, to name the
Supplement, i.e., something like this:  " . . . see the IGO's Minority
Statement in the Minority Positions supplement, Supplement A."

 

I also found on page 65 that the link to the attendance record requires
login to Confluence.  That was no problem for me but might be for those who
have not yet created a login ID & password.  On a totally different point
for GNSO consideration, not for this report, I think it would be good if
staff made the following improvement in attendance record reporting:  In the
group summaries, add boxes for total meetings, # in which the group was
represented by at least one person & the %.  The percent of total meeting
opportunities attended is very misleading;  for example, the report shows
that the RrSG a meeting opportunity attendance rate of 34% while the RySG 's
was 32% and the NCSG was 18%.  The numbers are heavily skewed by the number
of participants in a group as well as the number of individuals in a group
that missed a lot of meetings.  As everyone knows and as the data shows, the
RySG and NCSG (as well as other groups) had representation in a very high
percentage of the meetings while the RrSG was represented in a very low
percentage of the meetings.  Again, this is not something for this report
but a proposed improvement in reporting attendance in the future.  (BTW, the
link to the email archives does not require login to Confluence, so it
worked as expected.)  - Note that if fixing the link is not an easy task, it
should not delay submitting the report.

 

Everything else looks fine to me.

 

Chuck

 

From: owner-gnso-igo-ingo@xxxxxxxxx [mailto:owner-gnso-igo-ingo@xxxxxxxxx]
On Behalf Of Berry Cobb
Sent: Friday, November 08, 2013 7:30 PM
To: gnso-igo-ingo@xxxxxxxxx
Subject: [gnso-igo-ingo] IGO-INGO Final Report v1.7.1

 

WG Members,

 

Please find attached the latest version of the Final Report and its
supplements.  For this version, I accepted all the prior changes.  I'm
awaiting input from the GCO about the two issues we discussed in today's
call regarding the principles of implementation.

 

I ask members to review the latest draft closely and provide any additional
feedback noting of any errors in reference or other small content changes to
correct grammar or reduce confusion.

 

I will accept any suggested revisions until 9 Nov 2013 @ 23:59.  If no
objections are made, I will update the master version and prepare the final
draft.  I intend to send the report and supplements, along with a cover note
to the GNSO Council on 9 Nov 2013 @ 16:00 UTC. 

 

Thank you for everyone's contribution and I look forward to seeing many of
you in BA.

 

Thank you.  B

 

Berry Cobb

Internet Corporation for Assigned Names & Numbers (ICANN)

720.839.5735

mail@xxxxxxxxxxxxx

@berrycobb

 

 



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy