Create Dates-and-Reminders.md #794
Conversation
|
Add a reminder to meeting template to check on this doc. |
|
|
||
| ## Recurring dates | ||
|
|
||
| - CPC Chair election |
There was a problem hiding this comment.
This year, the CPC chair election happened ending on Aug 17. Should we choose a different date to make the official end of term? Perhaps not the same date as the Secondary Director election or is it not a big deal?
| - Director 1 election - term ends February 28 | ||
| - Director 2 election - term ends August 31 | ||
| - CPC Impact voting member selection - terms end March 31 | ||
| - CPC Non-impact voting member election |
There was a problem hiding this comment.
| - CPC Non-impact voting member election | |
| - CPC Non-impact voting members (2) election |
There was a problem hiding this comment.
Last election concluded May 14
| - Director 2 election - term ends August 31 | ||
| - CPC Impact voting member selection - terms end March 31 | ||
| - CPC Non-impact voting member election | ||
|
|
There was a problem hiding this comment.
| - Voting members (2) as elected by Regular members |
There was a problem hiding this comment.
Last election also concluded May 14
|
I'm wondering if using a versioned file for this is really the best solution. What if we maintained an issue instead? Wouldn't that be easier to modify and keep up to date? Opened a new issue to showcase what this would look like. |
Thanks for looking to optimize @tobie. I really dont know which one would be better -- I'm open to what others think is best. |
|
I'm good either way. A versioned file would be relatively easy to maintain if we removed the requirements for review (ie you could commit directly to master) |
|
LGTM |
WIP: Need to add actual dates.