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.
Need TAC Vice Chair – volunteer(s)?
10min
Discussion of ad hoc working groups and other form feedback
Concerns with working groups and time commitments in the past, think we should be cautious when creating new ad hoc working groups.
Created the API Ad Hoc Working Group. Good interest levls.
Work plan with timeline
Tight scoping
Other working group ideas:
Interest in seeing whether a working group could be chartered with the goal of evaluating local ArchivesSpace customizations. Of primary concern to me personally would be detailing precisely how organizations have developed and maintained plug-ins. Further, another area of focus I would propose would be to evaluate how user interface customizations have been ported between upgrades of ArchivesSpace.
I'd like to suggest an Aeon integration improvement working group. This suggestion is based on the results of the Integration Sub-team survey (shared at the Member Forum in Austin) + internal interest at Atlas in getting community feedback for improving the extant integration.
Noticed more questions popping up regarding configuration and/or functions not working as expected. Perhaps some direction in that realm might be useful...
Other comments:
Ask TAC Metadata Standards to comment on Records in Contexts Ontology (RiC--O) when it comes out for public comments in October
More basic education around the purpose and use of the API (through API Working Group) would be great.
10min
Brainstorming TAC meeting discussion topics
All
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