...

 Indicating note-taker

1. Brian Lowe
2. Benjamin Gross
3. Georgy Litvinov 
4. Nicolas DicknerHuda Khan 
5. Michel Héon 
6. Georgy LitvinovHuda Khan 
7. William Welling 
8. Benjamin GrossAlexander (Sacha) Jerabek 

Agenda

1. Moving towards RC1
   1. Reverting deployment changes for 1.12
      
      1. https://github.com/vivo-project/VIVO/pull/228
      2. https://github.com/vivo-project/Vitro/pull/217
   2. New issues:

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

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

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

      4. Permissions problems with page management? Others?
   3. Documentation
      

      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

      3. How an End-User Can Use the i18n Using VIVO's Internationalization (i18n) Features
      4. Simplifying end-user/installation instructions while retaining details for developers
      5. Making it easy for people to help with testing : Release Testing - 1.12.0
   4. Other questions
      
      1. Browser plugins that are able to double-submit editing forms? Cause for concern?

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

         How far did we get with this?

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

2. Embracing standard approaches : how do we better align VIVO with other software and make it easier to adopt / install / develop for without having to learn the "VIVO way"?
   1. Possible topics:
      1. Deployment
      2. Configuration : files / environment variables / GUI settings
      3. Frameworks / Spring
      4. Editing / form handling
      5. Adding custom theming without customizing build
3. Post-i18n priorities
   1. VIVO-in-a-box
   2. Ingest / Kafka
   3. Advanced Role Management
   4. Moving Scholars closer to core - next steps

...

1. Status of In-Review tickets

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Notes

1. PRs ready to revert deploy strategy.
1. Testing continued… -Georgy and Nicolas
2. To be reviewed and merged for RC1 -Michel and Brian
3. Close to RC1. - Brian
4. https://github.com/vivo-project/VIVO/pulls
5. https://github.com/vivo-project/Vitro/pulls
6. Some PRs requiring second reviews
2. Some new issues.
   1. Not used anymore. Remove entirely. -Brian
   2. What is the meaning of isomorphic in VIVO? - Michel
   3. Jena checks to determine if it is isomorphic… use of blank nodes… -Brian
   4. Check between new and old not returning expected results -Brian
   1. Not new behavior. -Nicolas
   2. Shouldn’t be a blocker and will look into effort for fix. -Georgy
   3. Is there a known issues page for release? -Michel
   1. Regex not supporting UTC
   2. Manual parsing not considering timezone
   1. Can create and delete but can’t edit by a non root user. -Benjamin
   2. Creating an issue and looking into. -Brian
1. Regression with Remove Portal and Tab resources
2. Should VIVO-1971 be blocker for release? -Brian
3. Date timezone issue not able to format with ‘Z’ as UTC.
4. Page management permissions issues?
3. Documentation
4. Other questions
1. EndNote browser plugin causes VIVO docker deployment to make duplicate requests for form submission
2. VIVO-1910 blocker for release and will take a look at -Brian
3. What version in Jira should we use? -Benjamin
4. Precise queries make everything go faster...

Draft notes on Google Drive

...