<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Hi Filiz, we will be in M10 .... <br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
<span id="OutlookSignature">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Get <a href="https://aka.ms/ghei36">Outlook for Android</a></div>
</span><br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Filiz Yilmaz <filiz@peeringdb.com><br>
<b>Sent:</b> Tuesday, February 18, 2020 11:51:42 AM<br>
<b>To:</b> Terry Sweetser <Terry.Sweetser@ix.asn.au><br>
<b>Cc:</b> DTF PeeringDB <dataownership-tf@lists.peeringdb.com><br>
<b>Subject:</b> Re: [PDB Data Ownership-TF] Apricot 2020</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Terry,<br>
<br>
Thanks for your mail.<br>
<br>
As it is announced now, lets keep it as it is. <br>
Like I said I will be there and can answer any questions. <br>
<br>
However I have a prior meeting between 12:00-13:00. So I may be a copule of minutes late as I move to the meeting room.
<br>
Which one will it it be in?<br>
<br>
Filiz<br>
<br>
> On 17 Feb 2020, at 21:52, Terry Sweetser <Terry.Sweetser@ix.asn.au> wrote:<br>
> <br>
> Hi Filiz,<br>
> <br>
> Please accept my apologies, I have obviously taken far too much liberty on the notion of an open meeting at Apricot.<br>
> <br>
> Will you be happy to continue the meeting in my proposed format? Would prefer to have a more private meeting, as well or instead of the public one?<br>
> <br>
> Regards,<br>
> <br>
> Terry Sweetser<br>
> General Manager, IX Australia<br>
> Mobile/WhatsApp: +61455067119<br>
> <br>
> <br>
> -----Original Message-----<br>
> From: DataOwnership-TF <dataownership-tf-bounces@lists.peeringdb.com> On Behalf Of Filiz Yilmaz<br>
> Sent: Monday, 17 February 2020 12:02 PM<br>
> To: DTF PeeringDB <dataownership-tf@lists.peeringdb.com><br>
> Subject: Re: [PDB Data Ownership-TF] Apricot 2020<br>
> <br>
> Arnold<br>
> <br>
> Few things:<br>
> <br>
> Nobody said we are not transparent or that this TF has a closed-behind the doors format or it is closed.
<br>
> <br>
> We have made our mailing list publicly archived and we are recording everything.<br>
> We also have an understanding that we take important decisions after ample discussion among ourselves.
<br>
> <br>
> But we also operate as a TF. TF members can post and participate on ongoing discussions that impact the work of the TF. So while we are transparent, active participation and the actual work to be done is exclusively for the TF members. As such we have not
made our Google doc public for everyone for example.<br>
> <br>
> We did not set a clear set of rules of engagement at the beginning because this group is pretty mature in running a bottom-up process and I believe everyone are familiar with how a TF operates in our industry circles.
<br>
> <br>
> I think when a public session should or should not be had, is in fact a subject of a collective decision of the TF.
<br>
> <br>
> There is a big difference between an internal informal discussion between few TF members who happen to be in the same meeting (which was the suggestion about this meeting initially) versus a public engagement session with community at large at a meeting.
Latter requires proper preparation and coordination because we will be talking about our findings and decisions and only few of us will be representing the TF.<br>
> <br>
> Transparency also starts “within” the group of course. <br>
> <br>
> To my understanding this was an internal and informal TF mtg between you, me, Terry and Job (before his trip got cancelled) so far. I had posts to this ml in order to arrange even an online GoTo mtg so other TF members could join into the meeting, like any
of our previous meetings, following the same transparency goals. <br>
> <br>
> Frankly to me what was not so transparent is that it now turned into a public engagement session without a clear understanding of the rest of the TF.
<br>
> <br>
> Agreed on having an open session is good in general for raising awareness about our work but like I said it requires preparation. It is hard to do that when you think a meeting is an internal one with some of the TF members but then it turns out to be a public
one with a totally different audience. <br>
> <br>
> All good from my end having the session as it is announced now on Whova app and as I said I will be there. We are all busy and communication is not easy but It is also key to the success of this TF. Lets help each other keeping each other up to date and well
informed. <br>
> <br>
> Filiz<br>
> <br>
>> On 17 Feb 2020, at 08:01, Arnold Nipper <arnold@nipper.de> wrote:<br>
>> <br>
>> Filiz<br>
>> <br>
>>>>>>>>> On 16.02.2020 21:45, Filiz Yilmaz wrote:<br>
>>> In principle TF should have agreed on this.<br>
>> <br>
>> is the TF a closed shop meanwhile? I can't remember that this was <br>
>> decided. However, I also was not able to attend every call.<br>
>> <br>
>>> I do not remember support for a public presentation when Arnold <br>
>>> suggested it previously.<br>
>> <br>
>> I've handed in a presentation for the Apricot Peering Forum and will <br>
>> mention the DTF briefly as well. No details, though.<br>
>> <br>
>>> As your initial call for meeting was for an internal TF members only <br>
>>> meeting for those who would be in MEL, my understanding was not at <br>
>>> all for this so far either.<br>
>>> There had been luckily some movement in the last TF meeting. So we <br>
>>> can provide a latest. You and Arnold were not present at that <br>
>>> meeting. You can of course watch the recording to get up to date.<br>
>> <br>
>> Having an open meeting is a good idea imho and is fully in line with <br>
>> the PeeringDB principles of openness and community support.<br>
>> <br>
>> <br>
>> CU soon<br>
>> Arnold<br>
>> --<br>
>> Arnold Nipper<br>
>> email: arnold@nipper.de<br>
>> mobile: +49 172 2650958<br>
> --<br>
> DataOwnership-TF mailing list<br>
> DataOwnership-TF@lists.peeringdb.com<br>
> <a href="https://lists.peeringdb.com/cgi-bin/mailman/listinfo/dataownership-tf">
https://lists.peeringdb.com/cgi-bin/mailman/listinfo/dataownership-tf</a><br>
</div>
</span></font></div>
</body>
</html>