...
Agenda
- Pressing issues?
- Next release
- Tickets that need help
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1704 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1718 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1723 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1726 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1728 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1729
- Reflection on technical roadmap progress towards Product Direction for 2019
- Short-term development activity
- Extract ontology from core codebase
- Extract languages from core codebase
- Move from 'develop' to 'master' branch
Notes
Clarity on what projects are committer-supported
- Yes: vivo-project
- No: vivo-community
- Review of repos in vivo-project for whether they belong in vivo-project or vivo-community
VIVO Scholars
- Goals (from core committers perspective)
- Interest in bringing VIVO Scholars into core
- Interest in making all ontology fields available
- TAMU's approach towards mapping "all" of the VIVO ontology into a flattened model is very helpful
- We should be able to represent all of the VIVO ontology
- Things we like: UI fed from APIs
- Things we like: GraphQL
- GraphQL over SPARQL: hypergraphql
- What would it look like to update VIVO's Solr to support the scholars-angular interface
- For the sake of a proof-of-concept, the Freemarker UI may be broken
- Obviously, we would not release in such a state
- ACTION: Andrew to draft architectural diagram, including elements such as:
- TPF, Solr, VIVO, Triplestore, UIs, Scholars
- iterate with the team
Statement from Committers
- Would be good to have an articulation from the core committer team
- What we think VIVO is?
- What we think VIVO should be, as it moves forward?
- What is VIVO about?
- Committers want to be a part of the strategic planning process
Actions
- Type your task here, using "@" to assign to a user and "//" to select a due date
...
- Move `develop` to `master` after 1.11.0 release
- Huda Khan to review:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1694 - Brian Lowe to review:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1694 - Ralph O'Flinn to review:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1694 - Andrew Woods to draft architectural diagrams