ICANN ICANN Email List Archives

[gnso-osc-csg]


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

Re: [gnso-osc-csg] RE: Actions/Summary: 07 March 2010 Nairobi Meeting

  • To: "Papac, Krista" <Krista.Papac@xxxxxxxxxxxxxxxx>
  • Subject: Re: [gnso-osc-csg] RE: Actions/Summary: 07 March 2010 Nairobi Meeting
  • From: Rafik Dammak <rafik.dammak@xxxxxxxxx>
  • Date: Thu, 18 Mar 2010 01:01:05 +0900

Hello Krista,


do you think that EC shouldn't comply to term limitations which is applied
to GNSO council itself?

Rafik

2010/3/15 Papac, Krista <Krista.Papac@xxxxxxxxxxxxxxxx>

>  All,
>
>
>
> Here are my suggested changes to Part II, Section 4a.  Additions are
> bracketed in red capital letters and deletions are stricken through in red.
>
>
>
> 4. Elections
>
> a. All  {GROUP} {CHARTERS SHALL CLEARLY DELINEATE HOW) {ELECTED
> POSITIONS}, including representatives to Stakeholder Group {EXECUTIVE
> COMMITTEES} and the GNSO Council, shall {BE ELECTED, WHAT THE TERM LIMITS
> ARE FOR EACH POSITION, AND MAXIMUM NUMBER OF} have a maximum two year
> limit and a maximum of two consecutive terms {IN THAT  THE SAME POSITION}.
> {ANY OTHER PROCEDURES RELATED TO ELECTIONS OR EXCEPTIONS TO ELECTION
> PROCEDURES MUST ALSO BE DESCRIBED IN THE GROUP CHARTER.}  An Officer who
> has served two consecutive terms must remain out of office for one full term
> prior to serving any subsequent term {IN THAT SAME POSITION   {GROUPS}  MAY}
> elect terms and term limits below these maximums at their discretion. {WHEN
> CIRCUMSTANCES DEMAND EXCEPTIONS TO THIS REQUIREMENT. EXCEPTIONS MAY ONLY BE
> MADE WITH SUPPORT FROM TWO-THIRDS MAJORITY OF THE MEMBERSHIP.}
> b. It is recommended {GOING FORWARD} that  {GROUPS} publish and maintain a
> list of all Office holders, past and present, { {GROUP} members and to
> provide transparency for term limits.
>
>
>
> I also want to comment on Part II, Section 1c.  I believe we may have
> closed this section out, but since I was unable to make the calls due to the
> reschedule time I am providing my comment to the WT in hopes we can make a
> change.  This section (pasted below) refers to Executive Committees and term
> limits.  From the perspective of the RrSG, this section should also refer to
> the Group Charter, rather than dictating what term limits are. I have
> suggested changes below.  Additions are bracketed in red capital letters and
> deletions are stricken through in red.
>
>
>
> 1. Executive Committees:
>
> a. All Executive Committees must promptly publish action points, decisions
> and any resolutions to constituency members. It is recommended that prompt
> publication means within a reasonable period and a guideline is between 72
> hours and 1 week of the relevant meeting.
> b. All Executive Committees must publish to constituency members their
> rules and procedures, decision making process and criteria.
> c. A limit of two years per term and a maximum {NUMBER OF CONSECUTIVE} of
> two terms per office being a total maximum of four years in any 
> office(hereafter Term Limits) shall apply to members of Executive Committees 
> {AND
> MUST BE DESCRIBED IN THE GROUP CHARTER}. {GROUP CHARTERS MUST ALSO HAVE
> PROCEDURES FOR REELECTING MEMBERS} A member who has  {HAVE} served two {THE
> MAXIMUM NUMBER OF} consecutive terms on the Executive Committee must
> remain out of office for one full term prior to serving any subsequent term
> as a member of the Executive Committee {IN THE SAME POSITION). {ANY
> EXCEPTION TO THIS POLICY WOULD REQUIRE APPROVAL BY THE MEMBERSHIP.} {MUST
> ALSO BE OUTLINED IN THE GROUP CHARTER.}
>
>
>
> Thank you,
>
> 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
>
>
>
> *“Software Escrow for Dummies”** - order your complimentary copy t*oday at
> <http://www.ironmountain.com/escrowfordummies>
> 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
>
>
>  ------------------------------
>
> *From:* owner-gnso-osc-csg@xxxxxxxxx [mailto:owner-gnso-osc-csg@xxxxxxxxx]
> *On Behalf Of *Julie Hedlund
> *Sent:* Monday, March 08, 2010 1:21 AM
> *To:* gnso-osc-csg
>
> *Subject:* [gnso-osc-csg] Actions/Summary: 07 March 2010 Nairobi Meeting
>
>
>
> Dear Work Team members,
>
>
> Here are the actions/summary from yesterday’s meeting.  Please let me know
> if you have any changes or questions.  Our next meeting will be held n*ext
> Friday, 26 March at 1300 UTC/0600 PST/0900 EST for one hour.*  The actions
> and summary are included on the wiki at: *
> https://st.icann.org/icann-osc/index.cgi?constituency_operations_team*.
>  Final agreed-upon changes to the Task 1, Subtask 1 document are on the wiki
> at: *
> https://st.icann.org/icann-osc/index.cgi?constituency_stakeholder_group_operations_work_team_task_1_subtask_1
> * and the Task 1, Subtask 2 document at: *
> https://st.icann.org/icann-osc/index.cgi?constituency_and_stake_holder_group_operations_work_team_task_1_subtask_2
> *.  Changes are shown in ALL CAPS, strikeout, and curly brackets.  Thank
> you very much.
>
> Best regards,
>
> Julie
>
> *Action Items:
> *1. *Work Team members* are requested to review the "Revised Language in
> Task 1, Subtask 2 through the end of Part II, Section 8 and provide any
> comments by the next meeting on *Friday 26 March.
> *2. *Section 4 Elections Paragraph a: Krista Papac* agreed to suggest
> alternate language.
> 3. *Section 5 Voting:*
>
>
>    - *Paragraph a and b: Mary Wong and Zahid Jamil* are requested to
>    review the revised language.
>    - *New paragraph d: Work Team members* are requested to consider and
>    comment on the language.
>
> 4. *Section 8 Policy:*
>
>    - *Paragraph a: Victoria McEvedy* is requested to provide clarification
>    on the meaning of the statement.
>    - *Paragraph d: Mary Wong* is requested to provide alternate language
>    for Work Team consideration.
>
>
> *Summary:*
>
>    - Task 1, Subtask 1: Work Team members agreed to the final version of
>    the revised recommendations.
>    - Task 1, Subtask 2: Work Team members reviewed and discussed changes
>    through Part II, Section 8 Policy.
>
>  ------------------------------
>
> * 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. *
>


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

Privacy Policy | Terms of Service | Cookies Policy