...

1. Release candidate 3
   1. https://github.com/vivo-project/VIVO/issues/3847
   2. https://github.com/vivo-project/VIVO/issues/3848
   3. https://github.com/vivo-project/VIVO/issues/3849
   4. Codestyle Vitro, Codestyle VIVO
   5. Readme file
   6. License
   7. Changeset user info
2. Jena 4 upgrade
   1. https://github.com/vivo-project/VIVO/pull/3836 https://github.com/vivo-project/Vitro/pull/368
   2. https://github.com/vivo-project/VIVO/pull/3845 https://github.com/vivo-project/Vitro/pull/374
   3. https://github.com/vivo-project/Vitro/pull/379
   4. https://github.com/vivo-project/Vitro/pull/380
      
      1. interface of scripts
      2. position of script files in codebase
         1. example.dump-restore-script.sh or dump-restore-script.sh
      3. position of script files in VIVO/Vitro home
      4. extraction from war file
3. Building/installation improvements
   1. https://github.com/vivo-project/Vitro/pull/370
   2. survey - https://docs.google.com/forms/d/1-4DDY48Lb2n1hvj5Vka0Of5uZrktkoArFEPZ8NcbvqU/edit

Notes

1. Release
1. Discussion of newly-opened issues to be resolved.
2. Should new codestyle files be merged in 1.14?
1. Will do later when we have strategy for enforcing in pull requests.
3. README: Use generic documentation link so we don’t need to update the link for each version?
1. Seems like the best solution.  Brian will check the text.
4. ChangeSet user info PR will be merged for next release.
2. Jena 4 upgrade
1. Great work from Kevin during sprint but needs to be continued.
2. Brian will find time in coming weeks to work on this.
3. Dump/restore script
1. Dragan: Should some settings continue to be specified in the script itself vs. command line parameters?
1. Brian: would be nice to have them all specified the same way.
2. Dragan:  Args currently depend on position, not flag like -p -u.
3. Brian: Seems error prone; maybe move all to config file / environment vars?
2. Dragan: Where should script go?
1. Georgy: /bin directory?
2. Dragan: Problematic because of git ignore.
3. Dragan: If in vivo.home, need to be careful not to wipe out existing dumps on redeployment.  Will need to think more about these issues before including.
4. Building/installation improvements
1. Dragan will wait a day or so for comments about deployment practices survey, then will distribute more widely
5. Dynamic API + JS frontend
1. Is Angular still the frontrunner?
2. William:  Could be, but also depends on whether we want to dive into a static UI or make it dynamic with ontology defining UI on the backend
3. Brian would be interested in starting to draft that ontology with current UI features as a starting point.
6. Dynamic API meeting time may need to be shifted again because new time is very early in Texas. 
1. Will discuss offline on Slack.

Draft notes on Google Drive

...