Goals:
Ongoing maintenance and promotion of Github tech-docs repository
Clarify access to tech-docs repository and how to add new contributors.
Review and merge pull requests. Identify who should be responsible for this work within subteam.
Review issues and address as required.
Promote Tech Docs work and facilitate broad community knowledge by linking to relevant portions of documentation in listserv responses and other communications.
...
Review organization of content and identify areas requiring refinement.
Identify functionality with missing or insufficient documentation.
Review release notes of new releases for documentation needs.
Monitor listserv for issues for which further documentation would be helpful, and create stub/placeholders for documentation to be added
...
Identify more effective ways of soliciting feedback from users and developer community.
Solicit specific input/contributions from community (based on needs identified in #2).
Encourage ArchivesSpace community to submit issues regarding documentation directly to the tech-docs repository or contact sub-team members via email to suggest improvements.
Explore how to improve visibility of TechDocs and related resources to the wider community.
4. Advisory Council Collaboration
Explore collaborative efforts between TechDocs and another body within the Advisory Council. Ideas?
User Documentation subteam sub-team of UAC
Within TAC: are Are there things you wish were in the TechDocs that are not?
Identify training needs that subteam (e.g., skills, specific tools) that sub-team members need or would benefit from in order to be successful.
...
.
...
Themes
Rebuilding
Facilitate continuity between terms
How can TechDocs support different types of users: beginners, turn users into super-users?
Information maintenance: https://zenodo.org/record/3236410
...