Participants:  Alejandra Reynoso, Joke Braeken, Eduardo Santoyo, David McAuley, Katrina Sataki, Ben Fuller, Lesley Cowley, MirjanaTasic, Dejan Djukic, Stephen Deerhake,

Staff:  Bart Boswinkel, Kim Carlson

Recording

Action Items

 


Agenda:

-          Status Quo: discussion on the current documents
-          Next steps: ccNSO Council Meetings; ccNSO Roles and Responsibilities
-          Tech Day – what to do?
-          AOB


Notes:

Discussions:

Agenda:

1. Welcome and roll-call

2. Wiki-space

3. Status Quo:  discussion on the aforementioned documents

4. Next steps:  ccNSO Council Meetings; ccNSO Roles and Responsibilities, Tech Day - What to do?

5. Work team updates - including discussion open issues

6. AOB

7. Next Meeting (21 December ?)

 

Action items

1. Chair of GRC at time of submission of guideline on ccNSO Meetings:

Include in a note to Council at submission on need to review the guideline in light of changed meeting structure, Council to decide, observation by WG

2. ccNSO Statement Guideline

Open questions

Action previous Bart:  To look at comments

3. Action Stephen: look at ccNSO Collaboration Groups Guidelines, simplify where possible

4. Action Margarita: look at Triage committee charter (Bart to ask her)

5. Action Team members Roles and responsibilities: look at identification and allocation of tasks

 

Welcome and Roll Call

No Apologies received

 

Wiki Space

Space for action items

Document by topic

Difficult to find reasonable structure:

  • Administrative activities of ccNSO
  • Meetings: include all aspects of meetings of ccNSO (not to be confused with meetings of GRC!)
    • Members meeting
    • Council meeting
    • Program WG
    • Tech Day
  • Officers and Appointees
    • Elections, Appointments
  • Operational Activities 
    • Working groups
    • Statement and positions

 

Discussion current documents /Guidelines

Guideline ccNSO Meetings: (latest version in wiki)

Lesley: Signal here potential change ICANN meeting might change. 

Katrina: Either add to current guideline or ask Program WG to update when need is clear

Alternative: Include a note when review warranted.

 

Include in a note to Council at submission, Council to decide, observation by WG

 

Program/Programme WG

Katrina: David and group to look into language

Program WG <- > Programme WG

Maintain Programme (UK English, as preferred spelling)

 

ccNSO Statement Guideline

Open questions

Action previous Bart:  To look at comments

 

All comments are taken into consideration: 

'taking into consideration' does not mean incorporating the comments"

 

ccNSO Collaboration Groups

Feed-back from Group

Volunteers for closer look at document? Stephen Deerhake

Translate into English

Action Stephen: look at ccNSO Collaboration Groups Guidelines, simplify where possible

 

Charter Triage Committee

Action Margarita: look at Triage committee (Bart to ask her)

 

ccNSO Council meetings

Start work

 

ccNSO Roles and responsibilities

Pending for ccNSO Roles and Responsibilities

Comments on identifying and allocating tasks version 4

Open issue: how to cover people who are not performing (mechanism included in WG guideline)

Suggestion/for discussion: include text in this Guideline?

Currently Councilor’s behaviour is addressable through attendance. 

Address it somewhere, ccNSO Members ACCOUNTABILITY

Need for separate, coherent Guideline on Accountability (members. WG members and 

Councilors. Currently part WG members included in WG  Guideline.

 

Tech Day 

Suggestion to include and consult with Tech WG, before making any changes

Should there be a Guideline for Tech Day?

AOB

No comments

Next call: 

21 December, noon UTC

 

Chat Transcript:

Alejandra Reynoso:Good morning

  Kimberly Carlson:Good morning

  EDUARDO SANTOYO:Morning

  Alejandra Reynoso:6am :)

  Alejandra Reynoso:Hi!

  Joke Braeken:Hi Katrina :)

  David McAuley:Good morning

  Joke Braeken:13:00h in Brussels

  David McAuley:7am here

  David McAuley:in DC area

  Mirjana Tasic .rs:Hello

  Lesley:Helo everyone

  Lesley:or hello even!

  Ben Fuller:Hi everyon e, will keep my mic muted because its raining here and the noise on the roof is very loud.

  Stephen Deerhake:Sprry I'm late.

  Stephen Deerhake:Still dark here.

  Lesley:Agree - review in advance of the 3 years normal review

  Lesley:Agree with Katrina

  EDUARDO SANTOYO:+1

  Lesley:US english or UK English

  Lesley:UK Engliah is 'programme'

  David McAuley:agreed - programme

  David McAuley:nice word

  Ben Fuller:Me too

  Ben Fuller:Yes, I will look at it

  Ben Fuller:Sorry we are getting lots of lightening strikes, but I can follow the audio

  Ben Fuller:Katrina, plese remind me which document you want me to look at.

  Katrina Sataki:- Charter: ccNSO Meetings Program WG – ready for the final round of comments (https://community.icann.org/pages/viewpage.action?pageId=56148764)

  Ben Fuller:OK will explain

  Stephen Deerhake:Spell it programme however, Ben :-)

  Ben Fuller:That final sentence in 3.6 looks OK to me

  David McAuley:Me too

  Lesley:'taking into consideration' does not mean incorporating the comments

  Stephen Deerhake:No problem with 3.6 either. 

  Katrina Sataki:yes, that's what I thought too, Lesley

  David McAuley:fully agree with Bart

  David McAuley:consider includes the notion of rejection as well as acceptance

  Stephen Deerhake:+1 for Lesley's interpretation.  That's what it means to me as well.

  David McAuley:I read it last night and frankly it seemed fine

  Stephen Deerhake:I can take it on...

  David McAuley:i will volunteer

  David McAuley:Thanks Stephen

  Stephen Deerhake:Trannslate it into English.

  David McAuley:Good point - the committees doc has some language on non-productive participants as I recall

  David McAuley:para 5.1 of collaboration groups addresses this issue

  David McAuley:+1 @ Lesley for one overarching place to address non-performance

  Stephen Deerhake:I agree with Lesley --have a separate policy document that then gets referenced.

  Ben Fuller:Good idea Lesley

  Ben Fuller:Are there any ICANN bylaws about accountability and performance we can refer to?

  David McAuley:work in progress

  David McAuley:Two days - one for workstream one, another for workstream two

  Mirjana Tasic .rs:I  am supporting Lesley's proposal how to cope with accountability

  Stephen Deerhake:I would say it's not broken; not sure what we need to tweak.

  David McAuley:Are there surveys from recent tech days that might help us

  Stephen Deerhake:Can We carry that question over to the next meeting so I can consult with Eberhard and the Tech WG ?  I'd get on audio but I have no voice today.

  Ben Fuller:It mightbe a good idea to include the TWG in this discussion

  David McAuley:Agreed - Dr Lisse appears to be quite involved - would be good to check with him

  David McAuley:Good idea Stephen

  Lesley:Tech day is still 'owned' by the ccNSO, so I think it should be included

  Stephen Deerhake:I am. Lucky for the group!

  EDUARDO SANTOYO:agree with Lesley

  Ben Fuller:Lesley makes a good point, there may be other initiavies the fall under the ccNSO but link to other SOs

  David McAuley:next call - are we on 2 or 3 week wsched

  David McAuley:ok sounds fine

  Lesley:21st fine with me

  Joke Braeken:for me too

  EDUARDO SANTOYO:ok

  Stephen Deerhake:OK.

  Alejandra Reynoso:ok

  Dejan Djukic:sounds ok

  Ben Fuller:OK

  EDUARDO SANTOYO:have a good week

  David McAuley:Thank you Katrina and Bart and Kim and all

  Stephen Deerhake:Thanks all.

  Alejandra Reynoso:Thank you! :)

  Kimberly Carlson:Thank you everyone

  Mirjana Tasic .rs:Bye

  David McAuley:Bye all

  Joke Braeken:Thank you :) have a nice day

  EDUARDO SANTOYO:bye

  Lesley:Bye

  Alejandra Reynoso:Bye

  Katrina Sataki:thank you, bye!

  Dejan Djukic:bye

  • No labels