2019-01-17 Agenda/Meeting Notes

Work plan progress
- Formalize tech-docs as official documentation repo
  - Laney has been updating tech docs repo - https://github.com/archivesspace/tech-docs/pulls?q=is%3Apr+is%3Aclosed
  - Has build page been updated to pull in data from tech-docs?
  - Is there documentation in the archivesspace repo that is not in the tech-docs repo?
  - Anything else we need to formalize this as the official location of docs? (Laney)
- Communicate with AS constituencies to solicit input and share work
  - Thanks to all who have been contributing to recent listserv discussions
  - Linking to documentation in listserv responses - has anyone tried this out?
  - Goals for frequency of listserv responses
  - Proactive solicitation of documentation needs
    - Call to listserv to add issues to tech-docs repo, contact Tech Docs members, or reply to listserv post with ideas - AD can send out an email this month
      - See Christine's email 1/15 - will that cover it?
    - Agenda item at next solo TAC meeting
    - How to reach out to developer constituency
- Prioritize changes based on community feedback
  - No new issues in tech-docs repo
  - Listserv monitoring/doc stubs
- Update API documentation
  - Progress - https://github.com/archivesspace/archivesspace/tree/endpoint_docs (Dave M.)
  - Ideas re: most problematic endpoints to address
  - Next steps
- General
  - How do we measure success?
Description text on sub-team wiki space
Questions, concerns, ideas, etc.