2019-02-14 Meeting notes
Date
Feb 14, 2019
Participants
@Christine Di Bella (Program Manager)
@Jared Campbell
@Peter Carini (Unlicensed)
@Former user (Deleted) - absent
@Alicia Detelich
@Max Eckard (Chair) - REGRETS
@Megan Firestone (Unlicensed)
@Bobbi Fox
@Patrick Galligan (Unlicensed)
@Edgar Garcia (Unlicensed) - absent
@Maggie Hughes (Vice Chair)
@Jason Loeffler (Unlicensed)
@Dave Mayo (Unlicensed)
@Julia McGinnis (Unlicensed) - absent
@Laney McGlohon (Unlicensed) (Technical Lead)
@Bria Lynn Parker (Unlicensed)
@Dallas Pillen
@Dustin Stokes (Unlicensed) - Regrets
@Trevor Thornton
@Wiedeman, Gregory
Goals
Mid-year check-in on sub-team work plans
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
2 min | Roll call and notetaker | @Bobbi Fox |
|
5 min | Recent contributions (since December 13, 2018) |
| Listserv:
Code:
Bugs/new features:
|
5 min | Program update | @Christine Di Bella | Community discussion on Feb 26 over Zoom with board members. Asking for “big picture” ideas for discussions. This is an opportunity to interact with board members.
March 18th Online forum. If have a proposal, please submit before Feb 18th. 11 hours of ArchivesSpace content! Starting at 1pm EST. Idea is to support users around the world. Trying new things. OPEN TO ANYONE, regardless of membership! @Christine Di Bella isn’t sure she’ll be there for all 11 hours.
Nomination season is going on, April 19th is the deadline for nomination. @Gordon Daines is chair of the Nominations Committee, but send nominations to Christine.
Final stages for search for community outreach coordinator; hope to have an announcement soon.
|
2 min | Bimonthly meetings | @Maggie Hughes |
|
20 min | Sub-team updates and mid-year check-in |
| Work plans
|
| Integrations | @Patrick Galligan (Unlicensed) | Lately been focusing on documentation for new approach to integrations; specifically how and why to integrate. Includes how to advocate for integration, different levels of integration. Updating to help users understand what we do. Brainstorming questions about what community members are looking for, with an eye to a formal survey. Have some information, but want a structured way to analyze and share with others. Trying to connect community groups outside the Aspace community to cast a wider net. (e.g.: google groups, local archivist group) Helped set up first Alma -Aspace integration meeting. Integrations work has been slow a the moment, so focusing outward.
|
| Migrations | @Julia McGinnis (Unlicensed) and @Bria Lynn Parker (Unlicensed) | Working independently on the import/export map updates ; discussing how to assess how the subteam is doing at monitoring listservs and helping with migration questions. |
| Technical Documentation | @Alicia Detelich | @Alicia Detelich met with @Dave Mayo (Unlicensed) to understand the changes he’s advocating for API documentation.
Needs to send email about work, and ask for more feedback. At last meeting, brainstormed on reaching out to the developer community; now have to act on those ideas.
Q: feedback on what? A: where there are gaps to fill. |
| Development Prioritization |
| @Maggie Hughes & @Lydia Tang (Unlicensed) will co-chair. Working on ways to handle tickets more efficiently & quickly. Decision was made that a workplan isn’t necessary for this group; leaving old workplan as an archived page. The work is pretty consistent, so there’s no way to add specifics to a workplan.
|
| Testing |
| [no update] |
5 min | Working group updates: Workflows and implementation strategies for smaller institutions/smaller staff levels | @Megan Firestone (Unlicensed) | Is there anyone on TAC interested in joining in to scope out the group’s work? Once there’s scope, it will go out to the listserv at large. Christine & Laney would be willing to help with the scope.
|
5 min | December discussion: “an active community of developers” | All | (quote found at https://archivesspace.atlassian.net/wiki/spaces/AC/pages/794230793/2018-2019+Technical+Documentation+sub-team+Work+Plan ) How does everyone feel about this discussion? Any next steps? @Patrick Galligan (Unlicensed) : sometimes ArchivesSpace community can be a little daunting to new members. Maybe should start small to build confidence. Have a small workshop at the annual meeting for a particular issue – like “pair programming”, to broaden pool of developers. @Laney McGlohon (Unlicensed): Trying to figure out how to get this started. Worried she goes too fast into the depths of Aspace. Maybe a “drop-in” where interested people could get involved. Doesn’t know how to get someone started. @Bria Lynn Parker (Unlicensed) : talked about this at core committers; put together an “on-boarding” process, not just for core committers but more broadly? @Patrick Galligan (Unlicensed) start with something really shallow. e.g.: this is how you can customize Aspace home page; this is how you can change what the exporter is doing, etc. @Dave Mayo (Unlicensed) : having some sort of “office hours” so people can come to you with a specific problem that they’re having. People are very focused on their problems, and might be less focused on onboarding in general. @Laney McGlohon (Unlicensed)y: did a workshop on plugins – maybe less scary? @Maggie Hughes : was at workshop, but maybe making it longer – another component later, like office hours. for followup & guidance.
@Dave Mayo (Unlicensed) : Adding missing in-line documentation like “this is what this class does”, and parameter description. @Laney McGlohon (Unlicensed): different type of documentation for those who are coders vs. people who are learning to code, or have done it in python, etc. It would help have fresh archivists' eyes to help on what they need to understand. Need to understand the architecture. (Jruby, RoR, Sinatra, how you run tests, etc.) There’s some basic stuff she doesn’t think is documented. Maybe put together and outline, and people volunteer to take different pieces. @Maggie Hughes : Do we need another group for this? @Laney McGlohon (Unlicensed) : Core committers is very interested in this; Laney is lead. Laney will bring this to core committers and get back to this group. Also meet at Code4Lib next week?
|
5 min | Open mic! | All |
|
2 min | Next time |
| Notetaker: @Patrick Galligan (Unlicensed) Thursday, April 11 at 2pm EST |