...

1. William Welling 
2. Andrew Woods 
3. Brian Lowe
4. Benjamin Gross 
5. Nicolas Dickner 
6. Georgy Litvinov
7. Ralph O'Flinn
8. Michel HéonHuda Khan 
9. Benjamin Kampe
10. Alexander (Sacha) Jerabek 
11. Don ElsborgBruce Herbert  

Agenda

1. A new season for the development community
2. Consolidating i18n into 'main'
3. Open email threads
4. Sprint updates
   Release blockers:Needing additional testing/review

   1. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1958

   2. VIVO Build and Installation Process
   3. digest.md5: Implementation questions
5. Releasing a 1.12 alpha
   1. Tickets to be 1814

   2. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1929

   3. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1947

   4. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1443

      1. vivo-custom-webapp PR-3
   Needing to be worked / resolved

   1. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1762

   2. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-

      1914

      1802

   3. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-

      1921

      1814

   4. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-

      1941

      1914

   5. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-

      1950

      1941

   6. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-

      1956
   Tickets that will hopefully have PRs in the next day or two:

   1. 1950

   2. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-18221956

   3. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1834

   4. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1928

   5. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1957

   5. All tickets that are targeted for the i18n Beta must be resolved and merged this week
   6. Merge of `sprint-i18n` to `main` at the beginning of next week (week of Feb 8th)

   7. 1. 1959

   8. Timing
      1. 1.12 alpha-1
      1.12 release planning
      1. 1.12 release candidate #1: Feb 15st
         1. Two week RC-1 testing period
         2. For each subsequent RC-2 (if required), adding another two weeks to the schedule
6. Potential patch releases?

   1. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1950

7. 1. Process
   2. Communication
8. New developments
   Tickets that should be close to merge

   1. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-16521436

   1. Post-i18n priorities
      1. VIVO-in-a-box
      2. Ingest / Kafka
      3. Advanced Role Management
      4. Moving Scholars closer to core - next steps

   ...

   Draft notes in Google-Doc 

   
   

   As Andrew is leaving Zoom links are going to be changed.

   Significant milestone is going to be achieved with the merging of vivo-1958. Brian reviewed and tested new changes. Ralph was doing sanity checking. Checked new building process. Checked on multiple systems like Windows, Mac and Linux, multiple browsers. Ralph is working on checking i18n.

   1. I18n Pull requests

   Andrew asks about pull requests.

   Either merge PR today or get some feedback on them. Some tickets on hold because of them.

   Ticket 1958 should help with testing new functionality.

   No code review expected at this point. There already have been code reviews.

   Need basic testing.

   William will try to test, at the same time VIVO needs a lot of resources for testing. 

   2. Digest file

   Diest file is now being created. The idea is now with 1959 we copy war file in tomcat. When tomcat starts VIVO Home directory got populated with war contents. As a part of that VIVO creates an md5 base file. With tomcat restart digest file is being read to find changes since last startup with files in VIVO Application. If files in war and on disk differ then files in home directory rewrites only if they were not changed. Digest file gets updated every time VIVO restarts. 

   On restart it recreates files map with md5.

   Only untouched files are getting overwritten. 

   If somebody want to look at this - you are welcome.

   Benjamin says it works good.

   3. Tickets to be closed
   

   Ticket 1802  Nicolas says it is expected behaviour. Ticket should be closed.

   4. Putting out alpha release

   We want to ensure users can upgrade. Upgrade should work with i18n and without it.

   People in both scenarios should have upgrade instructions without issues.

   All 1958 dependencies should be resolved shortly.

   Merge all by the end of the week.

   Reshuffling of RDF is ok for now as it doesn’t create any problems.

   Given the pace of things Andrew wont be able to push Alpha and RCs.

   Timing, Process, Communication with community 

   Release on monday or next week ? Release alpha by the end of next week.

   Send announcement for the community that alpha is ready, test it.
   

   Encourage testing! A day for extensive testing RCs after internal testing alpha.

   Advanced role management

   VIVO-1436 It was targeted against main. Could have merge conflicts after 1958.

   It could not be merged in 1.12 at this stage.

   Plan for merging after 1.12, maybe release in 1.13

   Misc

   Publish docker container on docker hub to simplify using VIVO.

   Individuals removal

   George proposed a new configuration property (for example, display: hasDeleteQuery) to associate an ontology class with a query to retrieve dependent individuals to be deleted along with the target individual when it is deleted.

   • Jira
     server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1962

   Actions

   •