Developers Meeting on Thurs, June 12, 2025

Time/Location

12 Jun 2025 from 14:00-15: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. Open Repositories 2025
     
     1. OR2025 DSpace Developer Meet-Up and Q&A (Workshop) - Sign up if you'd like to share your work or suggest a topic for discussion!
     2. DSpace at OR2025 - Wiki page of known DSpace-related talks to be presented at OR2025
  2. DSpace & DSpace-CRIS potential merger discussions
     1. DSpace and DSpace-CRIS Planning Groups - wiki pages to follow along with ongoing discussions.
     2. DSpace-CRIS and DSpace Differences  - List of known feature/architectural differences between DSpace 8 and latest version of DSpace-CRIS
  3. DSpace 8.2 and 7.6.4 maintenance releases
     1. Maintenance Board (9.x, 8.x, 7.6.x)
     2. Backporting recent bug fixes.
        1. Frontend fixes flagged with "port to dspace-7_x" and "port to dspace-8_x"
        2. Backend fixes flagged with "port to dspace-7_x" and "port to dspace-8_x"
     3. Release just after Open Repositories?  Tentative Date: Thursday, June 26?
  4. DSpace 10.0
     1. 10.0 Board: https://github.com/orgs/DSpace/projects/32
     2. 10.0 Priorities: DSpace Release 10.0 Status (Depends heavily on a final decision around potential merger with DSpace-CRIS)
  5. Other topics
     
     1. Some PR highlights for board review, if time: -kim
        https://github.com/DSpace/dspace-angular/pull/4434 (+1 already, small)
        https://github.com/DSpace/dspace-angular/pull/4448 (+1 by me, small, important)
        https://github.com/DSpace/DSpace/pull/10820 (ORCID bug fix, important, testers needed)
        
• Board Review:
  • 10.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.
  • Maintenance Board (9.x, 8.x, 7.6.x) - 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)
  
  • Ongoing Discussions (temporarily put on hold until there are updates):
    1. High CPU with DSpace 7 SSR: https://github.com/DSpace/dspace-angular/issues/3110  (This should be alleviated through several SSR related performance improvements in 7.6.3 and 8.1)
    2. Simplifying the Installation Process: https://github.com/DSpace/dspace-angular/issues/3184
  • Discussion: how to keep message catalogues in sync? https://github.com/DSpace/dspace-angular/issues/3334

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 
• Sascha Szott 
• Marsa Haoua 
• Jesiel Viana 
• Scholaris Team

Current Work

Project Boards

• DSpace 10.0 board: https://github.com/orgs/DSpace/projects/32
• DSpace 9.x, 8.x and 7.6.x maintenance 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 10.0

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

Priorities listed at DSpace Release 10.0 Status. 

Goals for 8.2 / 7.6.4

Deadline is TBD for both 8.2 and 7.6.4.  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 schedule

• No meeting next week due to OR/U.S. holiday; next dev meeting scheduled for June 26

Open Repositories 2025

• OR2025 starts this Sunday
• The developers workshop starts this Sunday
  • If you're attending the developers workshop on Sunday and would like to suggest a topic for discussion, please add your thoughts to OR2025 DSpace Developer Meet-Up and Q&A
• Also see DSpace at OR2025 for all DSpace-related presentations at OR2025

DSpace & DSpace-CRIS Merger

• The Technology Planning Group has concluded its review of DSpace-CRIS and DSpace Differences
  • If you see something missing from this page, please add it
• No further updates; no decision as of yet as to the merger
• Strategy Planning Group has submitted a draft of the Strategic Vision Document to Steering

Maintenance Releases

• Internal deadline for release is June 26; this is a tentative deadline, if we see there's more work to be done, we can postpone to early July
• Reviewed backports front-end: 
  • "port to dspace-7_x"
    • #4290: Moving along, coming soon
    • #3276: Assigned to Giuseppe, also coming soon 
    • #2774: Easier to port, will happen after OR
  • "port to dspace-8_x"
    • #4218: Not yet been ported; reminder to work on this if possible
    • #2774: see above
• Reviewed backports back-end:
  •  port to dspace-7_x" 
    • #10688: No movement yet, reminder to 4Science team to please take a look and see if it can be ported
    • #10580: Needs a very small port; Tim may be able to help after OR
    • #9733: Taken care of, needs review
  • "port to dspace-8_x"
    • #10688: see above
    • #9773: see above
• All in all, looking good, just a few outstanding backports; would be great if we can get those in
  • If anything cannot be backported, add a comment to PR or let Tim know directly
• Any bug fixes that we still see out there, we can still get into the maintenance releases

DSpace 10.0 Release

• Status page has been created
• More details regarding priorities will come, feel free to work on bug fixes and improvements in the meantime

10.0 Board

• Lot has been worked on in the past weeks, there is a lot in the "Reviewer Approved" column; they will get merged as much as Tim has time; lot of these are bug fixes
• Can also be approved by other committers – if you are a committer, please consider reviewing and approving them
• Reviewed #4431:
  • Kristof approved Kim's PR; very small, we'll go ahead and merge it and move it forward
• Reviewed #4448: 
  • This should be 1 approval, it's very small; Giuseppe will add comment regarding "defer", was added as reviewer
• Reviewed #10820:
  • Pierre volunteered to test it, will follow up with Kim or add comments on PR itself; Tim can help also after OR
• Reviewed #4019:
  • If possible, would like to get this moved forward relatively quickly (in combination with the other PR)

Upcoming Discussion

• June 26 meeting: will concentrate on maintenance releases
• Will have further discussion on code refactoring at July 3 meeting (4Science and Atmire)

Action items