2024-04-18 TAC meeting notes

5 min

Attendance ice breaker

@Austin Munsell

Icebreaker: What is the most common question you are asked when someone finds out what you do for a living?

5 minutes

Program Update

@Christine Di Bella

• Virtual Member Forum slides recordings are available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3560210434

• In-person member forum in conjunction with SAA 2024 to be announced shortly (August 14); call for program committee will be sent out soon

• Program team will be at Code4Lib 2024 in Ann Arbor (May 13-16)

15 min

Sub-team Updates

Development Prioritization:
@Matt Strauss

Integrations:
@Elizabeth Dunham

Metadata Standards:
@Kevin Clair

Technical Documentation:
@Jenna Silver @Rachel Searcy

Testing:
@Austin Munsell

• Development Prioritization:

  • Continued work with @Thimios Dimopulos on improving guidance for Jira tickets for feature requests and bug reports

• Integrations: Completed review of disposition decisions (with thanks to Bonnie and Liz!), moved content identified for retention to Confluence, and disposed of all Integrations Google Drive content.

• Metadata Standards:

  • Community survey on metadata standards is still in progress and will be circulated to the community soon.

• Technical Documentation:

  • Conversations around restructuring TechDocs to better support developers on Program Team

  • Next steps will include reviewing and revising charge

• Testing: Nothing to report

5 minutes

TAC Business

@Austin Munsell

• Thanks to Bri and Rachel for presenting at the Virtual Member Forum and Regine for helping to organize.

• Nomination season is April and May:

  • Looking to appoint up to 6 new members

  • Nomination deadline: April 26

• TAC Vice Chair needed for 2024-2025 term:

  • Term can be extended by a year for leadership roles

• End of term preparations

  • Retrospective planning

  • Google drive appraisal/cleanup

25 minutes

Jira ticket enhancement efforts and end to end testing possibilities

@Thimios Dimopulos

• Background:

  • Jira documentation:

    • Jira acts as a form of communication and knowledge sharing between users, DevPri, developers, and testers.

    • How to Request a New Feature

    • How to Report a Bug

    • Behavior Scenarios

      • Given / When / Then - Gherkin

        • Given some initial state

        • When the user makes an action

        • Then the system responds with an outcome

  • Virtual Member Forum Presentation

  • Issue Description Templates on Jira:

    • • Click on Create →Issue Type: Bug

      • Click on Create → Issue Type: New Feature

  • Additional Reading:

    • Writing Good Gherkin

    • Behavior Driven Development

      • Inclusion

      • Clarity

      • Automation

      • Code reuse

      • Confidence

      • More exploratory manual testing

    • Writing Great Specifications

• Next steps:

  • Gather feedback and improve the Jira templates and Wiki pages

  • Develop an End to End automated test suite

• Comments? Email thimios.dimopulos@lyrasis.org

• Comments from discussion:

  • Pointing out the need for outreach and education on templates and Gherkin; there is a need to address barriers to participation and feelings of intimidation.

  • Could members on TAC take on task of transforming user-submitted tickets into more preferred format?

  • DevPri have had some discussions on this subject and are interested in contributing to this effort

  • Middleware analogy: templates, open office hours on ticket writing, and other activities as a pipeline towards incorporation into the codebase

  • Role of existing regression testing process with regards to Gherkin use cases and/or automated testing? Potential for Testing sub-team members to participate in the development of these processes in the future

• Slides of presentation: 2024 18 April TAC Meeting.pptx

3 min

Open Mic

2 minutes

Closing Notes

@Austin Munsell

There will be breakouts for Retrospective work next meeting.

May 16 TAC meeting: Thursday, May 16th at 1pm EST / 10 am PST