...
- VIVO-release-publisher project
- what should be improved
- license
- decoupling publishing Vitro release and VIVO release
- update of Readme file
- DONE - https://github.com/vivo-project/VIVO-release-publisher
- Will be tested for the next release (run during VIVO committers calls)
- what should be improved
- Duplicated web addresses in the person profile
- The audit module
- The VIVO audit module
- https://github.com/vivo-project/VIVO/pull/3879
- the second reviewer (committer) needed
- Extended search
- https://github.com/vivo-project/VIVO/pull/3860
- should be documented (and presented)
- the configuration example
- the second reviewer (committer) needed
- ABAC (advanced role management)
- https://github.com/vivo-project/VIVO/pull/3887
- a big PR
- the second reviewer (committer) needed
- should be documented (and presented)
- Building process improvements
- https://github.com/vivo-project/Vitro/pull/370
- https://github.com/vivo-project/VIVO/pull/3844
- Should check if works in the case multi VIVO instances are run in one tomcat
- the second reviewer (committer) needed
- should be documented (and presented)
- Codestyle
- https://github.com/vivo-project/VIVO/pull/3840
- review completed
- documented - Code Style Guide
- strategy for merging needed
- CodeQL action
- https://github.com/vivo-project/VIVO/pull/3903
- CI tooling versions for intermediate releases for each CI step
- I forgot my password
- One theme and WCAG compatibility
Notes
Dragan informed committee members that releasing of Vitro and VIVO is decoupled in accordance with discussions from previous meeting - https://github.com/vivo-project/VIVO-release-publisher.
The issue with duplicated web addresses in person profile pages reported via Slack might be already addressed in VIVO 1.14.0. Dragan will continue communication with reporters on the issue.
Dragan briefly presented open PRs, after a short discussion reviewers have been assigned to those PRs. The soft deadline is September 10th.
Georgy explained how potential security vulnerability is prevented in ABAC (advanced role management) PR. Triplets defining role management are not accessible through SPARQL API. Audit module PR is probably compliant with the GDPR (General Data Protection Regulation).
Actions
- All - review PRs assigned to you till September 10th
Previous actions
- Dragan Ivanovic to prepare VIVO 1.14.0 release
- Dragan Ivanovic to prepare release candidate 4
- Georgy Litvinov to align https://vivo.tib.eu/vivorc/ with release candidate 4
- Dragan Ivanovic to respond to slack messages
- Dragan Ivanovic will try to collect wiki pages where strategy, vision and roadmap for development of VIVO were discussed in the past
- Georgy Litvinov will try to address the issue https://github.com/vivo-project/VIVO/issues/3871
- Dragan Ivanovic will ask Michael to open a GitHub ticket for the issue about UF performance during login (https://vivo-project.slack.com/archives/C8RL9L98A/p1684174222986709), Brian Lowe and others can continue discussion about this issue once a ticket is open
- Dragan Ivanovic will ask Rodrigo to open a GitHub ticket for the issue about custom theme and VIVO Docker (https://vivo-project.slack.com/archives/C8RL9L98A/p1684962021101889), William Welling and others can continue discussion about this issue once a ticket is open
- Brian Lowe to open a GitHub issue for index page exception
- https://github.com/vivo-project/VIVO/issues/3867
- add sample (minimal RDF to reproduce the issue)
- Miloš Popović or Ivan Mrsulja to review (https://github.com/vivo-project/VIVO/issues/3862)
- Georgy Litvinov to review (https://github.com/vivo-project/VIVO/issues/3847)
- Review (https://github.com/vivo-project/VIVO/issues/3865)
- Review (https://github.com/vivo-project/VIVO/issues/3864)
- Review (https://github.com/vivo-project/VIVO/issues/3858)
- Review (https://github.com/vivo-project/VIVO/issues/3859)
- Review (https://github.com/vivo-project/VIVO/issues/3855)
- Review (https://github.com/vivo-project/VIVO/security/dependabot/3)
...