@mogoodrich, short answer is yes! Here’s the link to the Google doc.
And really, the thanks goes out to you, @burke, @angshuonline, @dkayiwa, and @ibacher for the excellent discussion and resulting action items. Here’s a link to the notes and the key points/decisions and action items are summarized below.
Key Points and Decisions
- The TAC provides our technical direction and strategy. We want make our technical vision explicit and get alignment on our technical challenges and priorities.
- It’s important for the TAC and the PCC to have intentional opportunities to work together. We need to figure out when and where to make this happen.
- The TAC should also make sure that the platform is maintained and up to date. We acknowledged that we face a chicken/egg dilemma: we want and need resources to get work done - and we need to know what work needs to be done in order to allocate resources to work that is actually needed by implementations.
- Listing out what needs to be done is not going to help with alignment unless we know what our objectives are, what our technical direction and strategy is. Otherwise, we’re simply creating a list and people end up working on tickets or modules that are outdated while current work that would benefit many in the community languishes.
- As a result, we spent 20 minutes brainstorming potential objectives. These need to be fleshed out.
Action Items
- Put the rough objectives into a Google document
- Turn the list of ideas into real objectives (@mogoodrich offered to help me with this, others are welcome to pitch in)
We also need to:
- Confirm our weekly meeting time since Daylight Saving Time starts this weekend. This is what the new times would look like: 7:30pm IST | 5pm Nairobi | 4pm Cape Town | 2pm UTC | 9am Boston | 6am Seattle
- Figure out where and how we want to communicate on a daily/weekly basis. Do we want a dedicated Talk thread where we can discuss and make decisions, share meeting updates, etc? Do you want to use any other communication channels?