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, January 25, 2024


 from 15:00-16:00 UTC

Location: (Meeting ID: 502 527 3040).  Passcode: dspace

8.0 Release Schedule (UPDATED)

  • New Feature Development Deadlines
    • (tick) Feature PR Creation Deadline: Friday, Jan 19, 2024
    • Feature PR Review/Test Deadline: Friday, Feb 9
    • Feature PR Merge Deadline (Feature Freeze): Friday, Feb 23 
  • Major dependency upgrades: February 26 - March 15 
  • 8.0 Release Candidate:  Friday, March 22
  • 8.0 Testathon: March 25-April 5 (two weeks)
  • Bug Fix Deadlines
    • Bug Fix PR Creation Deadline: Friday, April 19
    • Bug Fix PR Merge Deadline: Friday, May 3
  • Documentation & Release Week: May 6-10
  • 8.0 Release Announced: Monday, May 13, 2024


  • Discussion Topics If you have a topic you'd like to have added to the agenda, please just add it. 
    1. 8.0 release topics
      1. Updated Release Schedule (see above)
      2. Feature Review Deadline is Friday, February 9.
      3. Any high priority questions or required feedback regarding new features?
    2. Accessibility Fixes to 7.x and 8.0
      1. As of Jan 19, DSpace Steering approved funded development (via the DSpace Development Fund) for any accessibility fixes.
      2. Valid accessibility work that can be funded includes:
        1. Creation of more automated accessibility scanning/tests (similar to this PR from Tim: The goal is to have this scanning performed for all pages in DSpace, but it must be added page by page. As these tests are added, remediation may be required on pages which do not pass the automated tests.
        2. Remediation of existing known accessibility bugs.  This includes any existing issue tickets with the "accessibility" label:
    3. (Other topics?)
  • Board Review & assignments:
    • Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
    • 8.0 Project Board - Assign new PRs to volunteers to code review and/or test.
    • 7.6.x Project Board - Assign new PRs to volunteers to code review and/or test.
  • Upcoming Topics: (Let us know if there are topics you want to discuss in future weeks)
    • None at this time


Current Work

Project Boards

To quickly find PRs assigned to you for review, visit  (This is also available in the GitHub header under "Pull Requests → Review Requests")

Goals for 8.0

This were decided by Steering in their meeting on June 28, 2023.

  1. Move forward major features which missed 7.x. 
    1. COAR Notify support (4Science & Harvard): 
      1. Development proposal page: Implementation of the COAR Notify protocol in DSpace 8
    2. OpenAIRE integration with notification broker/claim service (4Science)
    3. Porting "REST-Based Quality Control Reports" from old REST API to new one. (U of Laval, Canada)
    4. Duplicate Detection in Submission ported from DSpace-CRIS (The Library Code)
  2. Include new features which empower users in the admin UI.  Make things easier for Admins.
  3. Accepting community contributions of any 6.x features which missed 7.x
  4. Improve documentation, training to allow for greater community contributions.  (Ease setup/install/customization, etc.)
    1. Per DSpace 7 WG meeting on June 29, 2023, this may include dependency upgrades/maintenance (Angular, Spring, Solr, Tomcat, etc).  May also include necessary code updates/refactors to ease in ongoing maintenance. 
  5. Release Goal: April 22 2024
  6. In parallel to 8.0, proof of concepts / planning regarding modularization:
    1. Angular : library-based architecture proposal (4Science)
    2. DSpace Preservation-enabled Storage via OCFL (Lyrasis, post-8.0)

Goals for 7.6.2

Deadline is TBD for 7.6.2

  • Bug/security fixes only.  Release will occur when sufficient fixes have been made to warrant a release.
    • New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
  • Bug fixes should have one Pull Request 
    1. A PR against either the "dspace-7_x" maintenance branch OR the "main" branch.
    2. We will automatically generate a PR against the other branch using the "port to [branch]" labels & the "Port merged Pull Request" GitHub Action
    3. (In the case of complex bug fixes, it is possible this automatic port action will fail. In that situation a manual port PR may need to be created.)

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!