...
Samvera Connect 2019 and the Developer Congress
- Richard provided a "Companion Events" link to the Developer Congress page on the Confluence
- Organizers should still announce the Developer Congress to the tech. mailing list
- Also, listing the organizers on the page would be best
- Richard emphasized that we clarify that this is not a part of Samvera Connect 2019, and that this is a separate event
- Trey will draft the e-mail
- Point of contact for those who are interested in participating?
- Just list the Slack Channel as the primary mechanism for contact
- Chris, Tom, and LaRita were the original volunteers for organizing the event
- Adding the names as organizers to the e-mail will be addressed
Samvera Documentation WG Rejuvenation
- Drew is the product owner and chair of the Documentation WG
- It has had various successes throughout three years of progress
- There are still some issues which need to be addressed
- Reviving the group in order to address documentation issues in preparation for the Developer Congress
- The documentation is likely going to be a part of what is required for assisting development efforts for the Congress
- The site itself is a Jekyll site (static site generator)
- Only the GitHub repository should be used to publish the site
- Would like to reorganize the content - choose a theme which was is now not ideal for the requirements of the site
- Would like to explore dumping the theme
- Drew will organize this and create tickets
- https://github.com/samvera-labs/samvera_docs will be where the work is continued
- Component Maintenance WG will be contacted in preparation for the migration to the new theme
Next Scheduled Samvera Tech. Call
- Moderator: LaRita
- Notetaker: James
Call concluded at 09:24 PDT/12:24 EDT
...
- Chris Colvard
- Gordon Leacock
- James Griffin
3760
- Still waiting on Julie Allinson
3839
- Sprinters still working on Wings
3881
- Covered by the Hyrax WG
- It has been reviewed
- Tom asked for changes
3764
- Chris will be undertaking a review
3479
- Needs another review
3899
- Anyone can review this now, not just Tom
...
- Brings Hyrax up to Rails 5.2
- CircleCI build restructured into two different workflows
- In the Gemfile.lock, Rails, when generating internal test app., hard-coded a Rails version into the test app.
- This really couldn't be addressed without using workspaces between jobs (otherwise the invalid Gemfile.lock would be persisted)
- Trying to make the tests pass with a new release of hydra-editor with simple_form updates with Rails 5.2 has been the challenge
- simple_form was using #to_model which
- Also before_destroy: remove! was creating problems
- ActiveRecord in earlier Rails was throwing StatementInvalid where it should have been throwing more specific errors
3907
- This should be closed in favor of https://github.com/samvera/maintenance/issues/27
3908
- This might be a Hyrax WG issue
- Inclined to leave them for the WG
- Test failure may have been a flapping test, Chris is rerunning the build
- It was indeed a flapping test
- This still needs a review
- Different solution might be to permit users create a TransferRequest when FlipFlop has transfer works is enabled
- Defer to someone in the Hyrax WG
3909
- 3762 became stale
- user_id and grantee_id HTTP request parameter parsing raised some questions
- Also questions regarding `head :ok` statements
- Is a modal preferable to a flash message?
Non-Hyrax Pull Requests
- (Nothing was proposed)
Session concluded at 09:49 PDT/12:49 EDT
...