Re: [gnso-osc-csg] Actions/Summary: 26 March 2010 Meeting - Open meetings discussion

[Rafik Dammak <rafik.dammak@xxxxxxxxx>]

hi Robert,

Thank you for your remind, can you please give more details about this:
"That last area is a topic that Glen, Julie and I are currently studying in
the context of the “toolkit” of Constituency and Stakeholder Group services
that the Council approved in December."
can we expect outcome soon?

Regards

Rafik

2010/4/2 Robert Hoggarth <robert.hoggarth@xxxxxxxxx>

>  Dear All;
>
> Via email or during the next call, Olga, Chuck or Rafik may like to share
> some of the discussions that took place regarding “open” meetings during the
> GNSO Council operations procedures deliberations.  I think the meeting
> matters raised in those discussions are germane to the challenge of how to
> ensure that other organizational meeting are also open and transparent.
>
> I recall the Council discussion addressed community expectations for
> addressing both transparency goals and management of organizational
> resources.  As I recall, the consensus expectation was that ALL Council
> meeting matters and discussions needed to be available to the broader
> community but that electronic real-time attendance created logistical and
> resource issues that needed to be considered (e.g., the costs and logistics
> of having “open” meeting attendance during telephonic meetings).  As a
> result, the procedures approved by the Council in Seoul distinguish
> in-person meetings from other types of Council meetings (e.g., telephonic
> ones) (see Section 3 of the GNSO Council Operating procedures -
> http://gnso.icann.org/meetings/gnso-operating-procedures-clean-12nov09-en.pdf).
>
>
> I believe the general consensus that resulted in the current procedures was
> that so long that agendas were produced in advance of meetings (notice of
> subject matter to be discussed) and that transcripts, or minutes or
> recordings of calls were subsequently produced for community review then the
> letter and spirit of “openness” was preserved.
>
> As additional technological resources become available, this “electronic”
> attendance matter may need to be revisited.  For example, some of the remote
> participation tools we used in Nairobi (chat rooms, virtual Adobe Connect
> meeting rooms, etc.) could be extended over time.  Of course the
> introduction of those resources depends on the availability of
> organizational resources (e.g., costs and staff management/secretariat
> availability). That last area is a topic that Glen, Julie and I are
> currently studying in the context of the “toolkit” of Constituency and
> Stakeholder Group services that the Council approved in December.
>
> Hope this helps the conversation.
>
> RobH
>
>
> On 4/1/10 11:18 AM, "Papac, Krista" <Krista.Papac@xxxxxxxxxxxxxxxx> wrote:
>
> Thanks Chuck.  I hope we can discuss further on our next call.
>
>
> Krista Papac
> Iron Mountain Digital
> 5530 Bandini Blvd
> Bell, CA  90201  US
> Home Office: +1.714.846.8780
> Mobile: +1.714.865.7655
> Fax: +1.323.443.3573
> krista.papac@xxxxxxxxxxxxxxxx 
> <mailto:krista.papac@xxxxxxxxxxxxxxxx<krista.papac@xxxxxxxxxxxxxxxx>>
>
>
> *“Software Escrow for Dummies” - order your complimentary copy t*oday at <
> http://www.ironmountain.com/escrowfordummies>
> www.ironmountain.com/escrowfordummies <
> http://www.ironmountain.com/escrowfordummies>
>
> *New Gartner Report: Successful Software Escrow Requires Planning and
> Negotiation
> *Gartner advises: “It is also important that the licensee continue to
> track the software vendor’s financials and viability annually, because any
> signs of financial problems would justify the cost of verification
> services.” Continue reading the full report at:
> http://www.gartner.com/technology/media-products/reprints/ironmountain/170569.html<
> http://www.gartner.com/technology/media-products/reprints/ironmountain/170569.html>
>
>
>   ------------------------------
>
> *From:* Gomes, Chuck [mailto:cgomes@xxxxxxxxxxxx <cgomes@xxxxxxxxxxxx>]
> *Sent:* Thursday, April 01, 2010 7:55 AM
> *To:* Papac, Krista; Victoria McEvedy; Rafik Dammak; Julie Hedlund
> *Cc:* gnso-osc-csg
> *Subject:* RE: [gnso-osc-csg] Actions/Summary: 26 March 2010 Meeting
>
> Krista,
>
> My understanding was that it meant all types of GNSO meetings including SG,
> Constituency and Interest Group policy meetings.
>
> Chuck
>
>  ------------------------------
>
>
> *From:* Papac, Krista 
> [mailto:Krista.Papac@xxxxxxxxxxxxxxxx<Krista.Papac@xxxxxxxxxxxxxxxx>]
>
> *Sent:* Thursday, April 01, 2010 10:50 AM
> *To:* Gomes, Chuck; Victoria McEvedy; Rafik Dammak; Julie Hedlund
> *Cc:* gnso-osc-csg
> *Subject:* RE: [gnso-osc-csg] Actions/Summary: 26 March 2010 Meeting
> Thanks for the clarification Chuck. I think I must have misunderstood the
> recommendation.  I didn’t realize it was related to GNSO meetings, but was
> thinking it was related to stakeholder group, constituency, and interest
> group policy meetings.  By way of example, I thought the recommendation was
> saying that the RrSG would have to open it’s discussions on policy (or
> policy meetings) to the public, but from your response I can see I
> misunderstood.
>
> Thanks!
> Krista
>
> Krista Papac
> Iron Mountain Digital
> 5530 Bandini Blvd
> Bell, CA 90201  US
> Home Office: +1.714.846.8780
> Mobile: +1.714.865.7655
> Fax: +1.323.443.3573
> krista.papac@xxxxxxxxxxxxxxxx 
> <mailto:krista.papac@xxxxxxxxxxxxxxxx<krista.papac@xxxxxxxxxxxxxxxx>>
>
>
> *“Software Escrow for Dummies” - order your complimentary copy t*oday at <
> http://www.ironmountain.com/escrowfordummies>
> www.ironmountain.com/escrowfordummies <
> http://www.ironmountain.com/escrowfordummies>
>
> *New Gartner Report: Successful Software Escrow Requires Planning and
> Negotiation
> *Gartner advises: “It is also important that the licensee continue to
> track the software vendor’s financials and viability annually, because any
> signs of financial problems would justify the cost of verification
> services.” Continue reading the full report at:
> http://www.gartner.com/technology/media-products/reprints/ironmountain/170569.html<
> http://www.gartner.com/technology/media-products/reprints/ironmountain/170569.html>
>
>
>   ------------------------------
>
> *From:* Gomes, Chuck [mailto:cgomes@xxxxxxxxxxxx <cgomes@xxxxxxxxxxxx>]
> *Sent:* Thursday, April 01, 2010 7:41 AM
> *To:* Papac, Krista; Victoria McEvedy; Rafik Dammak; Julie Hedlund
> *Cc:* gnso-osc-csg
> *Subject:* RE: [gnso-osc-csg] Actions/Summary: 26 March 2010 Meeting
>
> It's a good question Krista.  With regard to policy working sessions that
> occur during ICANN international meetings, the GNSO has a practice of making
> those meetings open to the public on a space available basis except when
> otherwise stated.  For teleconference meetings, the call info is usually
> restricted to identified members or invited guests.
>
> Chuck
>
>  ------------------------------
>
>
> *From:* owner-gnso-osc-csg@xxxxxxxxx 
> [mailto:owner-gnso-osc-csg@xxxxxxxxx<owner-gnso-osc-csg@xxxxxxxxx>]
> *On Behalf Of *Papac, Krista
> *Sent:* Wednesday, March 31, 2010 9:32 AM
> *To:* Victoria McEvedy; Rafik Dammak; Julie Hedlund
> *Cc:* gnso-osc-csg
> *Subject:* RE: [gnso-osc-csg] Actions/Summary: 26 March 2010 Meeting
> Team,
>
> Can someone explain to me why {GROUPs} would want to open their Policy
> Committee Meetings to the public?
>
>
> Krista Papac
> Iron Mountain Digital
> 5530 Bandini Blvd
> Bell, CA 90201  US
> Home Office: +1.714.846.8780
> Mobile: +1.714.865.7655
> Fax: +1.323.443.3573
> krista.papac@xxxxxxxxxxxxxxxx 
> <mailto:krista.papac@xxxxxxxxxxxxxxxx<krista.papac@xxxxxxxxxxxxxxxx>>
>
>
> *“Software Escrow for Dummies” - order your complimentary copy t*oday at <
> http://www.ironmountain.com/escrowfordummies>
> www.ironmountain.com/escrowfordummies <
> http://www.ironmountain.com/escrowfordummies>
>
> *New Gartner Report: Successful Software Escrow Requires Planning and
> Negotiation
> *Gartner advises: “It is also important that the licensee continue to
> track the software vendor’s financials and viability annually, because any
> signs of financial problems would justify the cost of verification
> services.” Continue reading the full report at:
> http://www.gartner.com/technology/media-products/reprints/ironmountain/170569.html<
> http://www.gartner.com/technology/media-products/reprints/ironmountain/170569.html>
>
>
>   ------------------------------
>
> *From:* owner-gnso-osc-csg@xxxxxxxxx 
> [mailto:owner-gnso-osc-csg@xxxxxxxxx<owner-gnso-osc-csg@xxxxxxxxx>]
> *On Behalf Of *Victoria McEvedy
> *Sent:* Wednesday, March 31, 2010 4:02 AM
> *To:* Rafik Dammak; Julie Hedlund
> *Cc:* gnso-osc-csg
> *Subject:* RE: [gnso-osc-csg] Actions/Summary: 26 March 2010 Meeting
>
> I think Mary’s suggestions are excellent and I support either version. My
> view is these committees ---where all the crucial work of the Groups is done
> –most definitely need transparency, term limits and openness, real rotation
> of members and leaders as well as disclosure of work and work product –at
> least within the Group.  This is not currently happening in some Groups and
> goes to the very heart of all reforms.
>
> Best regards,
>
>
> Victoria McEvedy
> Principal
> McEvedys
> *Solicitors** and Attorneys
> *
>
> 96 Westbourne Park Road
> London
> W2 5PL
>
> T:   +44 (0) 207 243 6122
> F:   +44 (0) 207 022 1721
> M:  +44 (0) 7990 625 169
> *
> www.mcevedy.eu
> *Regulated by the Solicitors Regulation Authority #465972
> This email and its attachments are confidential and intended for the
> exclusive use of the addressee(s).  This email and its attachments may also
> be legally privileged. If you have received this in error, please let us
> know by reply immediately and destroy the email and its attachments without
> reading, copying or forwarding the contents.
> This email does not create a solicitor-client relationship and no retainer
> is created by this email communication.
>
>
> *From:* owner-gnso-osc-csg@xxxxxxxxx 
> [mailto:owner-gnso-osc-csg@xxxxxxxxx<owner-gnso-osc-csg@xxxxxxxxx>]
> *On Behalf Of *Rafik Dammak
> *Sent:* 30 March 2010 02:48
> *To:* Julie Hedlund
> *Cc:* gnso-osc-csg
> *Subject:* Re: [gnso-osc-csg] Actions/Summary: 26 March 2010 Meeting
>
>
> Hello,
>
> Mary sent her suggestions and there are two alternative:
>
>
>
> #1: "Policy Committee meetings shall be open for attendance by all {GROUP}
> members, and, subject to any express provisions otherwise in a {GROUP}
> Charter, shall also be open for attendance by the public."
>
>
>
> #2: "Policy Committee meetings shall be open for attendance by all {GROUP}
> members, and, subject only to the conditions specified in this Section 8(b),
> shall also be open for attendance by the public. These conditions are either
> that (i) the {GROUP} Charter expressly restricts attendance at a particular
> type of Policy Committee meeting; or (ii) the Policy Committee decides, in
> its reasonable discretion, that the nature of a particular Policy Committee
> meeting is such that attendance should be limited only to {GROUP} members.
> Provided that, in the case of condition (ii), the Policy Committee shall
> inform all {GROUP} members of its decision to restrict attendance at the
> meeting as soon as practicable and in any case prior to the commencement of
> the meeting, and it shall further use reasonable efforts to make public any
> decisions taken at that meeting as soon as possible thereafter."
>
> Regards
>
> Rafik
>
> 2010/3/27 Julie Hedlund <julie.hedlund@xxxxxxxxx>
>
> Dear Work Team members,
>
> Here are the actions/summary from today’s meeting and posted on the wiki
> at: *https://st.icann.org/icann-osc/index.cgi?constituency_operations_team
> *..  Please let me know if you have any changes or questions.  Our next
> meeting will be held *Friday, 09 April at 1300 UTC/0600 PST/0900 EST for
> one hour.*   Thank you very much.
>
> Best regards,
>
> Julie
>
> *Action Items*:
> *1. Task 1, Subtask 2: (See the wiki at: **
> https://st.icann.org/icann-osc/index.cgi?constituency_and_stake_holder_group_operations_work_team_task_1_subtask_2
> *. )
> *A) CHANGES THROUGH SECTION 8:
> *
>
>    - *Work Team members should review all changes through Section 8.
>    Policy and provide comments to the list not later than Friday, 01 April. It
>    will be assumed that all changes are agreed to if no comments are received.
>    *
>    - *Rafik Dammak* agreed to ask Mary Wong if she had suggestions for
>    alternative language for Section 8. Policy, paragraph b. "Committee 
> meetings
>    should be open for attendance by all {GROUP} members –- and at the election
>    of the Constituency -- to the public.”
>    - *Krista Papac* agreed to review Claudio DiGangi's suggested language
>    (added to the wiki) to Section 4. Voting as it also could be applied to
>    Section 1. Executive Committees to maintain consistency.
>
> *B) REMAINING SECTIONS:* *Work Team members should review the remaining
> sections of Task 1, Subtask 2 and send comments to the list:
> *
>
>    - *9. GNSO WG; *
>    - *10. Reference to Code of Practice at Annex B (and Annex B text); *
>    - *11. Reference to Handbook on Common Rules and Principles;    *
>    - *12. Reference to recommendations applying to Contracted House
>    Stakeholder Groups; and *
>    - *Part IV: Analysis*
>
>
> *2. Task 1, Subtask 3: Julie will load the latest version from Krista on
> the wiki.* Work Team members are requested to review the document in
> preparation for the meeting on Friday, 09 April.
>
> *3. Task 2: Outreach:* *Debbie Hughes will provide some ideas to begin the
> discussion on the Sub Team. *The Sub Team members are: Debbie (leader),
> Olga Cavalli, Rafik Dammak, Claudio DiGangi, Chuck Gomes, and Michael Young.
>
> *Summary:
> *
>
>    - Olga noted that Philip Sheppard, the new Chair of the Operations
>    Steering Committee, has requested that the Work Team complete its work by 
> 01
>    June in preparation for the ICANN meeting in Brussels. Olga explained to
>    Philip that the Work Team might not be able to complete Task 2, but would
>    complete the remaining subtasks of Task 1. She recommended that the Work
>    Team should finish Task 1, Subtask 2 by the next meeting and begin a review
>    of Task 1, Subtask 3, and asked Krista to send the latest version for Julie
>    to load on the wiki.
>    - The Work Team discussed additional changes to Section 1. Elections
>    and Section 4. Voting. Claudio provided revised language to the list for
>    consideration. Krista agreed to review Section 1. Elections in view of
>    Claudio's revised language.
>    - The Work Team agreed to retain the previous changes in Section 5.
>    Voting. Rafik agreed to ask Mary Wong if she had suggestions for 
> alternative
>    language for Section 8. Policy, paragraph b. "Committee meetings should be
>    open for attendance by all Constituency {GROUP} members –- and at the
>    election of the Constituency -- to the public."
>    - On Task 2, Olga asked for volunteers for a Task Sub Team. Debbie
>    Hughes agreed to be the leader of the Sub Team and the other volunteers
>    were: Olga Cavalli, Rafik Dammak, Claudio DiGangi, Chuck Gomes, and Michael
>    Young.
>    -
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4983 (20100329) __________
>
>
> The message was checked by ESET NOD32 Antivirus.
>
>
> http://www.eset.com
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4987 (20100331) __________
>
>
> The message was checked by ESET NOD32 Antivirus.
>
>
> http://www.eset.com
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4987 (20100331) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
> ------------------------------
>
>
> *The information contained in this email message and its attachments is
> intended only for the private and confidential use of the recipient(s) named
> above, unless the sender expressly agrees otherwise. Transmission of email
> over the Internet is not a secure communications medium. If you are
> requesting or have requested the transmittal of personal data, as defined in
> applicable privacy laws by means of email or in an attachment to email, you
> must select a more secure alternate means of transmittal that supports your
> obligations to protect such personal data. If the reader of this message is
> not the intended recipient and/or you have received this email in error, you
> must take no action based on the information in this email and you are
> hereby notified that any dissemination, misuse or copying or disclosure of
> this communication is strictly prohibited. If you have received this
> communication in error, please notify us immediately by email and delete the
> original message.
> *
>
>  ------------------------------
>
> *The information contained in this email message and its attachments is
> intended only for the private and confidential use of the recipient(s) named
> above, unless the sender expressly agrees otherwise. Transmission of email
> over the Internet is not a secure communications medium. If you are
> requesting or have requested the transmittal of personal data, as defined in
> applicable privacy laws by means of email or in an attachment to email, you
> must select a more secure alternate means of transmittal that supports your
> obligations to protect such personal data. If the reader of this message is
> not the intended recipient and/or you have received this email in error, you
> must take no action based on the information in this email and you are
> hereby notified that any dissemination, misuse or copying or disclosure of
> this communication is strictly prohibited. If you have received this
> communication in error, please notify us immediately by email and delete the
> original message.
> *
>
>
> ------------------------------
> *The information contained in this email message and its attachments is
> intended only for the private and confidential use of the recipient(s) named
> above, unless the sender expressly agrees otherwise. Transmission of email
> over the Internet is not a secure communications medium. If you are
> requesting or have requested the transmittal of personal data, as defined in
> applicable privacy laws by means of email or in an attachment to email, you
> must select a more secure alternate means of transmittal that supports your
> obligations to protect such personal data. If the reader of this message is
> not the intended recipient and/or you have received this email in error, you
> must take no action based on the information in this email and you are
> hereby notified that any dissemination, misuse or copying or disclosure of
> this communication is strictly prohibited. If you have received this
> communication in error, please notify us immediately by email and delete the
> original message.
> *
>
>