2017-12-15 Meeting notes

2min

Roll call and notetaker

2min

Recent contributions

 @Max Eckard

Listserv:

• Bobbi Fox

• Patrick Galligan

• Jason Loeffler

• Rachel Maderick

• Kari Smith

Code:

• Mark Cooper

Bug reporting:

• Ed Busch

• Jason Loeffler

• Kari Smith

2min

A big thank you to Kari Smith!!!

@Max Eckard and @Kari S. (Unlicensed)

• Kari leaving TAC starting this month

• Will not fill vacant spot until next round of appointments

5min

Program update

@Christine Di Bella

• 2.2.2 release came out and will probably be the last release of 2017

• Email sent out to improve content and layout of the development roadmap. Please provide feedback by Wednesday 12/20

• Staff interface enhancement group will provide recommendations are expected to release next week. These will probably drive a fair amount of development work in 2018. Expected to be a series of progress throughout the year. Looking for developers and partners in the community to help subsidize or contribute development work.

2min

TO-DOs from 2017-11-17 Meeting.

@Max Eckard and @Jason Loeffler (Unlicensed)

• Max will clean up 2016 TAC space for next meeting.

• TAC team leaders please make sure your pages are up to date.

• Jason has not gotten to talking to Christine about digital objects models yet.

15min

Outreach ideas for TAC

@Christine Kim

• Happy to facilitate any outreach activities that we're interested in

• Blog Series

  • Wants to start an all about community series and highlight teams and subteams in the ecosysten

    • Highlight teams in TAC to show various work

    • Could kick off with an overview of TAC and then additional posts for each subteam

    • Then highlight the work that each team is doing

• Webinars

  • Having visual aids about the work we're doing could help

  • Possible Webinars

    • "Lifecycle of an Issue or a Bug"? Give some clarity on what happens with a bug

    • Technical Documentation with tips for those building workflows

    • Migrations and prepping for migration

    • Development prioritization

    • Different importers/exporters

    • Integration highlights

    • Testing webinar just came out yesterday, 12/14

• Open Zoom phone call for entire community

  • Targeted focused discussions for general calls

• Regional forums on top of annual member forums

• Potential for training opportunities on topics like migration or other technical support

• Jason and Patrick offered to help with "A Bug's Life" and Open Calls respectively

• Jason asked for more specifics about ArchivesSpace regional meetings and offered to help with an NYC AS meetup

• Max had a question about how we could publicize blog posts

  • Mostly through tweets and email updates

2min

ArchivesSpace Development Roadmap

• Covered by Christine earlier

2min

Succession planning

@Max Eckard

Cross-council sub-team leaders

Chairs

Each Council Chair shall name a Vice Chair. Vice Chair duties include providing support for Council activities, liaising with and attending meetings of designated subteams, and acting as the Chair in meetings of the full Council in the absence of the Chair. The Vice Chair is the designated successor the next time the Chair position is open, whether because the Chair’s term on the Council has expired, the Chair has resigned from the Council, or the Chair has decided to remain on the Council but resign from the Chair position. If a Vice Chair resigns or leaves the Council before the Chair position becomes available, the Chair will name a new Vice Chair.

• Decided to ensure continuity of work and help with work

• Vice-chair would be the designated successor to the chair

• This would also impact cross-council teams like Testing and Dev Prioritization

• Reach out to @Max Eckard if you are interested in being a vice chair

• Dustin asked about what happens if a Vice Chair's term ends

  • Chair would select a Vice Chair that would be on the council longer than the Chair

  • Christine also mentioned that AS will work on determining the best way to name a Chair (election vs. appointment)

15min

Sub-team and working group updates

@Dallas Pillen (Unlicensed)

• API Documentation working group

  • 2 people expressed interest in joining the group

  • Looking for at least one or two more people to join up

  • Members do not have to be part of TAC

  • Email Max if you are interested in joining.

  • Dustin volunteered.

@Maggie Hughes

• Awesome ArchivesSpace working group

  • Similar update to Dallas

  • Has not gotten any responses

  • Idea of having Integrations topic area came up at the Integrations meeting this week

  • If you don't have time, but want to make a suggestion of someone you know of, please do

  • Hoping for 3-4 volunteers and starting work on January on a work plan and timeline

@Christine Kim

• Core Committers

  • Christine Kim filling in for Laney

  • Solidify process on who follows up on what for pull requests

@Jason Loeffler (Unlicensed)

• Development Prioritization sub-team (cross-council)

  • Going through bug and new feature requests and making them into new releases

  • Is on board with new Vice Chair

  • Also, would be happy to work on "A Bug's Life" webinar

@Patrick Galligan

• Integrations sub-team

  • Circa integration exploration

  • ILS Integration discovery and information-gathering

  • Changes to Work Plan and Mission Statement

@Dustin Stokes

• Migration sub-team

  • Hasn't met recently

  • Figuring out what they want to focus on in the coming year.

@Scott Hanrath (Unlicensed)

• Technical Documentation sub-team

  • Pilot tech-docs repo: https://github.com/archivesspace/tech-docs

    • Pulled tech docs into their own repo

    • Trevor created a README outline on the main page

    • Will use this as an opportunity to improve provisioning information and looking at more basic information about creating and installing plugins

    • Tech Docs will be maintained in the repo and then community members will submit pull requests or issues to drive updates

@Christine Kim

• Testing sub-team

  • Alex Duryee and Miloche Kottman did a testing practices webinar yesterday

5min

Open mic

• Kari Smitth mentioned that the OSS ArcFlow meeting happened and a report on the outcome should come out in about a month