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. Huda Khan 
  5. Alexander (Sacha) Jerabek (star)
  6. Benjamin Gross
  7. Nicolas Dickner
  8. Sandra Mierz
  9. Georgy Litvinov
  10. Ralph O'Flinn

Agenda

  1. 2021 North American Users Meeting - today @noon ET
  2. Recent development activities?
  3. Next weeks sprint
    1. Add your name to the wiki page 
    2. 2021-01-22 - i18n pre-sprint meeting: @10am ET
    3. Merged!
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    4. Non-i18n bugs to be fixed
      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.
    5. 1.12 release planning
      1. Merge and test of sprint-18n into master: week of Feb 8th
      2. 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
      3. Do we want the `war` install in 1.12? - Unable to locate Jira server for this macro. It may be due to Application Link configuration.
        1. Next steps?
  4. Tickets that should be close to merge
    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. Messaging
    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 

  1. 2021 North American Users Meeting - today @noon ET
    1. Mostly north American, some Europeans
    2. General overviews of who is doing what
  2. Recent development activities?
    1. meeting this Thursday, kickoff of Data Ingest task force, discussion about work on Kafka to date
  3. Sprint planning: 1.12
    1. BG: Maybe useful for the sprint.... but here's the docker container pointing at the i18n sprint branches https://github.com/vivo-community/vivo-docker2/tree/sprint-i18n
    2. 2021-01-22 - i18n pre-sprint meeting: @10am ET
      1. Objective is to pull together i18n work, and prepare next release
      2. Sprint planning kickoff meeting: make sure that people have the environment, branches they need to get work done. Initial round of assignments, assigned tickets
      3. Site admin part has not yet been fully tested
    3. Non-i18n bugs to be fixed
      1. VIVO-1910 - VIVO sitemap.xml broken Open
      2. VIVO-1929 - Site Admin users cannot create new individuals via the GUI Open
    4. 1.12 release planning :
      1.  balance bug fixes above with i18n functionality, vivo-1929 takes priority over vivo-1910. vivo-1910 is the source of some community reported problems, should be put into ‘release blocker’ category. Need to go through tickets to verify which ones need to be included in 1.12 release. Sprint + two following weeks, week after sprint, merge i18n into master branch, may be a good idea even if no all tickets are not yet finished.
      2. RoF: should be pushed out as RC1 instead of having two separate branches
      3. AW: 2 issues: 1. merge i18n into master; 2. Get a release candidate out. Reluctant to publish an RC if there are outstanding bugs.
      4. RoF: preferable to have one branch to deal with
      5. BG: in favor of merging branches once they are cleaned as best possible
      6. AW: then need to figure out how to fill the gap btw state of master vs bug free i18n state, this should be done as quickly as possible
      7. Georgy: would be willing to look at a patch for vivo-1929, need to be familiar with the commits process etc.
      8. BG: Some info on the project's policies for submitting code: https://github.com/vivo-project/VIVO/wiki/Development-Processes
      9. BL: see also https://wiki.lyrasis.org/display/VIVO/Contributing+code+with+a+fork,+branches,+and+pull+requests
      10. AW: basically submit a pull request, issue tracking in JIRA (need login), PR in GitHub should have a link to JIRA ticket, and vice versa
        1. Merge and test of sprint-18n into master: week of Feb 8th
        2. 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
      11. Do we want the `war` install in 1.12? - VIVO-1443 - Decouple VIVO build from installation Reopened
        1. See : https://github.com/vivo-project/VIVO/pull/197
        2. AW: this may not be ready for 1.12, we are hopeful, but someone needs to pick this up
        3. RoF: did Don test this?, others may have looked at it: William, Benjamin, etc. perhaps a turn-over call would be useful to identify a new ‘torch bearer’.
        4. BG: it is a non-starter since I can’t build the application with it.
        5. RoF: we can discuss this on the call
        6. WW: we have discussed this and understand what needs to happen, can work on this and submit some PRs
        7. RoF: if you want to split it up, I could help out
        8. AW: maybe a call is not necessary, can address concerns otherwise (Slack? etc)
        9. BG: would appreciate comments on my comments to make sure that I am not the only one with these concerns
        10. WW: will update the GitHub comments or JIRA ticket to address the concerns (restart should not clear out home directory.) 

Actions

  •  



  • No labels

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