...
Assuming WG ratification in the ESCo meeting earlier in the day, let’s get together to plan out the kickoff meeting (tentatively scheduled for the 15th). The objective is to solidify an the agenda for that meeting, which might include things like:
...
- Keeping the same cadence as other WGs makes sense
- Wednesday or Thursday makes sense, though most of our previous meetings have been on Thursdays
- Let’s stick to Thursdays, alternating with the FOS WG (which is also on Thursdays)
- Setting the tone for the next meeting: having a material discussion on work items, tracks, assignments, etc. Second meeting would then focus on progress on those tasks.
- Use Foundation Webex - less risk if Anthony is unable to attend
- Initial meeting schedule (over holiday period):
- 15th Dec
- 12th Jan
- Then every 2 weeks from then on
- Make Confluence public but keep formational content private (members only)
- Paul: question on how to encourage participation?
- Peter M: suggest rewarding individual participation
- Identifying decision making process up front is ideal and then ask for objections - don’t lay out a smörgåsbord of options as that encourages endless debates about procedure (which ultimately no one really cares about)
- For coordination amongst ourselves, Symphony cross-pod now seems to be enabled for BNY - Peter Leong is using it.
- Can Anthony find out if he can have it enabled too?
- Paul: best way to solicit work items for people to work on?
- Peter M: I don’t have a good answer, except to say there are no “sticks”, only “carrots” - we have no authority over the participants and really need to focus on rewarding participation as the primary motivator e.g. call out active participants - make sure they know their efforts are appreciated
- Paul: we should ask for prep items from the group for the kickoff meeting on the 15th Dec
- Put them in the agenda wiki page
- Also a separate “call to action” (probably an email to the API WG mailing list)
...