Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

11am-12pm PT / 2-3pm ET

Call info

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/480879807

Or iPhone one-tap :

US: +14086380968,,480879807# or +16468769923,,480879807# Or Telephone:

Dial(for higher quality, dial a number based on your current location):

US: +1 408 638 0968 or +1 646 876 9923 or +1 669 900 6833

Meeting ID: 480 879 807

International numbers available: https://zoom.us/zoomconference?m=84TFS7JsXMfyDTGBEmbXOm0WHlAnv3Zp

Participants

Notetaker: John Zarrillo (Unlicensed)

Goals

  • Mid-year check in on sub-teams' progress.

  • Discuss wiki and documentation for Councils and sub-teams.

  • Feedback on integrated sub-teams.

Discussion topics

Time

Item

Presenter

Notes

5 min

Roll call

Maggie Hughes


Program updates

Christine Di Bella


TAC/UAC updates

Lydia Tang (Unlicensed)

Quarterly Report for ASpace Governance Board due: March 2.

Will be second joint Quarterly Report for TAC/UAC. See Joint Quarterly Reports.

Council chairs assisted the Nominating Committee in revising their call for nominations - please share!

40 min max (~5 min each)

Sub-team and working group updates

  • Mid-year check in. Look at your work plans and comment on progress:

    • Are things progressing as you thought? Have you accomplished what you thought?

    • Have you encountered any roadblocks? Do your work plan scopes need be re-adjusted?

  • Sub-teams with ongoing work (not really work plans), like Testing and Dev Pri, can comment more generally.

TAC sub-teams

Integrations: Dallas Pillen

Metadata Standards: Kevin Schlottmann

Tech Docs: Alicia Detelich

API Working Group: Dave Mayo (Unlicensed)

Integrations

Metadata Standards

Tech Docs

API Working Group

UAC sub-teams

Usability: Julia Novakovic

User Docs: Jasmine Jones (Unlicensed)

Usability We have started to meet every two weeks in order to maintain momentum and focus.  We’ve worked on 7 tickets needing additional Usability investigation - we met with reporters for two of the tickets to continue to suss out and refine ticket requests.  We’ve also pursued topical projects, such as the usability and visual appearance of accessing the ArchivesSpace public and staff interfaces using a mobile device. Christine di Bella recently set up “swim lanes” in JIRA to ensure that Usability and Dev. Pri. don’t overlap when addressing tickets, which seems helpful. We are seeking additional members. If you’d like to join us, please email Lydia at ltang5@msu.edu!

User Docs: User Manual went live on Confluence in December. Users have already provided comments on pages requiring fixes. User Docs sub-team is in the midst of making those revisions, as well as assigned new/revision tasks, once the 2.7.1 release candidate is available. Sub-team is also currently establishing processes for updating the user manual with new documentation and existing documentation and connecting with Testing and Dev Pri during documentation development. Also developing a style guide for the user manual. Once established, the team will begin a review of existing documentation.

Cross-council

Dev Pri: Lydia Tang (Unlicensed)

Testing:Brittany Newberry (Unlicensed)

Dev Pri published a summary of the Dev. Pri. survey results in January and also a Leader Guidance document.  We have been exploring alternative approaches to assign tickets, having Edgar and Randy volunteer thus far to assign tickets. We’re seeking community feedback on the following tickets (as in, please comment on this ticket if you would also like these features and provide as much detail as possible on what that should look like and do):

  1. https://archivesspace.atlassian.net/browse/ANW-477

  2. https://archivesspace.atlassian.net/browse/ANW-336

Testing: Testing sub-team tested 19 Jira issues in December/January for the next release

15 min

Discussion on Council and sub-team documentation and using the wiki

Maggie Hughes

Discuss the purpose of this wiki. When should things be added here? And what are those things?

  • Feel comfortable with adding and updating

  • Sub-teams have ownership

  • Anything of enduring use or value to your sub-team

  • Documenting conclusions!

How have sub-teams been approaching this? Have any sub-teams created new documentation/practices that they can share?

What documentation should be improved?

5 min

Feedback on integrated sub-teams

Lydia Tang (Unlicensed)

General feedback on integrated sub-teams

  • Should continue?

  • Benefits?

  • Pain points?

2 min

Open mic

Next time

Next TAC meeting: April 21 at 12pm PT / 3pm ET

Next UAC meeting:

Action items

  •  

Decisions