...
- Chris Colvard has added CircleCI to a number of projects in order to support Rails 5.2 across components
- With this has come the CircleCI Orb: https://github.com/samvera-labs/samvera-circleci-orb
- Samvera is on a trial for CircleCI's new pricing structure
- This is hourly (as opposed to the number of boxes/containers used during the testing)
- We have 200 boxes and they track the amount of time which we use
- If the pricing is acceptable after this trial, the enhanced performance might remain the standard
- Otherwise, we might need to revisit how best to restructure build matrices (in order to avoid queuing delays)
Proposals for Other Work:
- Bess: active-fedora
- https://github.com/samvera/active_fedora/pull/1294
- This is blocked by hydra-head (and a few other dependencies)
- The value added is that the generators between Hyrax and Blacklight create different configuration directories for Solr
- We need to ensure that the directory structure does not conflict with the Blacklight-generated config. directories internally
(Waffle.io migrated to GitHub Projects successfully)
- It appears that GitHub Organizations can, themselves, have Projects
- There are issues from multiple repositories on the Organization Project
- There are usability difficulties when searching through the issues for the Project
- We still would need to manually add the issue cards for the board
- samvera/hydra-derivatives cannot link to the samvera-labs Project
- We could create samvera/maintenance as an Organizational Project
- Zube: Cannot One cannot add repositories from Organizations users don't own
Sprint Planning
- We are still not fixing bugs, and are just focusing upon maintenance issues
- hydra-head Issues
- Use `solr/conf` rather than `solr/config` when ActiveFedora changes
- Might be best to fix ActiveFedora before addressing this in hydra-head
- Integrating CircleCI for Core Components
- noid-rails
- hydra-pcdm (this already has
...
- an outstanding PR)
- The list of components will be completed after this meeting has been concluded
- Consider test coverage tickets for another sprint
- Ensure that desired Ruby/Rails versions are used in testing
Hydra Gem Mailing List Thread (samvera-tech)
- Adopters should be encouraged to avoid using the hydra Gem
- The Gem was deprecated, but it is clear that others can maintain a deprecated Gem
- Mark will respond to the thread
Meeting was adjourned at 12:38PDT/15:38 EDT
...