Date

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:

Slack

Attendees

(star)  Indicating note-taker

  1. William Welling 
  2. Andrew Woods 
  3. Brian Lowe
  4. Benjamin Gross 
  5. Nicolas Dickner 
  6. Georgy Litvinov (star)
  7. Ralph O'Flinn
  8. Huda Khan 
  9. Alexander (Sacha) Jerabek 
  10. Don Elsborg 

Agenda

  1. A new season for the development community
  2. Consolidating i18n into 'main'
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. VIVO Build and Installation Process
    3. digest.md5: Implementation questions
  3. Releasing a 1.12 alpha
    1. Tickets to be resolved
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      8. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Timing
      1. 1.12 alpha-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
    3. Process
    4. Communication
  4. New developments
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  5. Post-i18n priorities
    1. VIVO-in-a-box
    2. Ingest / Kafka
    3. Advanced Role Management
    4. Moving Scholars closer to core - next steps

Future topics

  1. Vitro JMS messaging approaches - redux
    1. Which architectural pattern should we take?
    2. What should the body of the messages be?
  2. Renaming of 'master' branch? (ZDNet, BBC)
    1. Guidance from GitHub 
    2. DSpace has done it
    3. Fedora has done it
    4. Samvera is doing it
  3. Incremental development initiatives
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Tickets

  1. Status of In-Review tickets

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes 

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.

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Actions

  •  



  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.