2018-11-16 Meeting notes

• Notetaker: Alicia Detelich

• Up next: Jared Campbell

Listserv:

• Megan Firestone (Unlicensed)
• Bobbi Fox (Unlicensed)
• Dallas Pillen
• Trevor Thornton

Code:

• Bobbi Fox (Unlicensed)
• Maggie Hughes
• Bria Lynn Parker (Unlicensed)
• Trevor Thornton
• Wiedeman, Gregory

Bugs/new issues:

• Patrick Galligan (Unlicensed)

• Lora Woodford is now the Junior Developer for ArchivesSpace and will be concentrating on development full time. (yay Lora!)
• Christine Kim is stepping down from the Community Engagement Coordinator position at the end of December for a new opportunity with the California Digital Library. We have posted the position at https://lyrasis.isolvedhire.com/jobs/43961.html; applications received by December 7 will receive priority consideration. Hoping to fill by early next year.
• We expect to have one more ArchivesSpace release before the end of 2018. 
• Kansas City Forum is taking place on November 30. Program is looking great - one of the workshops is an introduction to Git and GitHub.
• What will Lora be doing in her new role? 
  • • Day to day things - bugs, small feature enhancements
    • "Future-proofing" activities - increase in stability, improved integration potential, sustainability; testing, migration pathways, etc.
    • Larger features - staff interface enhancement group recommendations, digital objects module (maybe)
    • Lora won't necessarily be doing all of these things herself, but having her in this new role will help get more done overall

• Quarterly TAC report due by 11/21; will share rosters and work plans from sub-teams. If there's anything else to add let Max know.

• Christine, Laney, TAC and UAC chairs meet to discuss cross-council things
• Idea from UAC to combine TAC & UAC meetings
  • May try a joint meeting 1-2x per year to see how it goes
  • Interesting idea, but may be too much for a single meeting to do this all the time
  • Maybe send representatives from certain TAC subteams to UAC meetings and vice versa?
  • Documentation could benefit from more coordination - UAC and TAC both work on this

Subteam leaders share out action plans.

Integrations:

• Met last week; many new members
• Work plan is a work in progress - have a set of tasks, but this may change
• Carry-over from last year - integrations documentation review, update; create centralized list of documentation resources
• Target new integrations - i.e. Alma
• Use feedback from listserv to guide work
• Reach out to communities of other systems that AS integrates with/might integrate with
• Invite integration stakeholders to sub-team meetings
• Education/outreach opportunities - work with Kim's successor

Migrations:

• Audit of import/export mapping files; update as needed, think about a new format
• Use Awesome Archives list for migration resources
• Monitor listservs and respond to migration-related queries

Technical Documentation:

• Met last month; reviewed last year's work plan
• Formalize tech-docs repo as official location for AS documentation
• Communicate with AS community to solicit input re: documentation and share sub-team work
• Prioritize documentation updates based on feedback from community
• Update API documentation...iteratively
• Solicit input from listserv re: potential documentation improvements
• Add UAC to list of constituencies to include in Tech Docs conversations
• Endpoints not listed on API docs? (Patrick send list to Dave if possible)

Development Prioritization cross-council

• Got through 10 or so tickets
• May increase meeting time from 1 hour to 1.5 hours
• Average age of resolved Jira tickets is appx. 2 years from when first reported; would like to get through these a little faster

Testing sub-team:

• Will be testing prior to end-of-year release
• Laney and Lora will be improving automated testing for the application; testing sub-team will be involved in this

Workflows and implementation strategies

• Getting a meeting scheduled; some UAC people interested; working on scoping out what group wil do

API Documentation

• Tech Docs team would like to take ownership of this
• Could potentially recruit others from outside Tech Docs team or TAC/UAC

• Sub-teams continue with work, report at next meeting

• Plugin list