Re: [gnso-ppsc-wg] Summary & Action Items: Operating Model Sub-Team Meeting, 30 Apr 2009

[Thomas Roessler <tlr@xxxxxx>]

Thanks a lot for these minutes; they are highly useful -- and  
apologies for missing the call due to yet another conflict.
I suspect that I bear some responsibility for the "guidebook" term,  
out of a private e-mail exchange with Subiah; that term was based on  
the notion that many of the things talked about in the logistics  
subgroup were on a level of detail that needs some discretion.  (Yes,  
I had overlooked one of the introductory sentences that said as much.)
However, I'll note that there are a few (really, few) points in there  
that probably go beyond mere guidance; I'd like to see us try to tease  
these out and write them down separately.
--
Thomas Roessler, W3C  <tlr@xxxxxx>




On 1 May 2009, at 05:32, Ken Bour wrote:

> Working Group Team:
>
> The “Operating Model” Sub-Team met today, 30 April 2009 (1500-1615  
> UTC).
> The following participants attended the conference call:
> Konstantinos Komaitis
> Caroline Greer
> Alexey Mykhaylov
> Tim Ruiz
> Alexei Sozonov
> S. Subbiah (Chair)
> Staff Support:
> Glen de Saint Géry
> Liz Gasster
> Ken Bour
>
> The following summary attempts to capture the essence of the  
> discussion including action items (also posted to our Operating  
> Model Sub-Team WIKI page: https://st.icann.org/icann-ppsc/index.cgi?wg_team_model) 
>  .
> The Sub-Team followed Subbiah’s suggested agenda sent via email to  
> the list.
> AGENDA Proposed by Session Chair - S. Subbiah
>
> - Roll call
> - Agreement on previous minutes
> - Input on any additional agenda items for this session
> - Section reports from Mini-Team Leaders
> - Roles and Responsibilities
> - Norms
> - Logistics and Requirements
> - Products and Outputs
> - Plan next steps
> - Modifications to reports
> - Plan for presenting the reports at next full WG Team call
> - AOB
>
> Note:  the mini-team assignments held firm from the prior meeting  
> (24 April) and are repeated below so that readers can identify which  
> individuals are working on what functional areas (now termed  
> Chapters) of the Operating Model document.
> Participants & Team Assignments:
> NAME
> AFFILIATION
> ASSIGNMENT
> Nacho Amadoz (L)
> RyC
> Roles & Resp
> Alexei Sozonov
> Registrar
> Roles & Resp
> Caroline Greer (L)
> RyC
> Norms
> Greg Ruth
> ISPs
> Norms
> Konstantinos Komaitis
> NCUC
> Norms
> S. Subbiah (CHAIR & L)
> Individual
> Logistics
> Thomas Roessler
> Individual
> Logistics
> Tim Ruiz (L)
> Registrar
> Products
> Alexey Mykhaylov
> Individual
> Products
>
> After roll call, as a first order of business, Subbiah asked for  
> acceptance of the “Summary and Action Items” prepared by Ken Bour  
> from the last session (24 April).   That Summary was thereupon  
> accepted without objection.
> Subbiah invited each team leader (marked “L” above) to take the  
> group through its recommendations – all having been posted by Ken to  
> the WIKI.
> Ken requested the opportunity to start with a newly recommended  
> Chapter 1.0 General added since the last meeting.   He then covered  
> its four prospective sections briefly.    Subbiah suggested that the  
> term “Guidebook” be added to the document title as in “Operating  
> Model Guidebook” to reflect the viewpoint that this document is  
> intended to be more of a compendium of considerations, options, and  
> best practices rather than a set of procedures to be rigidly followed.
> Alexei followed with Chapter 2.0 Roles and Responsibilities assisted  
> by Ken.   Ken recommended that the “Checklist,” under Section 2.1,  
> be relocated to an Appendix (e.g. Section 6.0) and volunteered to  
> make that change in the outline so that the group can see what it  
> would look like in that form.   Under Section 2.3, there was some  
> discussion that this section should also lay out the various roles  
> that any WG might need, e.g. Chair, Vice-Chair (or Alternate Chair),  
> Secretariat (e.g. minutes, summaries), Staff Support, Meeting  
> Logistics, et al., along with duties.   Ken volunteered to add these  
> sub-sections to the outline.   Tim raised the question about whether  
> “expert” roles might also be described in this section (currently  
> handled in Section 4.3).   Also, under Section 2.4 Sub-Teams, it was  
> suggested that we mention the importance of achieving  
> representational balance on any sub-teams created to avoid unhealthy  
> alliances from forming that might work at cross-purposes to the  
> goals of the WG.   It was also discussed that, perhaps, we should  
> combine Sections 2.5 and 2.6 since both deal with the background,  
> experiences, and interests of members.   Finally, there was  
> discussion that Section 2.5-2.6 should contain procedures concerning  
> two questions:  (1) How can a WG member be removed or ejected  
> (presumably for ‘cause’)?  and (2) What appeal might there be for a  
> non-member if he/she was not accepted into the WG?   Ken will add  
> those thoughts to the outline for further discussion.
> Caroline continued with Chapter 3.0 Norms.   Under Section 3.1, it  
> was suggested that content be added concerning participant  
> “contribution,” including any ideas we might have about what minimum  
> levels might look like.    In Section 3.2, Ken recommended  
> incorporating ICANN’s Code of Conduct so that the sub-team can see  
> other possible behavioral norms that could possibly be included.     
> Ken mentioned that, for Sections 3.3 and 3.4, the Charter may be  
> prescriptive in terms of “Rules of Engagement” and a strict  
> definition of “Consensus,” especially if the WG is commissioned for  
> a policy development purpose.   This Operating Model, though, could/ 
> should still contain these sections in the event that the Charter is  
> silent on those matters (e.g. non-policy scope/mission).
> Under time pressure, Subbiah described his mini-team’s content under  
> Chapter 4.0 Logistics and Requirements without much discussion.    
> After he completed those sections, we were 15 minutes over the hour  
> threshold.
> It was agreed that Tim’s Chapter 5.0 Products and Outputs would  
> continue to be discussed via the WIKI and email list between now and  
> 6 May – the next full Working Group Team meeting.
> A final question that was very briefly discussed was how to review  
> this level of detail with the larger team.   Ken agreed to discuss/ 
> share with J. Scott so that we can come up with an approach that  
> maximizes the limited amount of time available on 6 May’s conference  
> call.
> If anyone needs Staff support with respect to continued editing of  
> the WIKI document, please let me know.
> Thank you for another productive session,
>
> Ken Bour
>
> P.S.   For those who missed the call, an MP3 recording will be  
> available at:  http://gnso.icann.org/calendar/ (See 30 April,  
> Operating Model Sub-Team, 1500 UTC).