2020-10-21 Meeting notes

5 mins

Roll Call

@Brittany Newberry (Unlicensed)

UAC Vice Chair

@Brittany Newberry (Unlicensed)

Dan Michelson is the new UAC Vice Chair

5 mins

Program Update

@Christine Di Bella

• Two further releases are planned this year. The first is planned for November and will contain new code and bug fixes. The second release towards the end of the year will focus on the new Agenets module. Christine thanked all of the testers and encouraged participants to join future testing.

• The new lead developer post has been advertised. Christine asked UAC members to share the advertisment and direct anyone interested in the post with questions or queries to Christine.

• The Friday ‘take a break with ArchivesSpace’ Zoom calls will wrap up at the end of October.

10 mins

Sub-team Reports

Please report updates since the last meeting on September 15

Development Prioritization

@Daniel Michelson

Discussed 12 Jira tickets at our September meeting.

Users Documentation

@Krista Oldham (Unlicensed)

@Johanna Carll (Unlicensed)

• Reviewed page assignments and assigned page edits.

• Discussed Style Guide

• Assigned release v. 2.8.1

Testing

@Joshua Shaw

• Testing 32 JIRA & GitHub Issues. Will be doing standard regression testing for upcoming release in next few weeks.

Usability

@Lori Dedeyan

@Althea Topek

• Usability submitted a new feature request as a follow-up from the collection organization report:https://archivesspace.atlassian.net/browse/ANW-1118

• Started reviewing tickets from the usability_subteam swimlane

Member Engagement

@Brittany Newberry (Unlicensed)

@Regina Carra

• met 9/25/2020

• reviewed draft code of conduct created by Jessica Crouch

• discussed new projects, such as Members Match, a revamped version of the Implementation Buddies program

30 mins

Discussion: ArchivesSpace Code of Conduct

Member Engagement sub-team

https://drive.google.com/file/d/1Bcx3sgWlq-Nj8neKiLUXP208e2Zv8-ia/view?usp=sharing

Regina provided an overiew of the Member Engagement sub-teams work on this the code of conduct:

• First project of the sub-team.

• ArchivesSpace had previously used the Code4Lib code of conduct.

• Jessica Crouch was been tasked with drafting the code following the August sub-team meeting.

• One question was how to deal with complaints, reviewing reports and recourse. It was decided that the Member Engagement sub-team would review reports arising from complaints and decide by majortity vote on any recourse.

• The sub-team were keen to gather ideas on how the the draft code could be shared with the ArchivesSpace community for feedback.

Comments and suggestions:

Regina: having the community norms and expectations at the start of the code was very good and showed what the community was about and that it was welcoming.

Jessica: several codes of conduct were reviewed in drafting the code.

Kat: asked how the code would be disseminated. Would it be in the terms that ArchivesSpace members have to agree to or would it be circulated on listservs?

Bailey: dissemination is to be discussed at the next Member Engagement sub-team meeting.

Regina: can we clarify whether this is for the community or anyone joining an ArchivesSpace event?

Bailey: would want to be able to address potential harassment at open forums or Zoom meetings.

Jessica: would be disseminated at any type of event - at the announcement and registration. It would be sent to all participants. Not currently sent out to all community members.

Brittany: would be great to have it sent to new members when joining the community.

Christine: agreed that sending out to new members as part of their new member package would be a good idea. However, agreements with institutions are usually only sent to one individual. Could also be placed on Github and cover contributing code and also on Listservs.

Althea: appreciated inclusion of consideration for participants' time.

Jessica: the sub-team plans to disseminate this code of conduct to UAC and TAC. It will also be opened up to the wider community for comment.

Regina: asked if anyone has advice on the consultation process and how to receive comments? Planning on using a Google doc for the process.

Dan: suggested using Google forms going into a Google sheet.

Brittany: agreed that Google forms made sense.

Kat: thought it might be best to have comments posted on the document. It might still be possible to have comments submitted anonymously.

Bailey: risk that comments can get messy in a big community on a Google doc and could require a lot of time to work on, review and implement.

Brittany: sub-team can discuss at Friday’s meeting as to how to move forward with this. Thanked the Member Engagement sub-team for leading the discussion and to Jessica for drafting the code of conduct.

10 mins

Other business

Althea asked what is the status of the ArchivesSpace implementation buddy program?

Brittany: it is currently being worked on by the Member Engagement sub-team. Looking at rebranding as a member match scheme which would go beyond implementation.

Ashley: the previous implementation buddies name made it too specific on implementation.

Brittany: asked participants to send any ideas to the Member Engagement sub-team. Working on the scheme during this yearly meeting cycle.

Brittany: suggested participants look at Trevor Thornton’s TAC document on engagement.

Next Meeting

November 18, 2020, at 1 PM ET