[PDB Data Ownership-TF] Reminder of actions to be completed before Meeting#3

[Filiz Yilmaz]

Hello everyone, 

This is a reminder for actions set in the previous meeting. As a summary:

- Participate in the Doodle <https://doodle.com/poll/svbw6g4kpz8phnth> to set next meeting date/time: Deadline 26 Nov (tomorrow)!
- Go through the Scope <https://docs.google.com/document/d/1su38Vko9_3-aoo_LYvKckbK6PNVTwfLgzbYQBN3bv7c/edit> document: Deadline 6 dec
- Go through the Policy <https://docs.google.com/document/d/1wVqWwmQpYu5L-2lhvLeu0VHOTWCw8dJMEOrw8Cg5DBk/edit#heading=h.mnvwhx5r2153> document: Deadline 6 dec


Regarding my actions: 

> Look into timezones to see if there any time-period that we can set as a fix meeting time on a regular basis and communicate it on the list. 

Unfortunately I could not find a common/greenish slot <https://www.timeanddate.com/worldclock/meetingtime.html?iso=20191125&p1=16&p2=47&p3=136&p4=107&p5=64&p6=56&p7=78> between our timezones which are spread in +/- US, EU/South Africa, Australia, that would not put someone in disadvantage for all their meeting attendance.  
 
So I am not proposing any fixed times at this point. We can discuss how we want to handle this moving forward. 

My personal take on this is that “pain” needs to be shared, that would be only fair. 
So maybe we should continue Doodling the future meetings instead of fixing it at a time that is someone’s 2AM all the time. 
Thoughts?

> Action on Filiz: Work on a timeline for TF to plan its work. 

There is now a WorkPlan and Timelines <https://docs.google.com/spreadsheets/d/1moqmdjkicnXN3cQApnvC6nDwSa6t5nLC2j53aGr1NnY/edit#gid=0> document in Shared folder for your review.


Kind regards
Filiz



> On 20 Nov 2019, at 12:35, Filiz Yilmaz <filiz at peeringdb.com> wrote:
> 
> Dear all,
> 
> We had our 2nd Meeting on 18 Nov 2019, Monday. 
> 
> Below you can find information about this meeting, the actions and pointers for further follow-up:
> 
> 
> 
> Agenda, the high-level notes and the recording of the meeting are all in the shared folder (https://drive.google.com/drive/u/2/folders/1wz08_g6NtqkiBkOYUhekLwVJYwZkCnBv <https://drive.google.com/drive/u/2/folders/1wz08_g6NtqkiBkOYUhekLwVJYwZkCnBv>).
>  
> 
> Highlights of the meeting were:
> 
> Agreement reached on that TF should agree on a scope statement. 
> TF should work towards finalizing this in the next 2 weeks. 
> Action on all TF members: Go through the scope doc <https://docs.google.com/document/d/1su38Vko9_3-aoo_LYvKckbK6PNVTwfLgzbYQBN3bv7c/edit> and make comments or edits. Deadline: 6 December. 
> Agreement on the policy document that it is a good start too and it has the right structure. 
> Ben noted that we may need another section where we discuss the logical data in database on a higher level, with a note how this represented in the database as a database object.
> General agreement that this is a good suggestion. 
> Action on all TF members: Go through the policy doc <https://docs.google.com/document/d/1wVqWwmQpYu5L-2lhvLeu0VHOTWCw8dJMEOrw8Cg5DBk/edit#heading=h.mnvwhx5r2153> and start making comments or edits. Deadline: 6 December. 
> Cadence of meetings should be more frequent. General agreement on having them every 2 weeks. 
> We can also make it a standing meeting set at a fixed, specific time. This may help everyone to have their agendas managed better however we may have time-zone challenges with some zones having the meeting in really bad times. 
> Actions on Filiz:
> Make Doodle call for the 3rd meeting. We should have one the week after 6 December, to discuss the feedback on scope and policy document. 
> Look into timezones to see if there any time-period that we can set as a fix meeting time on a regular basis and communicate it on the list. 
> Other: 
> A rough work plan/timeline might be helpful.  
> Action on Filiz: Work on a timeline for TF to plan its work. 
> 
> 
> If you have any questions, please let me know.
> 
> Kind regards
> Filiz
> 
> 
> 
> 
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.peeringdb.com/pipermail/dataownership-tf/attachments/20191125/a6953ed3/attachment.html>