...

1. Ralph O'Flinn
2. Kitio Fofack 
3. Tim Worrall

4. Huda Khan

5. Mike Conlon 
   

6. Muhammad Javed

7. Marijane White 

8. Jim Blake 

9. Benjamin Gross 

10. Don Elsborg
    

11. Andrew Woods

12. Qazi Asim Ijaz Ahmad

13. Martin Barber

Link on Duraspace Wiki:

https://wiki.duraspace.org/display/VIVO/2018-05-01+-+VIVO+Development+IG

Attendees

1. Andrew Woods

2. Muhammad Javed

3. Benjamin Gross

4. Jim Blake

5. Kitio Fofack

6. Mike Conlon

7. Ralph O’Flinn

8. Marijane White

Agenda

Last opportunity to discuss before the retrospective meeting.

1. April Sprint

 

2. (Sprint JIRA Board)

   Updates from:

1.10 release

Benjamin: recommends that it is better to keep the mysql driver maintenance release of mysql driver (5.1.46) instead of the last GA (8.0) release. Benjamin will continue watching security vulnerabilities resolution on mysql driver.
Mike: Mysql should not be exposed at least for VIVO scenario where there should be instead a SPARQL endpoint. The known vulnerabilities of mysql driver might therefore mitigated by the context on VIVO. Here are the links to both rleases of mysql connector-J https://dev.mysql.com/doc/relnotes/connector-j/5.1/en/, https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/

   Distribution API, there is no one against it’s inclusion in the VIVO Code as Graham is absent.

Mike: VIVO is not dependant on Distribution API unless the installation is customized to use it.

Jim: The project is open source so there is no emergency in integrating that API into VIVO since one can always integrate it into his installation.

  There are many pending PR on Vitro/VIVO to be reviewed.

VIVO ontologies

1. 1. 1. 1. Javed VIVO Ontology & ontologies.owl are merged. Migration from VIVO 1.9 to 1.10 has been tested and requires no effort

         2. Mike: any person who seems unsure can give a try

         3. VCard Ontology update will not change anything in the application during this sprint. The work planned on that issue is all done.

Multi-Language support

1. 1. The issue generated PRs on VIVO, Vitro, Vivo-languages and sample-data

   2. Benjamin: The PRs on VIVO-1451 can’t found on the vivo-project repository; Kitio will make sure to put the links in the corresponding JIRA ticket.

2. Tickets In-Review piling up

3. 1.10 PR-freeze and code-freeze

noformat

1. Deadline

1. for

1. a

1. pull

1. request

1. submission:

1. April

1. 30th,

1. 2018

1. 12am

1. PST.

1. 
   *

1. Pull

1. requests

1. submitted

1. after

1. April

1. 30th

1. will

1. be

1. considered

1. for

1. later

1. release.

1. 
   Deadline

1. for

1. Code

1. freeze:

1. May

1. 10th,

1. 2018

1. 12am

1. PST.

1. 
   *

1. Any

1. code

1. that

1. is

1. not

1. merged

1. in

1. dev

1. branch

1. by

1. May

1. 10th,

1. may

1. not

1. go

1. in

1. ver

1. 1.10

1. and

1. will

1. be

1. considered

1. for

1. later

1. release.

1. 1. On-going sprints,

see 

2. 1. see 2018 Sprint Schedule (For Discussion)

3. Production Evolution updates?
4. VIVO Slack... approaching 10k message threshold (at 8.5k)
5. Java versions planning
   1. For reference: Fedora Policy - Supported JVM
6. Huda Khan: Security concerns for VIVO (based on issues raised at an institution looking at making its instance based on Vitro public)
7. ...

Meeting Notes

Draft notes in Google-Doc

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

...

1. 1.    What would be pace the team can commit to ? One sprint each month or each quarter. 

Mike: We can have a flexibility to say a planned sprint is not going to happen. Other participants are interested in coming into sprints but they need a schedule.

Javed: We need a schedule in order to have institutions committed and build the community.There are issues to meet in terms of resources (Sprint leaders, Task leaders, developers) and corresponding task.

Andrew: Having a schedule with no commitment might end up in new participants alone on a sprint.

Kitio: Suggest keeping a ad-hoc mode as we did for the first sprint. 

Notes

...