Date
Call-in Information
Time: 11:00 am, Eastern Time (New York, GMT-05:00)
To join the online meeting:
- Go to: https://duraspace.zoom.us/j/823948749
- Or iPhone one-tap :
- US: +14086380968,,823948749# or +16468769923,,823948749#
- Or Telephone:
- Dial(for higher quality, dial a number based on your current location):
- US: +1 408 638 0968 or +1 646 876 9923 or +1 669 900 6833
- Meeting ID: 823 948 749
- International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5
Slack
- https://vivo-project.slack.com
- Self-register at: https://goo.gl/forms/JxQFkut4TYj4Ehww1
- Self-register at: https://goo.gl/forms/JxQFkut4TYj4Ehww1
Development Process
Attendees
Indicating note-taker
Agenda
Review of agenda
- Any pressing issues?
- Java 8, Java 11, and future support (Ralph)
- Landing 2018?
- Any pressing issues?
December sprint - (Dec 3 - 7)
- One week
- Focus
- Introduction to VIVO development (minor clean-up)
- ElasticSearch?
Housekeeping updates from last week
Moving the Advanced Role Management feature forward
Follow-on PRs addressing code review comments:
- Vagrant
- Updating to 1.10 (issue-41) - Don Elsborg?
- Triple Pattern Fragments
- Themes
- Kitio Fofack -
- - may be unnecessary?
- Misc
- Don Elsborg(investigate) & Benjamin Gross(approve?) & Graham Triggs(approve after one more update?) -
- Kitio Fofack ) - minor, need one more review (
- Mike Conlon to review -
In-Review
1.10
bugs (1.10.1?)
Notes
Pre-agenda
WikiCite 2018 - Don Elsborg and John Mark Ockerbloom attending
Per Mike Conlon -- wikidata has no concept of an “authoritative source”
Dec dev call -- Danial Mecham (sp?) from wiki is attending the VIVO dev call
JDK -- per Ralph -- past Jan 2019 - jdk8 no longer supported by Oracle. Next option is JDK 11, since 9 and 10 are not options. Oracle will take over openjdk project and update patches?? ( not sure I heard this right ). So for VIVO we need to dev a policy as to what JDK we support - eg jdk 11 long term. Don - is oracle supporting openjdk Ralph - in a sense yes. Oracle jdk 11 and openjdk 11 should work identicaly except for a couple of minor differences. For 6 months on each release they’ll support patches for both. After that it becomes a leadership thing for openjdk as to how to provide continuing support, for things like security. It does look like Redhat took the lead. Andrew - based on changes Oracle is introducing we should release VIVO against a non-Oracle openJdk.
https://developers.redhat.com/blog/2016/03/31/no-cost-rhel-developer-subscription-now-available/
Ralph - Open ticket for JDK policy
Agenda
All: Think about what to tie up for this year
Dec Sprint
Dec Sprint - Short - 1 week
16 people - many not developed in VIVO before
Focus - Dev Process
Ideas about future processes?
PE - ElasticSearch/Solr Plan for Dev Sprint (Don/Ralph)
Look into Containers - what it might take? (Huda)
(Add to Sprint Page)
Internationalization
Extract English to handle like other languages
Housekeeping of JIRA
Don - Vagrant (https://github.com/vivo-community/vivo-vagrant/issues/41)
Actions
- ...
Previous Actions
- Andrew Woods to submit PR to https://github.com/vivo-community/vivo-vagrant/pull/38 to remove whitespace updates
- Kitio Fofack to work
- Don Elsborg to investigate rationale for retaining two nearly identical propStatement-dataDefault.ftl files in VIVO and Vitro ( )
- Kitio Fofack to review
- Don Elsborg - add jira tickets for abox/tbox use cases - one ticket for each use case
- Brian Lowe - check with ontology group on handles
- Alex Viggio will bring news of Elasticsearch instead of Solr up with Product Evolution.
- Benjamin Gross to create new Jira issue for additional errors thrown startup.
- Don Elsborg - create Jira ticket for data property linking by default
- Don Elsborg - discuss his data property linking pull request with the ontology group