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
- Organization proposals
- Split issues into smaller pieces → make smaller PRs ( maybe without creation of new github issue for each PR ) - less conflicts, faster reviews, better commit history
- Two meetings a day (standups with discussions for peope in different 3pm EST and 10pm EST) ?
- Simplier PR template for small sprint PRs ? link to issue, description of improvement
- All issues and PRs are with regular VIVO PRs and Issues. Any way to improve it in future?
- Tickets - https://github.com/orgs/vivo-project/projects/2/views/1
- Ontology
- changes
- restAPI
- REST endpoint
- version
- HEAD or part of url
- minVersion
- restAPI pool (and change in the ontology)
- version
- SolrQuery or SeachEngineQuery
- N3Template
- should that be parameterProvider or not???
- Testing strategy
- Ontology
- Blockers
- PRs - https://github.com/vivo-project/Vitro/pulls
- Documentation - VIVO Dynamic API
Slack stand-up template
[VIVO Dynamic API Standup]
Finished yesterday:
{ticket titles and associated GitHub links}
{AND please include brief textual description}
Working on today:
{ticket titles and associated GitHub links}
{AND please include brief textual description}
Blockers:
{brief textual description}
