Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

Developers Meeting on Thurs, September 4, 2025

Time/Location

 from 14:00-15:00 UTC

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

10.0 Release Schedule (TENTATIVE - Not Finalized)

  • New Feature Development Deadlines
    • Feature PR Creation Deadline: Friday, February 20, 2026
    • Feature PR Review/Test Deadline: Friday, March 13
    • Feature PR Merge Deadline: Friday, March 27
  • 10.0 Release Candidate:  Friday, April 3
  • 10.0 Testathon: April 6-17 (two weeks)
  • 10.0 Translation updates: April 6-17 (during Testathon)
  • Bug Fix Deadlines
    • Bug Fix PR Creation Deadline: Friday, May 1
    • Bug Fix PR Merge Deadline: Friday, May 15
  • Documentation & Release Week: May 18-22 
  • 10.0 Release Announced: Tuesday, May 26, 2026

Agenda

Attendees

Current Work

Project Boards

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 9.2 / 8.3 / 7.6.5

Deadline is TBD for 9.2, 8.3 and7.6.5.  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 9.x.  That said, where possible, we'll try to backport bug fixes (especially significant ones) to 8. x and 7.6.x.

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

Merger Discussions

  • No major new developments.
  • Q&A webinar scheduled for September 30, 2025 with registration details forthcoming.
  • Technology group working on a potential roadmap (how to merge code, timelines, review processes).

Modularization (NX vs Angular CLI)

  • Art Lowel delegated initial prototyping to Yury; Art to continue next week.

  • Preparation PR: may be useful regardless of final decision (NX or Angular CLI). Needs multiple reviews and tests.

  • Tim to test; Art/Yury to review and give feedback.

  • Rename PR for broader relevance.

Aggressive Bot Mitigation

  • Please use this discussion ticket on GitHub to share best practices and feedback
  • Fedora-led webinar series also exploring solutions (AI Showcase Series).

    • Showcasing institutions' attempts to deal with aggressive bots; first sessions held last week
  • Existing PR: upgrade to rate limiter (default: 500 hits/IP); please share feedback if you have experience with changing the limiter

PRs and Issues Raised

  • Metadata Import Script:

    • Refactored for modularity and customization.

    • Reviewers: Kim (confirmed), Tim (tentative).

  • Key Code vs Key Character Handling:

    • Fix for keyboard input inconsistencies.

    • Art to test and merge after meeting.

  • Audit Trail Feature:

    • Large PR; requires multiple reviewers.

    • Planned demo on September 25, 2025 meeting.

  • File Upload/Download Fix:

    • Bug due to symbolic links and canonical paths.

    • Small PR; Tim to review/merge soon.

  • Archival Information Packages (AIP):

    • Proposal: include groups/people at collection/community level (not just site).

    • General agreement: useful for restoration flexibility, despite duplication.

    • Concern: performance issues for large repositories. Ticket needed.

  • JPEG Orientation Fix:

    • Correct rendering of thumbnails with EXIF rotation metadata.

    • Needs more tests and JavaDocs.

Other Notes

  • Emphasis on bringing PRs/tickets to meetings for feedback.
  • Project board still has a large backlog; more reviewers/testers needed.

Action items

  • Art/Yury: Continue NX vs Angular CLI prototyping; review preparation PR.
  • Community: Share aggressive bot mitigation tips in discussion ticket.

  • Kim: Review metadata import refactor; Art to test and merge key character PR.

  • Stefano: Present Audit Trail feature demo on September 25.

  • Tim: Review/merge symbolic link fix; test AIP duplication changes; ensure ticket created for large-repository AIP performance.

  • Contributors: Add tests/JavaDocs for JPEG rotation fix.