Date

11 Dec 2018

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 
    

Development Process

• See https://github.com/vivo-project/VIVO/wiki/Development-Processes

Attendees

 Indicating note-taker

1. Kitio Fofack 
2. Ralph O'Flinn 
3. Andrew Woods
4. Mike Conlon 
5. Benjamin Gross 
6. Brian Lowe 
7. Steven McCauley 
   
8. Svantje Lilienthal
   

Agenda

1. Review of agenda

   1. Any pressing issues?

2. Sprint update

   1. i18n
   2. Externalized search
   3. Product evolution
   4. Misc

3. Design / Contribution process for larger features

4. Tickets that are looking for a shepherd:
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

5. Housekeeping updates from last week

   1. Moving the Advanced Role Management feature forward

      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      2. Follow-on PRs addressing code review comments: Jim Blake / another to review

         1. https://github.com/vivo-project/Vitro/pull/94

         2. https://github.com/vivo-project/VIVO/pull/95

   2. Themes
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Thanks,Kitio Fofack! We need one more reviewer
   3. Misc
      
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Don Elsborg(investigate) & Benjamin Gross(approve?) & Graham Triggs(approve after one more update?)
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Can anyone reproduce or further describe this bug? Graham Triggs ?

6. In-Review

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

7. 1.10 

   1. bugs (1.10.1?)

      Click here to expand...

      type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
      Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes 

Draft notes in Google-Doc

Actions

• Don Elsborg to post data property linking pull requests to develop Slack channel. 
• Don Elsborg to approach ontology group with additional identifier properties they created for CU instance
• Brian Lowe  confirm LDF server issue with TDB content stores
•  

Don: TODO 

Previous Actions

• Andrew Woods to respond to mailing list: "fresh 1.10 release install crashing with..."
• Mike Conlon to address:   Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Don Elsborg to update vagrant for 1.10
• Don Elsborg to investigate rationale for retaining two nearly identical propStatement-dataDefault.ftl files in VIVO and Vitro ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )
• 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.