...
This page is intended to document the internal processes of the Technical Documentation sub-team to facilitate continuity between terms. It is currently under construction and will be filled out throughout the remainder of the 2022-2023 term.
Roles and Responsibilities for TechDocs Members
Maintain ArchivesSpace technical documentation in tech-docs Github repository
Collaborate with ArchivesSpace program team to prioritize, assign, and work on issues in the TechDocs Jira board.
When new versions of ArchivesSpace are released, review release notes, providing edits/suggested changes to developers.
Identify documentation maintained by other sub-teams, link to it as appropriate, and avoid duplication of effort.
Review community-submitted issues and pull requests to the repository.
Perform yearly surveys of old documentation to provide edits/updates.
Review and manage Awesome ArchivesSpace.
Solicit feedback and contributions from the community
Encourage ArchivesSpace community to submit issues regarding documentation directly to the tech-docs repository or contact sub-team members via email to suggest improvements.
Monitor listserv for issues for which further documentation would be helpful , and create the appropriate documentation, or at least a stub for future documentation, in a timely fashionfile an issue in the TechDocs Jira board to be prioritized and assigned.
Review, manage, and promote Awesome ArchivesSpace.
Perform outreach and make ArchivesSpace community aware of TechDocs
Promote TechDocs work and facilitate broad community knowledge by linking to relevant portions of documentation in listserv responses and other communications.
Suggest the inclusion of relevant links to TechDocs within documentation maintained by other sub-teams.
Membership
TechDocs includes members of the Technical Advisory Council, as well as members of the ArchivesSpace Program Team. Meetings are also open to Lyrasis developers who support ArchivesSpace.
Roles & Responsibilities for Lead & Vice-Lead
The Vice-Lead is responsible for taking notes during the meeting and covering for the Lead if they are unavailable. The Lead is responsible for orienting new members, facilitating access to the GitHub repository and Slack channel, scheduling meetings, creating agendas, and writing the quarterly reports on sub-team activities. Both the Lead and Vice-Lead write and submit the retrospective at the end of each term.
Communication between meetings
In addition to communicating asynchronously via the TechDocs Jira Board and emails, members of Techdocs and the ArchivesSpace program team can use the Slack channel.
TechDocs Github Repository
...