Versions Compared

Old Version 3

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version Current

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add notes for today

...

  • (30 mins) General Discussion Topics
    1. Open Repositories 2022 (June 6-9 in Denver). Who is planning to attend? What would we want to plan for DSpace 7 ?
    2. DSpace 7.2/7.3 workshop: Leaning towards holding an online workshop/webinar instead of a workshop at OR2022. 
      3. DSpace 7.2/7.3 talks: Team noted it would be best to have at least one DSpace 7 talk at OR2022 in order to provide an update to the OR community.  Additional talks might be moved online perhaps alongside the online workshop? at OR2022 - What talk(s) are we submitting for OR2022?
    3. Review tentative 7.3 Release Schedule above. This is based on a new 4-month release window, but could conflict with OR2022 plans.
    4. Any assigned 7.3 work needing early discussion?
      1. Additional feedback on Administrative Control Panel: DEMO of third-party webapp for Spring Boot Actuators. Could we use this webapp as our Administrative Control Panel, or should we build our own UI in the Angular UI?
        1. Actuator PR: https://github.com/DSpace/DSpace/pull/8166
      2. Additional feedback on DSpace 7 Versioning with Entities: https://docs.google.com/document/d/1E7_zUse5ojI_N9hks53GS3NGboXKkxkF6ud1lPmcDP8/edit#
        1. Feedback from last week was the high level design looks good.  All agree.
        2. Asked Ben Bosman for a new diagram to outline the use case of two Publications linked via a relationship where Publication A is the review of Publication B.  If Publication B is then versioned into B2, it may be important for Publication A to somehow retain an "original" link to Publication B (as that was the version which was reviewed), even if B2 is now the latest version.
    5. (Other Topics?)
  • (30 mins) Planning for next week
    • Review the Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
    • Review the 7.3 Project Board - Assign tickets to developers & assign PRs to reviewers.
      • Paid (by DSpace project) developers must keep in mind priority. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.
      • Volunteer developers are allowed to work on tickets regardless of priority, but ideally will review code in priority order.

...

  • Discussing Release Support now that 7.x is out
    1. The DSpace Software Support Policy notes that we support the "most recent three (3) major releases" (where a major release is defined by the changing of the first number, e.g. 6.x → 7.x).  This would mean that 5.x, 6.x and 7.x are all supported at this time.
    2. Should we propose to Committers / Governance a change of policy to the "most recent two (2) major releases"?  This would mean that we move to only supporting 6.x and 7.x.

Notes

  • Additional feedback on Administrative Control Panel:
    • Luca demoed the Spring Boot Admin Server user interface.
    • We decided that we'd still like a very basic Angular UI for the "Control Panel".  It should ONLY display the "info" and "health" actuators, which align well with the sort of basic status updates that the old DSpace XMLUI Control Panel had.
    • Anyone who wants more complex "Control Panel" functionality should install/use the Spring Boot Admin Server.  We should add instructions on how to do so, as this is a very powerful tool for anyone who wants more insight into their DSpace site's performance.
    • The old XMLUI Control Panel also included a "Systemwide Alerts" section. However, this needs to be split out as a separate Ticket, as it cannot be achieved with Spring Boot Actuators. It's more an Angular UI task.
  • Additional feedback on DSpace 7 Versioning with Entities: https://docs.google.com/document/d/1E7_zUse5ojI_N9hks53GS3NGboXKkxkF6ud1lPmcDP8/edit#
    • Ben went over updates of the new (edge) use case: two Publications linked via a relationship where Publication A is the review of Publication B.  If Publication B is then versioned into B2, it may be important for Publication A to somehow retain an "original" link to Publication B (as that was the version which was reviewed), even if B2 is now the latest version.
      • Feels that the current design can be extended to support this use case easily
      • Mark W noted that this use case may need to be a separate task .  Start simple and address the edge cases later.  Tim agrees.
      • Andrea said he's not sure it's that hard to achieve this use case, but also says the approach of splitting this up is fine.
    • Updated estimate from Ben of 80-120 hours
    • All agree that the original design is good as-is.  Minor feedback is still welcome on either the ticket (https://github.com/DSpace/DSpace/issues/7937) or the Google Doc.  Development can begin.
    • All agree that the edge case can be a secondary PR later on. However, if Ben finds a way to achieve it easily, it's OK to achieve in the same PR.  As of today though, it seems like it may need more analysis & therefore is not required for the first PR.
  • E2E tests - Needs more discussion of what we mean by this.  Will bring to next week's meeting.