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
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
Agenda
- Questions/Issues/Pull requests/Announcements
- New Year pause for VIVO meetings
- The i18n redesign sprint number two is over
- "hide from display" option
- a month VIVO community meeting
- collecting community needs and requirements
- presentation of new/planned features
- The i18n redesign sprint
- Documentation needs update - Developing a New Interface Language for VIVO
- VIVO demo meeting
- Sprint results - 2023-01-26 - i18n redesigning demo meeting
- or VIVO 1.14.0
- Publishing VIVO 1.14.0 release
- we will start preparation after the sprint
- architecture improvements
- archiving VIVO-languages and Vitro-languages
- i18n improvements
- performance improvements
- faux data properties
- architecture improvements
- we will start preparation after the sprint
Notes
- Organization of next VIVO-meetings during holidays season, proposal - cancel, and have the next meeting on 3rd January, or for the next few weeks have a bi-weekly meeting, and after get back to a regular schedule of weekly meetings.
- I18n redesign sprint part 2 is over, but the few cleaning to make merges are needed to be made. There are few pull requests regarding i18n redesign (one is a big one).
- Feature “hide from display” can be implemented but with changes of now architecture. Few points user might want to have private from others, or from other group, that are not connected with his.
- New format of monthly meetings, where not developers might take action and tell about features they want to see in a future. Points are to make it not only for developers, but also for others, and to split this meeting with around 50/50 technical and non-technical meetings. First one will take a test and see if it’s needed. Presentations, slides and basic information is welcomed to be shown here. Mostly telling different modules of VIVO, such as authorization, search, uploads.
The main point is this should not be too technical (depending on the user’s level). Might be a kind of getting feedback from the users of VIVO. - Other small PRs will be reviewed, before new 1.14 VIVO version.
Task List
Previous Tasks
- Brian Lowe to review https://github.com/vivo-project/VIVO/pull/3788 and https://github.com/vivo-project/Vitro/pull/341 preferably by end of the week (11/25/2022)
- Brian Lowe to review https://github.com/vivo-project/Vitro/pull/347
- Michel Héon to validate https://github.com/vivo-project/Vitro/pull/347 and test performance with remote Fuseki
- Anyone to validate https://github.com/vivo-project/Vitro/pull/348 and https://github.com/vivo-project/VIVO/pull/3797 preferably by end of the week (11/25/2022) - description how it should be validated provided in the PR description
- Benjamin Kampe to review https://github.com/vivo-project/Vitro/pull/349 and https://github.com/vivo-project/VIVO/pull/3795 preferably by end of the week (11/25/2022)
- Dragan Ivanovic to create PR in cooperation with Michel Héon for merging ttl files (labels' translations) into Vitro/VIVO repositories
- Dragan Ivanovic to ask Arif for more info on the reported issue - https://groups.google.com/g/vivo-tech/c/gmyQIMWbm_Y
- Dragan Ivanovic to open a ticket for https://groups.google.com/g/vivo-tech/c/wDblxLmeTjs. Done, ticket available at https://github.com/vivo-project/VIVO/issues/3772
- Dragan Ivanovic will redirect reporter of this issue https://github.com/vivo-community/vivo-docker2/issues/22 to https://github.com/vivo-project/VIVO#docker
- All to analyze the issue reported in the slack (https://vivo-project.slack.com/archives/C8RL9L98A/p1663253504895989) and check whether we should open a GitHub issue and add to the i18n redesign project board - https://github.com/orgs/vivo-project/projects/4
- Brian Lowe will respond on the email https://groups.google.com/g/vivo-tech/c/5AY9h15h4vc/m/OjqekVxlBgAJ?utm_medium=email&utm_source=footer&pli=1
- All to consider participation in the sprint and register via https://forms.gle/qLi1PhRrrpvUrrYRA
- Dragan Ivanovic to work on specification of tasks for the sprint - GitHub project board
- Michel Héon to work on the translation messages ontology
- Dragan Ivanovic will bring up with leadership group that we would like to set up task force for dynamic API
- Dragan Ivanovic will create infrastructure for the next sprint (slack channel, GitHub project board, wiki page, GitHub branch, GitHub issues, etc.)
- Michel Héon to work on the ontology for UI labels (in multiple languages)
- All to think about dates for the next sprint
- Dragan Ivanovic to resolve conflicts for https://github.com/vivo-project/Vitro/pull/311 and https://github.com/vivo-project/Vitro/pull/297
- Dragan Ivanovic to write script for preparing a release candidate - started at https://github.com/chenejac/VIVO-release-publisher
- All to test the release candidate - Release Testing - 1.13.0
- Dragan Ivanovic to publish VIVO 1.13.0 release (if there is no reported issue till 1st of September)
- Dragan Ivanovic to prepare presentation for demo meeting - 2022-07-07 - Dynamic API demo meeting
- Dragan Ivanovic to send reminder for the demo meeting - 2022-07-07 - Dynamic API demo meeting
- Dragan Ivanovic to open an issue for a reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
- Dragan Ivanovic to contact Andrew Wood for resolving the issue with registration for the Slack channel
- All to consider participation in the sprint and if decide to participate to register for the sprint - link
- Dragan Ivanovic to send a require to add in the Leadership group agenda a topic for discussing Copyright owner in License
- All please help in filling this document - spreadsheet
- Dragan Ivanovic to create a draft version of a Google Spreadsheet document with labeled columns representing requirements and to share with committers
- Committers to review the structure of the document and to fill it with data for JS and CSS frameworks