[Ssr2-review] SSR2 Call Summary: 2 August

[Eric Osterweil]

<no hats>
Hi Phil,

I’ve commented in-line below:

> On Aug 6, 2018, at 7:46 PM, Phil Khoury <phil at crkhoury.com> wrote:
> 
> Hi all,
>  
> Oh boy. Can I just say that was a pretty terrible meeting – I feel like we took about 5 backward steps in 40 short minutes.
>  
> Thanks Eric for comments and background. 
>  
> Pretty sure we don't want to be editing records of meetings to this extent, in particular individual historical perspectives that weren’t part of the meeting. That said – it is useful to understand how everyone is thinking.

I have to say, I don’t understand this.  I think the meeting summaries represent the go-to source for the archival progress of our work.  I’d argue that in the future, people will look at _those_ without ever (for example) listening to the transcripts and/or reading the chatroom archives.  Therefore, I would argue that these are the most important artifacts of our work (except for our eventual report, obviously).  This is, actually, why we’ve been seeking meeting minutes for so long.  That’s why I (personally) think these summaries _must_ be accurate and complete.

As for the text I sent, I don’t presume that my words need to be used.  I simply sent proposed text as a courtesy.  In some spaces (like the IETF) it’s polite to "send-text” when advocating for changes.  Regardless, I think we (as a team) need to learn how to fish and produce these summaries (with Staff support in whatever capacity we land on), so thanks for facilitating this issue with us, Phil.

That said, I would submit that the comments that I made before and during the call (including those in the chatroom) constitute more than an individual historical perspective.  If you’re wondering about them, I suspect you should be able to verify them by listening to our recordings from the corresponding times last year (I don’t think we had minutes back then for easy lookup). ;) Anyway, ymmv.  

>  
> Happy to edit ICANN 63 item to reflect your observation about ‘significant’. Jennifer could you please remove ‘significant’ from the text. My only concern is to make sure no one thinks that there is some magical solution that solves for all the problems with F2F meetings.

Thanks, while I agree that this is necessary, I also strongly feel that it is not sufficient.

>  
> As for the whole NDA issue. Sigh. To be crystal clear:
>  
> No one raised the NDA as a problem with me. A few people on the team mentioned the issue when I asked if there were unfinished things that would need to be dealt with. My conversations re: the NDA totalled about 4 minutes in all the calls I had.
> Staff did not raise it with me or ask for it to be put on the agenda.
> I, in my ignorance, simply added it to the agenda to make sure that we were starting to pick up on some of the practical things that need doing.
> Clearly this is an issue that some team members have strong views about – it was my intention to have a 90 second conversation about this – not trigger another half-hour debate. 

I think this needs to be added to the session summary in some form.  The context and explanation here is far more illuminating that what is in the record now.

> I have asked Steve Conte to do a brief summary of the position reached previously – it is not immediately critical, can we just leave it there for now. 

So, shouldn't we hold off on publishing the summary until this can be reviewed?

>  
> As our meeting was cut short by technology grief and distractions, we did not get time to talk about process leading up to the F2F in Washington. Please note that I am going to be contacting team members, hopefully I will get to all of you, between now and then to have a further one-to-one discussion about outcomes and your individual contribution.
>  
> Finally, I appreciate that this is not easy, but can I ask for some patience please. 
>  

Eric
</ho hats>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ssr2-review/attachments/20180807/f0c7451a/attachment.html>