...
Monday 27 April | Topic | Who | Length | Spkr OK? Slot OK? | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
12:00 EDT | Housekeeping | Maria Whitaker | 10 mins | ||||||||
12:10 | Status check on appointment of Community Manager and Technical Coordinator (slides) The Community Manager will be advertised as a remote post. Things will be moved forward as quickly as the hiring freeze at Emory allows. If that becomes problematic we may need to consider an alternative hiring strategy. | Jon Dunn | 15 mins | ||||||||
12:25 | Finance and budget reports (slides) | Richard Green | 15 mins | ||||||||
12:40 | Steering Group elections 2020 (slides) | Richard Green | 5 mins | ||||||||
12:45 | Connect 2020 and 2021 (and maybe 2022) - info and status checks Connect 2020 in Santa Barbara has been cancelled as the direct result of the COVID-19 pandemic. A virtual event will be arranged in place of the cancelled face-to-face conference. See Brian McBride's presentation below for further details. We plan to hold Connect 2021 at the University of Notre Dame (this was already in the early stages of planning as Rick Johnson's presentation below shows) and UC Santa Barbara hope to stage the event there in 2022. | Chrissy Rissmeyer Rick Johnson | 5 mins 5 mins |
| |||||||
12:55 | Virtual Connect 2020 - info May 14-15, 11am - 1pm EST Currently 12 presentation proposals on a range of topics, 13 working group updates Working on logistics - timetable likely available next week Planning meeting on 4/30, until then proposals will still be accepted - ping David Schober and Franny Gaede on Slack if you do want to do so. | David Schober | 5 mins | ||||||||
13:00 | Encouraging contributions to, and participation in, Connect conferences; ideas for format of fall Connect Contact brian dot mcbride at utah dot edu Slack: Brian McBride | Brian McBride | 15 mins | ||||||||
13:15 | Governance assessment exercise (slides) Governance Working Group produced a set of six recommendations. Exercise is to go through them and judge how well we are doing in implementing them. Also going to survey more broadly - people who are interested in Samvera but not highly engaged - how we appear to people outside our Community but that we interact with. Rank each recommendation in a similar fashion to the 'It takes a Village' report:
| Esmé Cowles | 40 mins | ||||||||
13:55 | Wrap-up | ||||||||||
Tuesday 28 April | |||||||||||
12:00 EDT | Housekeeping | Maria Whitaker | 10 mins | ||||||||
12:10 | Samvera's use of Circle CI Samvera's current payment plan for CircleCI assumes a fairly steady usage of the tool and doesn’t cope well with the peaks that occur – for instance when we hold a developer event. It is proposed that we move to a new plan that relies us on buying ‘credits’ which can be used at any rate and topped up if needed. Our devs think that this may possibly lower our annual CircleCI bill as well as suiting their needs better. After discussion, it was agreed that we should move to the new arrangement immediately. The system will initially be set to provide regular credits at approximately the current rate of usage and we can manually finesse this as required - increased to deal with a peak, dialed back if we are amassing a surplus. Richard Green will notify Lyrasis of the change in charging pattern. The system will be set to copy Steering's finance subcommittee with details of charges. | Esmé Cowles | 10 mins | ||||||||
12:20 | Brief reports from Roadmap Council, Component Maintenance WG, Hyku IG, Hyrax MWG and IG | ||||||||||
Nabeela referenced the detailed email she had sent out recently giving a quarterly update on the Roadmap Council's work. Her first slide details the membership of the Council. Subsequent slides set out the Council's three next goals and the pattern of meetings. The first goal, currently being worked on, involves analyzing roadmaps and planning cycles around the Community to try and produce a centralized roadmap. The second goal is to facilitate the process for getting code back into core, 'code reclamation'. The third goal is to improve communication into and out of the Roadmap Council, to help increase collaboration across the Community and to help facilitate 'asks'. Rob Kaufman explained that the code reclamation work is to reclaim useful features for the core that have been implemented in one or more projects. As part of that it is envisaged that people who have contributed to core code in the past would work with 'new' people who have interesting code but have never yet contributed it back. Another aspect would be encourage people to look at existing implementations of a feature in the Community, and rather than write their own version from scratch, spend their dev cycles getting a generalized version of that feature code back into Hyrax. Rob wants to try and break the pattern that "we didn't invent this code and so want nothing to do with it" and, in doing so, cut down on duplicated work. A reminder from Nabeela that we have lists on the wiki of systems in production and in development which help the Roadmap Council identify features that might usefully come back into core. | Nabeela Jaffer | 7 mins | |||||||||
Component Maintenance Working Group (slides) James | Griffin7 mins | Hyrax Maintenance Working Group | Tom Johnson | 7 mins | Hyrax Interest Group (inc update on Hyrax PO) 's first slide details Phase 4 (Jan 2020 - Oct 2020) of the CMWG's work and its membership. Phase 3 had addressed quality assurance and documentation across all the core GitHub repositories. Phase 4 is addressing Ruby and Rails support to bring our code into line with their latest versions so that we can continue to take advantage of their bug fixes and security patches. CMWG are keeping up to date the 'State of Core Components' spreadsheet tracking new releases of gems that Samvera uses (note a typo on this slide - the date should refer to 2019). Future plans include a Community sprint in June 2020 to update our gem dependencies etc and possibly a second one in the fall. Keen to identify some more active members for the Group to help with the maintenance and documentation work; how do we get them, and would incentivization be helpful? | James Griffin | 7 mins | ||||
Hyrax Maintenance Working Group Group is a stable, agile team that runs sprints on a two weeks on, two weeks off basis to provide maintenance for the Hyrax code base. Goal is to prioritize security and bug-fixes, provide some stability in architectural direction of the code base and keep a level of coherence in the code across the many contributors. Group allows for a stable maintenance policy for Hyrax in terms of what gem versions are supported. Hyrax 2.7 is current, 3.0 coming soon. QA has moved from a pre-release 'swarm' to also involve ongoing QA on tickets going through the WG - not marked closed until the QA done in addition to the fix. Like CMWG, also looking to attract new members - please contact Tom or Jessica Hilt. | Tom Johnson | 7 mins | |||||||||
Hyrax Interest Group (inc update on Hyrax PO) Meeting regularly and trying to 'pick up the slack' of not having a PO. Lot of planning for Hyrax 3.0 and Valkyrization so ticket grooming is a little behind. Participation has fallen off over the last few months but it is hoped 'summer will invigorate people'. Group has been searching for a new PO - this should become the pattern; it should not be for an outgoing PO to find someone. PO job description has been modified to be a bit more realistic in a 20%-size box but new POs should also be able to concentrate on parts of the job where they feel they can add most value and delegate the rest. A small number of candidates identified and talked with and Julie Hardesty is likely to take on the role starting July - does not want to take on the Community pieces of the role but to concentrate on the true PO aspects they should go to the Samvera Community Manager (CM), when appointed, or perhaps to a Hyrax CM in the meantime. Just working through a last few issues before Julie can make a formal commitment. General agreement that 'community asks' should be a CM role, not a PO one, and that these need to be regular. | Rob Kaufman | 7 mins | |||||||||
Hyku Interest Group | Rob Kaufman | 7 mins | |||||||||
12:55 | Report from Marketing Working Group including discussion on website update (slides) | Chris Awre | 15 mins | ||||||||
13:10 | Process for forming Working and Interest Groups - review and update the guidelines? | Robin Ruggaber | 30 mins | ||||||||
13:40 | Partner Ask for Upgrading Hyrax to Improve Valkyrie Work | Jessica Hilt | 5 mins | ||||||||
13:45 | Parking lot
| 15 mins | |||||||||
14:00 | Wrap-up - evaluation of on-line versus f2f meeting (may be earlier depending on parking lot items) | ||||||||||
Deferred | |||||||||||
Are job adverts put out on our lists successful? Where did successful applicants hear about their jobs (do we know)? | All | Email survey? | |||||||||
Code of Conduct review - status check https://docs.google.com/document/d/17hrlfQtE89zw_N0ccp373JVA29NY_EVZrsdFszK-rdU/edit?usp=sharing | Jessica Hilt? | move to monthly call? |
...