Monday 27 April | Topic | Who | Length | Spkr OK? Slot OK? |
---|
12:00 EDT | Housekeeping | Maria Whitaker | 10 mins | |
12:10 | Relationship with Lyrasis 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. We will need to discuss at the October Partner Meeting the relationship with Lyrasis who, long term, would like us to use them as an 'organizational home' - this would be a significantly different arrangement to the current fiscal sponsorship. We need to agree what we would want out of a relationship and see how that matches what Lyrasis offers as an organizational home - or even if we want such a thing. Need to be decisions on this by spring next year. | 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. Connect 2021 Status Update (slides) | 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
Program Committee is reviewing how other conferences are dealing with needing to 'go virtual'. Seeking input from Partners on how the virtual event might look. Trying to capture all the valued aspects of past f2f Connects: dev congress, plenary, presentations, lightning talks, unconference, Partner meeting - also keep the social component: themed evening dinners, conversations over coffee. Other conferences are trying a spread over several days, full-day and half-day on line, spread over multiple weeks with only a short (2hr?)presentation time each day. Can we/should we try to multiple track presentations? Theme days? Topic days? Trying to get a lot of feedback from the Community to put together something beneficial and to which people will feel welcome. Please everyone take some time to think this through and offer suggestions about how to structure tracks, themes, social components - either own ideas or ideas from other conferences. What software might we use? Need a good sample of data from the Community. Helpful if we could have ideas by the time of the next Program Committee meeting on 7 May. Plan to refine it and put 2-3 suggestions to the Virtual Connect meeting for consideration and discussion. Note that having an online conference might bring in people who wouldn't have travelled to Santa Barbara and many of they could be 'newcomers'. Also online may give us an opportunity to try new ideas that we wouldn't couldn't have done in an f2f.
Initial feedback: Spreading the conference out potentially allows someone to attend more events than they would physically have been able to but that scheduling your calendar becomes more difficult "people schedule over the top of you". Small group dinners have usually gone down well - perhaps we should try and make sure there is a social event (or several small ones) especially for new folks. A "newcomers coffee hour"? In considering what CNI did to go virtual we should remember that they needed to arrange something very rapidly and we should realise that they did not have the luxury of a great deal of planning for it. 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: **Just getting started **Making good progress but not yet fully accomplished **Completed an under periodic review **Don't know Particularly wanting to surface any places where there is not a good consensus.
- Steering will become an elected body from Partners
Overwhelming majority say 'done' but a handful (including several from Steering) say only 'good progress' (still one more election cycle to complete it). - Samvera will hire centralized staff
8 say just getting started, 21 say making good progress. Still some big questions up in the air and we are still uncertain when the first, let alone the second, appointment will be made. People can't yet plan to take advantage of this staffing. Nevertheless we think we are close to hiring a Community Manager through Emory (despite the COVID problems) - we're closer to finishing that than to just starting. Hope that the MOU with Lyrasis, which will allow Samvera to transfer the necessary monies to Emory straightforwardly, will be signed 'in the next couple of weeks' so that we could then post the position. Contribution Model work takes us some way to putting together money for the Tech Coordinator position in the future. - Samvera will develop a Contribution Model
Similar split to (2). We may have the paperwork but we haven't actually seen the money come in yet and we don't know how that will go. We are making progress towards spring 2022 when the contribution model minimum contribution comes into effect. The Model was created not expecting a major financial crisis; this year will help us see how the Model can be made more resilient to cope with fluctuating funding situations at institutions in the future. We probably need to put some thought into how we deal with institutions that genuinely can't meet their minimum in a given year. - Partners will establish a Roadmap Council
19 say completed and under review. Established and doing a lot of good work - looking forward to a Community Manager in place who can help with coordination across the Community. RC is trying to transition to a body that knows things 'that are going to happen' rather than 'have happened'. 3 say 'making good progress but'. Not all the Community is coordinating in the way that was envisaged when the Roadmap Council was created. Several voted 'don't know' - knew that the RC had been formed but not very aware of what it has been doing. Note that the RC feels they are about coordinating elements of the roadmap - not about creating it. "The reason we don't have a roadmap is that we don't have enough people moving the work forward to justify having one." A roadmap would need cooperation between Avalon, Hyku and Hyrax "so that everyone is on the same page about what work is getting done." - Newly established Steering will update bylaws
Solid majority for 'completed and under periodic review'. - Partners will assess governance at the end of 2019
Accepting that it is now 2020,.. We are currently engaged in this work and it is not yet complete. Still need to survey a wider group (see introduction to this segment). Governance is not a value unto itself, it facilitates the functioning of the Community and we should ensure it is doing that. The Governance Assessment WG will report back when the wider survey has taken place. We should probably assess governance on a regular basis.
| 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 |
|
|
|
| Roadmap Council (slides) 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. | Nabeela Jaffer | 7 mins | |
| Component Maintenance Group (slides) | James Griffin | 7 mins | |
| Hyrax Maintenance Working Group | Tom Johnson | 7 mins | |
| Hyrax Interest Group (inc update on Hyrax PO) | 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 - Need to discuss resourcing for (software) development work.
- Samvera's next set of recommendations or goals; what goals we should set to achieve
- contributing local code to core code
|
| 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? |
|