...

1. Mike Conlon
2. Brian Lowe
3. Huda Khan
4. Benjamin Gross
5. Ralph O'Flinn
6. Andrew Woods 

Agenda

1. Pressing issues?
2. Next release
3. Tickets that need help

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1704

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1718

   3. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1723

   4. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1726

   5. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1728

   6. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1729

4. Reflection on technical roadmap progress towards Product Direction for 2019
5. Short-term development activity
   1. Extract ontology from core codebase
   2. Extract languages from core codebase
   3. Move from 'develop' to 'master' branch

Notes 

Clarity on what projects are committer-supported

1. Yes: vivo-project
2. No: vivo-community
3. Review of repos in vivo-project for whether they belong in vivo-project or vivo-community

VIVO Scholars

1. 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
2. GraphQL over SPARQL: hypergraphql
   • https://www.hypergraphql.org/
3. 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
4. ACTION: Andrew to draft architectural diagram, including elements such as:
   • TPF, Solr, VIVO, Triplestore, UIs, Scholars
   • iterate with the team

Statement from Committers

1. 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?
2. 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