Wanted to review our recent retrospective for new members, to keep in mind for the upcoming year, and because it relates to a few different things in this meeting.
Start doing:
Standards committee or sub-team. Might be at a higher level than TAC.
Identify ways to foster engagement in smaller working groups to help.
Stop doing:
Execution of working groups need fine tuning. Perhaps people are stretched thin in sub-teams and working groups and there should be limits.
Perhaps reevaluate sub-teams like Migrations and Integrations, Integrations sub-team might not need to meet monthly and Migrations might not necessarily be needed since migration paths exist.
Keep doing:
Cross-council meeting was super interesting.
Conversation about how to encourage the community of coders as a group. Identifying issues was helpful in what we are doing (in sub-teams)
Schedule time to meet with sub teams and develop work plan for things to accomplish before the end of fiscal year
Goals should accomplishable
Work plans should be up by the next TAC meeting October 15
Metadata Standards needs a team leader – volunteer(s)?
Tech Docs could use another member if anyone is interested
No interest in continuing Reports Working Group. Reports efforts - from a usability standpoint - are intended to be picked up by the Usability subteam depending on member interest.
Thinking about how to make the most of our TAC meetings and building on our “how to encourage an active community of developers” conversations from last year.
Keep space in our TAC meetings for program updates, sub-team reports, and other things, but add a discussion topic. Ideas:
Each sub-team takes a meeting. Could be used to get feedback, discuss new ideas, etc.
?
5 min
Open mic
All
Next meeting: Tuesday, October 15th from 12-1pm PT / 3-4pm ET
Action items
Sub-team leaders will have action plans for next full meeting