Developers Meeting on Thurs, January 23, 2025

Time/Location

23 Jan 2025 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 9.0 release (see release schedule above)
     1. 9.0 Board is created: https://github.com/orgs/DSpace/projects/31/
     2. Early ideas/brainstorms captured at DSpace Release 9.0 Status
  2. DSpace 8.1 / 7.6.3 releases (Tentative Release Date: Jan 30?)
     1. High Priority bug reported:
        1. Giving someone Workflow privileges (Reviewer, Editor, Final Editor) also gives them submit privileges:  https://github.com/DSpace/dspace-angular/issues/3849
     2. 8.1 / 7.6.3 "To Do" List:
        1.   Restrict Angular SSR to paths in sitemap (https://github.com/DSpace/dspace-angular/pull/3682)
        2. 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) (NEEDS UPDATING BY DEVELOPER)
        3. Exclude search & browse components from Angular SSR (https://github.com/DSpace/dspace-angular/pull/3709) (APPROVED)
        4. Prevent request with page size of 9999 (https://github.com/DSpace/dspace-angular/pull/3694) (NEEDS RE-REVIEW)
        5. Support configurable limit for exporting items (https://github.com/DSpace/DSpace/pull/10030) (NEEDS REVIEW/TESTING)
        6. Processes should only be failed after a Tomcat restart (https://github.com/DSpace/DSpace/pull/10158) (NEEDS REVIEW/TESTING)
        7.   Fix issue where scoped browse throws errors (https://github.com/DSpace/dspace-angular/pull/3845) (MERGED)
        8. (NEW) Browse Performance Fixes (https://github.com/DSpace/dspace-angular/pull/3846) (NEEDS REVIEW/TESTING)
        9. (NEW) Accessibility: Make reorder buttons keyboard accessible: https://github.com/DSpace/dspace-angular/pull/3372 (MERGE CONFLICTS)
        10. (NEW) Accessibility: Support for disabled elements for screen readers: https://github.com/DSpace/dspace-angular/pull/3268 (MERGE CONFLICTS)
        11. (Optional) On error in DOI organizer bulk operations, continue instead of stopping (https://github.com/DSpace/DSpace/pull/9835) (NEEDS REVIEW/TESTING)
        12.   (Optional) Add ORCID icon with tooltip (https://github.com/DSpace/dspace-angular/pull/3345) (NEEDS UPDATING BY DEVELOPER)
        13.   (Optional) Handles versioning for ORCID publications (https://github.com/DSpace/DSpace/pull/9718) (NEEDS UPDATING BY DEVELOPER)
        14.   (Optional) Fix redirect of bitstream URLs with spaces in filename (7.x only) https://github.com/DSpace/dspace-angular/pull/3876 (NEEDS REVIEW/TESTING)
  3. Other topics
     1. (Add other topics here)
• 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)
  
  • 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 coming 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
  • 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 
• Sascha Szott 
• 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

Action items