Time: 11:00 am, Eastern Time (New York, GMT-05:00)
To join the online meeting:
Indicating note-taker
Two In-Review tickets that need a push forward:
Search index: approaches for configuration and processes
Mailing list messages
Status of In-Review tickets
Soft balls
Kitio Fofack ? Orcid and i18n
Received
|
Bugs (1.11)
Among those present, Benjamin and Jim are limited participants.
Ralph is starting work with search tasks
Andrew starting work with Docker tasks
Mike: Thoughts on documentation for new installation process?
Ralph: The new process is much more straightforward. Mike: A button would be good. Ralph: Not quite.
This is for 1.11 correct? Yes.
Thoughts on when 1.11 may be released? By conference?
Andrew: Rumblings in community that we may have enough content to make a release now. 1.10.1 or 1.11 up for discussion. The dockerization and search updates would definitely be for 1.11.
Mike: If integration testing could be done for the next version, that’s a huge step forward
Ralph: Could use just a little time for the community to play with it more, test it. Especially with big changes like Docker.
Mike: Maybe a release candidate for conference? Or soon, so it’s ready/released for conference? Would like to have the tools to run tests.
Andrew: If we achieve goals of merging search branch and complete dockerization (VIVO, Solr, MariaDB containers) we should have a release candidate.
Don: Looking at doing Maven build via Docker, begin with normal 2 stage (VIVO + Vitro) build.
What are expectations for skills needed to build and deploy for sysadmin vs dev ops? Don: Most people seem to be a combo, should be fine with using Docker and git.
Andrew: You can point Docker toward your modified runtime.properties which gets us toward a single command spin up
Andrew: Ralph, you need any support? Ralph: Nope!
Tickets that need addressed: https://wiki.duraspace.org/display/VIVO/Design+-+External+Search
Two In-Review tickets that need a push forward:
VIVO-1641 - Replace afn:localname / afn:namespace with cross-platform equivalent IN REVIEW - Benjamin Gross ?
Cineca's BlazeGraph integration depends on this
Benjamin and Ralph to review https://github.com/vivo-project/VIVO/pull/96
VIVO-1661 - Merging VIVO-DE community translations into code base IN REVIEW
Latest and greatest from TIB translations
Andrew: this is a classic at this point. Pushes us way forward on i18n support. Kitio left his position for another position at a company :*(
Benjamin: Any tips on how to test this?
Observation: the only files touched that affect anything but the german language is the pom.xml files.
Benjamin: Will check for missing all.properties strings that have been added in english since the time of this pull request
Acceptance tests moved to vivo-community, thanks Jim Blake
How to run it?
Jim: Doing some additional work to make it more useful for the next person that gives it a shot
Jim: I’ve made considerable progress
Search index: approaches for configuration and processes
Huda added this…? Calling out Jim. Jim: Can we use existing code to populate multiple search indexes? Internal + external. Brian Lowe called it hacky, but at least Jim could finish it. Huda said it was silly that application setup code is sitting in the display graph (search indexer configuration). Jim to talk to Huda more about it.
Mailing list messages
ORCiD Integration - Sync - Muhammad Javed suggesting Jim Blake has clues
- Is this a very old version of VIVO? Hard to help until we know.
Next Week: When Androids Dream (codename: androdies) - Huda Khan (PPT version) ( Relegated to next week but feel free to review/give feedback on slides)
Status of In-Review tickets
Benjamin: to answer the question posed for VIVO-1656, yes it is of broader interest because it is a prereq for https://jira.duraspace.org/browse/VIVO-1415