Date
Call-in Information
Time: 11:00 am, Eastern Time (New York, GMT-04: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
- April Sprint (Sprint JIRA Board)
- Code freeze and Release candidates
- Updates from:
- 1.10 release
- VIVO ontologies
- Multi-Language support
- Slack channels: #sprint1 and #sprint1-1_10-eval
- Email traffic
- Review and testing needed
[VIVO-1470] Cross-platform improvements for Maven
Reviewed by Benjamin. Need a reviewer running Windows ideally
(No Jira issue) Look in vitro.home/config directory for runtime.properties at startup https://github.com/vivo-project/Vitro/pull/63
Reviewed by Jim, need 1 more
VIVO-1458 - Update to Jena 3.6 IN REVIEW
- Reviewed by Sarbajit Dutta, Mike Conlon (reviewing).
- Reviewed by Sarbajit Dutta, Mike Conlon (reviewing).
VIVO-1435 - Compliance with ORCID style guidelines IN REVIEW
- Andrew Woods (approved), Mike Conlon
- Testing issue type for JIRA? (Now available)
- Proposed 2018 sprint schedule. See 2018 Sprint Schedule
- Time-permitting: Security concerns for VIVO (based on issues raised at an institution looking at making its instance based on Vitro public)
Meeting Notes
Sprint began yesterday. Javed update; evaluating combined vivo.owl file. Missing a few labels. In application configuration ontology namespace must be replaced. Will begin on candidate release modules.
Jim uncovered a couple issues: Jena 2 tools fails on export from previous version of VIVO, never even got to SDB content. It happened on a 1.9.3 VIVO that had only been started once. Couldn’t reproduce with Scholars data imported into 1.9.3.
Mike: I didn’t have issues.
Ralph: Will attempt this afternoon with 1.9.3.
Success of Jena tools appears to be data dependent
Problem may be in Jena itself, we would need to interact with them, investigate Jena version.
MySQL Connector version in dev branch has time zone issue
Issue w/ connector has been fixed in later versions
Latest in 5 series, released in Feb has fix. Inclined to use that version rather than 8 which is unproven.
Jim has created a pull request replacing 6.0.6 with a series 5
Ralph: Should we consider the increasingly popular MariaDB instead of MySQL?
Mike: Ontology combined into vivo.owl
Mike plans on making a new commit to the existing pull request
vCard ontology updates
Summary of vCards entities in VIVO: https://docs.google.com/spreadsheets/d/1U4eGaoM3wzbCI9xmbpunLcI0QVhSrwYbbQU_Rgo9OCk/edit#gid=0
Work right now is only analysis, no plans on changing for upcoming release
Preparation of ontology modules for the candidate ontologies/entities to be deleted, Javed will begin work soon
Multi-language support
Meeting yesterday
Kitio pushed some code yesterday to https://github.com/VIVO-CA/VIVO
Andrew: What is the ideal outcome of the sprint with how it relates to the release of 1.10. One goal: Address all blockers currently on board and surface any additional. Mike: If we do that, is that RC1? Andrew: Yes. Would propose a timeline (3 weeks?) for how long RC1 is out in the public for comment before we release.
Deadline for pull request, April 30. Deadline for code freeze May 10th.
Jim: Do we have a timeline for the version following 1.10?
Ralph: Proposes speeding up release cycle, releasing more maintenance releases between major releases.
Jim: Likes the idea but how much effort is required to release something, beyond the code itself (e.g. documentation)
Ralph: For documentation, don’t create new spaces for minor releases, only small release notes in the major version’s space.
Andrew: Recommends documenting the release process.
Javed: Documenting all the changes in the wiki isn’t as trivial as in the code
Discussion about semantic versioning and our current releases… Mike: We eventually want to release VIVO 2. The upcoming release should really be 2 because of the breaking changes. We need end user features to market before branding it 2.0.
Andrew: Version number is all technical. Can we separate out the marketing from the version number?
Can we agree that it’s too late to flip back to 2.0 for this release. YES.
Mike: Version 2 is the hardest because the expectations are high. Gets easier with successive major releases.
Andrew: This relates to agenda item 5, the roadmap.
Email traffic
Unresolved message is anybody able to respond?
Review and testing needed
Andrew: Is Sprint task 1 addressing these PRs? Benjamin: Yes. But we could use help. Andrew: Should have some bandwidth next week if he can help. Benjamin: Perfect because many of the PR authors on also working on the task and can’t review.
Testing issue type for JIRA? (Now available)
Mike added, you can now mark issues as tests. Sub-tasks are uninformative oftentimes. Many tasks are actually tests so Mike created new type.
Proposed 2018 sprint schedule. See 2018 Sprint Schedule (For Discussion)
Should we have monthly sprints that are 2 weeks long each?
Mike - only participate in the ones that you can, no expectation that one person can participate in all.
Mike had heard some feedback that runup time for sprints must be longer for planning
Andrew: Sprints need a leader. Who can lead these? Lets carry this topic over to next week.
Action items
- Type your task here, using "@" to assign to a user and "//" to select a due date
Recent JIRA Tickets
Tickets created in the last 30 days:
Tickets resolved in the last 30 days:
Bugs
