Samvera Tech Call 2018-05-16

How to connect: https://psu.zoom.us/j/613720745 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

Time: 9:00am PDT / Noon EDT

Moderator: LaRita Robinson

Notetaker: Chris Diaz

Attendees:

• Lynette Rayle (Cornell)
• Jim Coble (Duke)
• LaRita Robinson (Notre Dame)
• Collin Brittle (Emory)
• tamsin woo (DCE)
• Brian McBride (University of Utah)
• Steve Van Tuyl (oregon state university)
• cam156 (PSU)
• Chris Colvard (Deactivated) (Indiana University)
• Julie Allinson (CoSector, University of London)
• Mark Bussey (DCE)
• Andrew Myers (WGBH)
• bess (DCE)
• Jason Corum (WGBH)
• Jennifer Lindner (DCE)
• Ayse Durmaz (Duke)
• Trey Pendragon (Princeton)
• Anna Malantonio (Lafayette College)
• Kevin Musiorski (AIC)

Agenda

1. Roll call by timezone per following order - ensure notetaker is present (moderator)

   1. folks outside North and South America

   2. Eastern timezone

   3. Central timezone

   4. Mountain timezone

   5. Pacific timezone

   6. folks who were missed or who dialed in during roll call

   7. Welcome all newcomers!
2. Agenda (moderator)
   1. Call for new agenda items (moderator)
   2. Hyrax 2.1 Update (tamsin woo)
   3. Which Rubies do/should we support? (tamsin woo)
      1. Hyrax says: "We recommend either Ruby 2.5 or the latest 2.4 version."
      2. We don't specify ruby support in `hyrax.gemspec`, should we?
      3. We currently check syntax against Ruby 2.1, preventing use of modern syntax.
      4. WIP: https://github.com/samvera/hyrax/compare/ruby-2.3
   4. Hyrax 2.1, SemVer, and You. (tamsin woo Steve Van Tuyl)
      1. exhibit 1: https://groups.google.com/forum/#!topic/samvera-tech/3V-t_7IEpeE
3. Notetaker and moderator for next time
   
   1. Notes: Jennifer Lindner
   2. Moderate: tamsin woo
4. After call, this week's notetaker should create the agenda for the next call.

Notes

Hyrax 2.1 Update (Tom Johnson)

• Released Hyrax 2.1 rc3 yesterday
• Testing is ongoing, primarily around permissions
• One blocking issue that will require rc4 #3076
• If you can upgrade a 2.1 app to rc3, that would be helpful, especially if you can help with documentation
• Jim's upgrade to rc3 was successful
• Tom recommends successes in upgrading should be announced in the Google Groups thread announcing the rc3

Which Rubies do/should we support? (Tom Johnson)

Background: Hyrax says: "We recommend either Ruby 2.5 or the latest 2.4 version." We don't specify ruby support in `hyrax.gemspec`, should we? We currently check syntax against Ruby 2.1, preventing use of modern syntax. WIP: https://github.com/samvera/hyrax/compare/ruby-2.3

• Proposal to formalize ruby support to communicate expectations to adopters
• We should support rubies that are not end-of-life
• Lynnette seconds that proposal to update our ruby support to newer version. maybe we need documentation on updating ruby version (i.e. updating travis, rubocop, gemfile, etc.)
• Question for the community: What ought to be our policy re: ruby version support?
• Tom will make a formal proposal on the tech-list for supporting ruby 2.3+, with future versions to drop support for ruby version in end-of-life status; only support ruby versions with security updates or higher
• There is support for this proposal

Hyrax 2.1, SemVer, and You

Required reading: https://groups.google.com/forum/#!topic/samvera-tech/3V-t_7IEpeE

• Should Hyrax 2.1 be 3.0? The changes in 2.1 seem to warrant a major release, but previous discussions indicate that the community does not want more than one major release per year due to the resources required to keep up
• There is no desire to create more friction around this release; however, it might be the useful to adopt SemVer practices to introduce stability now, rather than later.
• 2.1 requires a data migration, and certain methods have been renamed. The extent of the changes depend on the complexity of the customizations made your app.
• Will this take me less than a day of work?
• Takes a day or two to migrate.
• Concern: this conversation being had among highly well-connected developers. This will be much more difficult for developers at smaller institutions who are less up to speed on all of the changes in the stack.
• The proposal to adhere to SemVer is not specific to Hyrax; the community as a whole could benefit from the spec
• We should be able to release new features in backwards compatible ways
• Re: 2.1 – the only change that is not backwards incompatible has to do with admin set ids and collection id; most database changes are backwards compatible (everything related to collections-extensions, at least)
• Recommendation: continue this discussion on the thread
• Proposal: stick to this release as a 2.1
• What is the harm with 3.0? We had this conversation months ago, but it seems clear that the conversation did not come to a satisfactory conclusion
• When all of the technical work is done with 2.1, we should make the call

Agenda for next week:

• SemVer and Hyrax 2.1