...
Sub-teams and their charges may need to be revised as the system matures and new needs emerge. This year we saw one sub-team sunset – and do so with care and intention – as well as another team restructure themselves. We should always be open to changing things that are either not working or no longer serve a significant need. New sub-teams and or task forces may be required in order for the Council to continue supporting the technical growth of the application, and the community’s understanding of it.
Larger conversations and developments in the archival profession may warrant dedicated conversations and/or projects regarding their potential implications for TAC, such as the release of EAD4 or the incorporation of community contributions to the core code.
The testing process and the role of individuals on the Testing sub-team will likely evolve as the ArchivesSpace Program team explores behavior scenarios and assesses the feasibility of an automated end-to-end testing suite.
Continued communication and collaboration between TAC and the ArchivesSpace Program team is encouraged.Multiple Council members expressed a desire to better understand the contexts in which other institutions are using the application.
Multiple Council members expressed a desire to have a better understanding of work that is underway or on the horizon, in particular the development roadmap and the Jira tickets being discussed in Development Prioritization.
Multiple Council members expressed a desire to better understand the contexts in which other institutions are using the application.
Leadership for 2024-2025
...