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

Compare with Current View Page History

« Previous Version 2 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. Georgy Litvinov 
  3. Nicolas Dickner 
  4. Michel Héon 
  5. Huda Khan 
  6. William Welling
  7. Benjamin Gross(star)

Agenda

  1. How can we make a push to get to RC1?
    1. Open pull requests:
      1. https://github.com/vivo-project/VIVO/pulls
      2. https://github.com/vivo-project/Vitro/pulls
    2. New issues
      1. Additional thoughts/results about precise subquery default for TDB or not?
    3.  Release Testing - 1.12.0
      1. How can we encourage community testing?
      2. Can we simplify documentation for new users?
    4. Documentation
      1. How an End-User Can Use the i18n Features
      2. Simplifying end-user/installation instructions while retaining details for developers
    5. Blocker issues
      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. 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

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