Developers Meeting on Thurs, Nov 7, 2024

Time/Location

07 Nov 2024 from 15:00-16:00 UTC

Location: https://lyrasis.zoom.us/my/dspace?pwd=RTk4QUhISnhPRi9YenVrTFJKbDllQT09 (Meeting ID: 502 527 3040).  Passcode: dspace

• More connection options available at DSpace Meeting Room

Agenda

• Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it. 
  
  1. DSpace at OR2025 - Open Repositories 2025 Call for Proposals. Proposals Due on December 18.
  2. DSpace 9.0 release (due April 2025)
     1. 9.0 Board is created: https://github.com/orgs/DSpace/projects/31/
     2. Early ideas/brainstorms captured at DSpace Release 9.0 Status
  3. Ongoing Discussions:
     
     1. Incentivizing Code Reviews and PR Testing
     2. High CPU with DSpace 7 SSR: https://github.com/DSpace/dspace-angular/issues/3110
     3. Using both public/private REST API URLs for better performance (Frontend PR: https://github.com/DSpace/dspace-angular/pull/3358, Backend PR: https://github.com/DSpace/DSpace/pull/9856)
     4. Simplifying the Installation Process: https://github.com/DSpace/dspace-angular/issues/3184
  4. Other topics
     1. (NEW) DSpace 8.0 sometimes gets "stuck" on the loading image ("Infinite load times when editing or browsing") https://github.com/DSpace/dspace-angular/issues/3584
     2. New possible performance fix (needs testing): https://github.com/DSpace/dspace-angular/pull/3585
• Board Review:
  • 9.0 Project Board - Review PRs collaboratively or Assign new PRs to volunteers to code review and/or test.
  • Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
  • 8.x and 7.6.x Maintenance Board - Known bugs can be found here, along with any backported bug fixes.
• Upcoming Topics: (Let us know if there are topics you want to discuss in future weeks)
  
  • Discussion: how to keep message catalogues in sync? https://github.com/DSpace/dspace-angular/issues/3334
  • Discussion/proposal around refactoring and simplifying Live Import and External Data frameworks: https://github.com/DSpace/DSpace/issues/9758
    (nothing concrete yet but would be great to get thoughts added to this issue and maybe find some collaborators)

Attendees

• Tim Donohue 
• Holger Lenz 

• Art Lowel (Atmire) 

• Andrea Bollini (4Science)

• Giuseppe Digilio (4Science) 
• Paulo Graça
• Mark H. Wood 
• Grazia Quercia (4Science)
• Corrado Lombardi (4Science) 
• Julian Timal (eScire) 
• Martin Walk 
• Melissa Anez 
• Oliver Goldschmidt 
• Hrafn Malmquist 
• Pascal-Nicolas Becker 
• Pierre Lasou 
• Kim Shepherd 
• Nicholas Woodward 
• Regrets: Scholaris Team

Current Work

Project Boards

• DSpace 9.0 board: https://github.com/orgs/DSpace/projects/31
• DSpace 8.x and 7.6.x board: https://github.com/orgs/DSpace/projects/29

To quickly find PRs assigned to you for review, visit https://github.com/pulls/review-requested  (This is also available in the GitHub header under "Pull Requests → Review Requests")

Goals for 9.0

To be decided by DSpace Steering Group with feedback from Leadership Group. 

Early brainstorms at DSpace Release 9.0 Status.  Please feel free to add your own brainstorms or link in tickets that you wish to be considered. 

Goals for 8.1 / 7.6.3

Deadline is TBD for both 8.1 and 7.6.3.  Bug fix releases do not have fixed/scheduled deadlines. Instead, the developer team will determine when to create a release based on the significance of the issues to solve. (e.g. If major issues are fixed, then a bug fix release will occur more rapidly.  If minor issues are found, then a bug fix release may be delayed until sufficient fixes have been made to warrant a release)

• Bug/security fixes only.  These minor releases will not include any new features.
  • New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
  • Accessibility fixes are also allowed in bug fix releases, provided they don't significantly modify component behavior or similar.
• Bug fix PRs should be created against "main" branch where possible. The "main" branch has the most strict code style rules. (i.e. PRs created against dspace-7_x  are becoming more difficult to port forward.)
• Per our support policy, bug fixes are only guaranteed to be ported back to 8.x.  That said, where possible, we'll try to backport bug fixes (especially significant ones) to 7.6.x.
  • Keep in mind, if a specific bug fix is important to you in 7.6.x, then it is best to create two PRs (one for main and one for "dspace-7_x").  If you are able to provide a backport version of the PR, then we will merge it alongside the "main" branch version.
  • NOTE: In many scenarios, a backport to "dspace-8_x" should be possible to automate using the "port to [branch]" labels & the "Port merged Pull Request" GitHub Action

Try "Pull Request Trading" for a quicker review

Do you have a PR stuck in "under review" that you really want to see move forward?  Or maybe it's someone else's PR but you want to get it more attention?

See Trading reviews on Pull Requests for how to get immediate attention to that PR!

Notes

Dev Meeting Time

• Due to Daylight Savings Time, our meeting time is now 15:00UTC until March 9, 2025

Discussion Topics

• OR2025 proposals are due Dec. 18
• Please add new ideas for presentations, workshops, etc. or feedback to the wiki page 

9.0 Release Schedule

• We are aiming for the 9.0 release to come out in April 2025
• See the current Release Schedule at 2024-11-07 DSpace Developers Meeting
• Any thoughts, feedback or ideas regarding the 9.0 release schedule, feel free to let Tim, Holger or any Steering member know
• Concerns were expressed that the April timeline is too tight for a major release
  • 9.0 will be a smaller, transitionary release on purpose, which will allow a full year of development time for 10.0; therefore, it is important that we stick to the April 20205 release date timeline

Priorities for 9.0

• There are still plenty of tickets that need to be claimed which address 9.0 priorities as listed on the DSpace Release 9.0 Status page
• Priorities listed on the wiki page marked with a green checkmark have been completed
• Anything that is currently on the list for 9.0 development that will not be completed by April 2025 will be pushed to 10.0 or 11.0

Ongoing Discussions

• Call for testers: PRs from 4Science Team were updated by Giuseppe, they are ready for testing (#3358) 
• Additional topics were added to the agenda which relate to the High CPU ongoing discussion issue
  • Some sites are seeing an "infinite load time" when editing an item or browsing DSpace – it seems like the DSpace UI gets "stuck" (#3584)
    • Assigned to Art
  • New possible performance fix (#3585) – would be great to get this PR in and see if it helps with the infinite loop issue
    • Assigned to Giuseppe
  • Pierre will test the tickets and see if they fix the problem

9.0 Project Board

• Purpose of reviewing tickets together is to get people comfortable with the process; if you have time, please continue to work on tickets in the "needs reviewers assigned" column
• Reviewed #9718
  • Code looks good
  • Would be good to have a manual test and an automated test added
  • If anyone is using ORCID and item versioning and wants to make sure this is synchronizing properly, please test this
• Reviewed #3224
  
  • Code looks reasonable
  • Need someone to test this, please volunteer if you can test this (easier test: only on Angular UI)
• Reviewed #3225
  • Claimed by Tim and Mark to test this

Action items