Change Management: Core Devs Meeting

[kaitlin-beegle]

Over the last few meetings, current participants in Filecoin Core Devs calls have discussed opportunities and needs for the forum. These are broadly summarized HERE.

The below is a roll-out plan to put these changes into effect. The purpose of this documentation is to have a single point of reference throughout the roll-out process, and for participants to be able to ask questions and provide additional suggestions.

New Meeting Structure

• Length: 1 hour
• Scheduling: beginning of each month on an alternating time basis ( XX 16:00 UTC & XX+1 00:00 UTC)
• Format:
  • Agenda available in repo prior to meeting.
  • Agenda circulated two weeks prior to meeting, with reminders one week prior to meeting.
  • Presentation will include a slide deck of discussion topics, prepared and circulated in advance.
  • Meeting notes and video recordings will be made available afterwards in the TPM repo.
• Attendance:
  • Mandatory; invitees who miss three meetings will be removed from the attendees list.
  • Current Core Devs will be asked to source the list of attendees (privately, since email addresses will be exchanged)

New Meeting Logistics

• First Meeting Date: Thursday, August 4
• Location: Zoom (calendar links sent to attendees)
• Agenda: TODO

Change Management Details

• Ahead of the meeting:
  • Current Core Devs will be asked to help construct, review, and approve the initial list of attendees.
  • The #fil-implementers channel will be changed to #fil-core-devs, and participants updated.
  • Standards and expectations for the new meeting will be shared.
  • Meeting attendees, as well as the broader Filecoin community, will be reminded to submit meeting topics for the kick-off call.
  • A draft presentation will be created in advance and publicly shared.
• During the meeting:
  • An initial review of expectations, purpose, and intent of the meeting will be shared.
  • Attendees will be welcomed to give feedback and offer suggestions for future meetings.
• After the meeting:
  • Meeting materials will be uploaded to the TPM repo.
  • Any additional feedback will be incorporated ahead of the September meeting.

[anorth]

Thanks @kaitlin-beegle. Minor clarifications

invitees who miss three meetings will be removed from the attendees

We probably need some redemption period here, strikes don't last forever. Maybe missing three out of a rolling eight?

It's implicit, but perhaps should be made explicit, that we're expecting attendees to attend at some terrible hour local time once every two months (around 2-4am oceania, 0-2am Europe). Ability to turn up for that will become a condition of continued participation.

[kaitlin-beegle]

Yep, totally right. I put the "three strikes, you're out" as a hold, but we can fine tune the exact rules during the meeting (or here, if you feel strongly about an alternative way of doing things).

The attendance policy isn't designed to exclude/punish anyone, more to emphasize the importance of consistently attending. I agree with your note about the crappy timezone requirement- we all have to do it, it's not fair if folks only show up every other month.