Date

24 Apr 01 May 2018

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-04:00)

...

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

4. Huda Khan

5.  

6. Mike Conlon 
   

7. Muhammad Javed

8. Marijane White 

9. Jim Blake 

10. Benjamin Gross 

11. Don Elsborg
    

12. Andrew Woods

13. Qazi Asim Ijaz Ahmad

14. Martin Barber

Agenda

Agenda

Last opportunity to discuss before the retrospective meeting.

April Sprint 

1. April Sprint

2. (Sprint JIRA Board)

   Updates from:

1.10 release

...

...

Ralph: 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. Ralph 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

1. Deadline for a pull request submission: April 30th, 2018 12am PST.
   * Pull requests submitted after April 30th will be considered for later release.
   Deadline for Code freeze: May 10th, 2018 12am PST.
   * Any code that is not merged in dev branch by May 10th, may not go in ver 1.10 and will be considered for later release.

1. 1. On-going sprints, see 2018 Sprint Schedule (For Discussion)

         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

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

...