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, October 8, 2026

Time/Location

 from 14:00-15:00 UTC

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

11.0 Release Schedule (Tentative)

  • New Feature Development Deadlines
    • Feature PR Creation Deadline: Friday, February 19, 2027
    • Feature PR Review/Test Deadline: Friday, March 12
    • Feature PR Merge Deadline: Friday, March 26
  • 11.0 Release Candidate:  Friday, April 2
  • 11.0 Testathon: April 5 - 23 (three weeks)
  • 11.0 Translation updates: April 5 - 23 (during Testathon)
  • Bug Fix Deadlines
    • Bug Fix PR Creation Deadline: Friday, May 7
    • Bug Fix PR Merge Deadline: Friday, May 21
  • Documentation & Release Week: May 24 - 28 
  • 11.0 Release Announced: Monday, May 31, 2027

No Developer Meeting on Thursday, October 1 because of conflicts with return travel from the DSpace North American User Group meeting.  Our next meeting is Thursday, Oct 8.

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 11.0

Finish the merger of DSpace and DSpace-CRIS. Other priorities be decided by DSpace Steering Group with feedback from Leadership Group. 

Priorities listed at DSpace Release 11.0 Status. 

Goals for 10.1 / 9.4 / 8.5 

Deadline is TBD for 10.1, 9.4, 8.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-8_x  are becoming more difficult to port forward.)
  • Per our support policy, bug fixes are only guaranteed to be ported back to 10.x.  That said, where possible, we'll try to backport bug fixes (especially significant ones) to 9.x and 8. 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

North American User Group Meeting

  • Briefly reviewed the North American User Group Meeting, which was attended by ca. 50 people from North America and Europe
  • Slides will be shared on the DSNAUG wiki page in due time

DSpace 11 Release Schedule

  • Tentative schedule has been published; DCAT feedback still to be solicited
  • Please direct any comments or thoughts to Tim

General Merger Updates

  • Current merger work is happening in a shared working branch off of the main branch (unified-model-11_x)
  • Nothing has been merged to this new branch as of yet
  • Anyone is welcome to contribute by reviewing, testing, or contributing feedback to the work 

Merger-related PRs

DSpace AI Contribution Policy

  • Has officially been approved and posted on the wiki (AI Contribution Policy)
  • PR templates have also been updated
    • Any new PRs include an AI disclosure section in the templates
  • Note: Steering's approval is on interim basis – an active working approval has been given that allows testing the policy during a three month interval
    • Any necessary adaptations emerging during this period will be brought back to Steering & Committers for a new vote

Aggressive Bots and SSR performance

  • Better SSR caching: PCG will be sharing a PR on using Redis caching with DSpace.
  • Anubis or CloudFlare instructions on Managing Aggressive Bots? 
    • If you are using any of these tools, please add to this page
    • Additionally, if you are using any of these tools and are open to share your solutions with the community, please consider presenting your solution(s) at a webinar
    • Question: Does Anubis also allow to protect the REST API of DSpace?
      • Anubis is a proof-of-concept tool that mainly protects the frontend; backend protection requires setting the proxy in the proper way
    • Question:  Do we know whether the bots are more likely to slow down the frontend through SSR, or overwhelm the REST API?
      • Generally, it seems to be hitting the frontend through SSR, not the REST API
      • Comment: Bots have taken down the backend at times when the frontend has remained standing; not a lot of detail on the specifics though
      • Comment: Frontend usually dies first when bots are about scraping; bots focused on testing security and vulnerabilities often attack the API
  • Creating a list of trusted IPs for fine-tuned SSR:  https://github.com/DSpace/dspace-angular/issues/6212
  • Several recent SSR-related PRs from Sascha
  • Discussed ideas for a larger PR to remove translations from the SSR output



All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.