Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Notes

VIVO development Fund was approved. 

VIVO terms of service discussions started, on the Leadership group meeting (the first week of December) it should be discussed further. For some EU countries it is highly required to have different terms of use/service, due to the laws.

Due to Thanksgiving day, the start of the next sprint might be postponed/changed to another date. Information will be provided by Dragan about the new channel, and about the sprint plans in general. 

Last week had lots of PRs. In terms of valueness Georgy’s pull request hugely decreases VIVO loading files (for example: switching data from one VIVO instance to another). Finale speed depends on lots of factors: HDD or SSD, size of model (more data you have, more time it will load). Also some models require a few steps of serialization and deserialization. One more reviewer is needed. 

The i18n redesign sprint (registration link: https://forms.gle/tJT4WHgBeMTT8cKb7): 

  1. Since VIVO-languages will be moved to VIVO, this point is in question. Still lots of work should be done.
  1.   Special tag can be added, because language tag includes private subtag (will be  discussed on the next sprint)
  2. State of VIVO/Vitro-languages after redesign should be discussed. Point is, clients might be confused if in the future there might be some commits. For “moving home artifacts” validation is required. In the next pull requests: pull/348 and pull/3797 everybody is welcomed to test. 

 Dynamic API

People interested in working forward in dynamic API development are welcomed in. 

Drafts ideas for i18n redesign part 2: https://wiki.lyrasis.org/display/VIVO/Sprint+redesigning+2

If you feel that something is missing, don’t forget to write it, or mention on a next meeting.

Draft notes in Google Docs

Task List

  •  All to review PRs assigned to them

Previous Tasks