Date
Call-in Information
Time: 10:00 am, Eastern Time (New York, GMT-04:00)
To join the online meeting:
https://lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09
Meeting ID: 843 7861 5572
Passcode: 556561
One tap mobile
+16699006833,,84378615572#,,,,*556561# US (San Jose)
+19292056099,,84378615572#,,,,*556561# US (New York)Dial by your location
+1 669 900 6833 US (San Jose)
+1 929 205 6099 US (New York)
+1 253 215 8782 US (Tacoma)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
+1 346 248 7799 US (Houston)
877 853 5257 US Toll-free
888 475 4499 US Toll-free
Meeting ID: 843 7861 5572
Passcode: 556561
Find your local number: https://lyrasis.zoom.us/u/kerqtGDrJ4
Slack
- https://vivo-project.slack.com
- Self-register at: http://bit.ly/vivo-slack
Attendees
Resources
Agenda
What went well
What didn’t go well
- What is completed
- What is not completed
- Next Sprint
Notes
Tasks completed in the last two days
WW and KD completed quite a challenging task of generating OpenAPI spec for a certain resource and linked dynamic actions. WW: there is still space for improvements, it is stated in the PR description (https://github.com/vivo-project/Vitro/pull/285). However, we have the first version and PR is ready for review.
DI worked on validation of data content and structure over defined parameter types and validators. There is a space for improvement in validation of type for primitive types, at the current implementation adding a new primitive type in the RDF requires adding Java code for validation. However, we can define a final set of primitive types and expect from dynamic action creators to define complex data structures by combining existing primitive types in objects and arrays. There is a problem in the adoption of SolrQueryTests for a new interface of validation method, VM will help in resolving this issue.
Merging of the sprint branch
DI: should we merge the sprint branch to the main branch? There are cons and pros for merging it now and postponing merging until the next sprint. Conclusion of the sprint participants is to create PR for merging to the main branch, the VIVO committers will decide whether to merge it now or later. Some of the sprint participants are planning to continue working on assigned tasks after the sprint.
Retrospective
What went well
A lot of effort has been invested in the sprint by all participants, some of them even started working on preparation tasks before the sprint. A lot of code contributions were produced, although we don’t have a complete feature at the moment, this is a big step towards that. We had quite good communication, enough meetings have been organized, slack has been used for some discussion as well. Reviewing of PRs has been effective, always completed in some reasonable time, at least two reviewers participated in the reviewing of a PR. We didn’t have so many blocking tasks for a long period of time.
What didn’t go well
We shouldn’t use month for naming branches (https://wiki.lyrasis.org/display/VIVO/Branching+strategy+for+a+sprint+using+GitHub), because some branches might continue to exist for more than one sprint. More balance in reviewing PR is needed, we should encourage non-committers to participate in reviewing. We haven’t been consistent with submitting daily stand-up reports at slack channel. More structured wiki documentation should be created in the preparation of the sprint, to encourage participants to contribute there immediately after completing some tasks. The basic idea of dynamic action has been tested with quite simple and non-real examples of dynamic actions.
What is completed
Around 70-80% of planned tasks have been completed. The first version of the ontology is defined, and its binding to JavaBeen is implemented. Moreover, REST and RCP endpoints have been implemented.
What is not completed
Most uncompleted tasks are in the Execution track (https://github.com/orgs/vivo-project/projects/2), which includes tasks for implementation of the engine for execution of an dynamic action defined in the RDF format. Iterative and conditional steps are not implemented yet. Wiki documentation of developed features are missing. Logging of the execution tasks for debugging of an action in operation is missing (step started, operation started, step ended, etc.).
Next sprint
Probably in May, but will be discussed in VIVO tech group.
