2022-09-01 Meeting Agenda and Notes

3 minutes

Introductions

Rachel

• Welcome @Elizabeth M. Caringola

• Who you are, where you work, years on TAC (or involved in ArchivesSpace)

• Note-taker? Liz C.

5 minutes

Orientation

Rachel

• Important things are linked at the top of the agenda!

• What does this group do?

10 minutes

Logistics and Updates

Rachel

• Scheduling for monthly meetings

  • Probably won’t meet in Dec.

  • If there’s a month where we’re working on something, then we can touch base asynchronously

  • Rachel will send out a Doodle poll to find a regular meeting time

• Sub-team Vice Lead needed

  • Folks can take time to think about it and determine later in the year if needed

• TechDocs will lead discussion for April TAC meeting

• Access to documentation and working spaces

  • Austin, Liz, and Jenna need access to the GitHub repo; some people probably also need to be removed. Rachel will email Christine about it.

• Open pull requests (can discuss more in work plan section)

5 minutes

Review last year’s work plan and retrospectives

Rachel

• No work plan last year

  • This is a year of rebuilding

• 2021-2022 Tech Docs RetrospectivePreview

  • Actually TechDocs hasn’t implemented Jekyll for the Tech Docs site yet; to make it happen Mark would need collaborators and someone to research/determine which site generator to use and map out a project plan. It sounds like we don’t have the capacity to fully work on it this year, but perhaps we can do more researcher/planning. Could also look into whatever themes/features might be possible with the GitHub site in the meantime.

30 minutes

2022-2023 Workplan

Rachel

• 2022-2023 TechDocs Work PlanPreview

• New ideas are in red.

• What should we add? What should we remove?

  • Jekyll research/planning could fall under improving visibility/usability of TechDocs.

• Specific ideas?

  • Access to repo/pull requests? People from same institution probably shouldn’t merge each other’s requests. Anyone on TechDocs should feel empowered to merge. One idea is to discuss at our monthly meetings and do it live together.

  • Rachel will review current pull requests and merge.

  • At our next meeting we can discuss what we want the process to be going forward.

• Collaboration

  • Are there other groups that could contribute documentation?

  • Training needs

    • Git

    • Identify training that’s readily available

5 minutes

Recap

Rachel

• Identify and review action items

• Identify items for next meeting