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
What went well
A lot of effort has been invested in the sprint by all participants. Participants even started working on preparation tasks before the sprint, one week before the sprint we organized daily one-hour meetings. A lot of code contributions were produced, although we still don’t have a complete feature, a big step towards that was made. We had good communication via Slack and daily synchronization meetings.
What didn’t go well
We are still using a sprint branch with month in its name, which is confusing (https://wiki.lyrasis.org/display/VIVO/Branching+strategy+for+a+sprint+using+GitHub). We haven’t been so effective in reviewing PR as in the previous sprint. More balance in reviewing PR is needed, we should encourage non-committers to participate in reviewing. Still, we have complex and new tasks which need design decisions (UI, validation, introducing security, etc.), which is introducing a problem of incorporating new members in the community. We hope for the next sprint there might be small, isolated tasks which might be easily resolved by new community members. Work completed in this sprint has not been documented at all. We might have a half of the first week for planning/designing solution, two weeks for coding, and last half a week for wrapping up the sprint (reviewing PRs, documentation, preparation of demo meeting, etc.).
What is completed
Around 50-60% of planned tasks have been completed. The first elements of UI have been developed, endpoint for logging to the system, validation of a dynamic action, conditional steps, computation of required parameters, and a couple of examples of resources with CRUD REST endpoints.
What is not completed
Authorization is not implemented, there is a need for further development of UI components, SHACL rules for validation might be improved as well, iterative steps are not implemented yet, flow for processing of IO data should be redesigned.
Next sprint
Probably in September, but will be discussed in VIVO tech group.
