You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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. Brian Lowe
  2. Ralph O'Flinn 
  3. Georgy Litvinov 
  4. Nicolas Dickner 
  5. Michel Héon 
  6. Huda Khan 
  7. William Welling
  8. Don Elsborg 
  9. Benjamin Kampe (star)

Agenda

  1. 1.12 release
    1. Issues reorganized into v1.12 and v1.13 releases in JIRA
      1. https://jira.lyrasis.org/projects/VIVO/versions/15140 (1.12)
      2. https://jira.lyrasis.org/projects/VIVO/versions/15542 (1.13)
      3. Many older issues not assigned a verson. 
        1. 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.

    2. Open pull requests:
      1. https://github.com/vivo-project/VIVO/pulls
      2. https://github.com/vivo-project/Vitro/pulls
    3. Blocker issues - including older issues that we should close if they are no longer reproducible.
      1. issuekey summary issuetype created updated duedate assignee reporter priority status resolution

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

  2. Future of JIRA
  3. Embracing standard approaches
    1. frameworks: Spring / Spring Boot / alternatives
    2. Horizontal scalability
    3. Deployment
    4. Configuration : files / environment variables / GUI settings
    5. Editing / form handling
    6. Adding custom theming without customizing build
  4. 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. 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 on Google Drive



  • No labels