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, December 14, 2023


Today is the last DSpace Developer Meeting of 2023.  Our next meeting will be on Thursday, January 11, 2024.

 from 15:00-16:00 UTC

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

8.0 Release Schedule

  • New Feature Development Deadlines
    • Feature PR Creation Deadline: Friday, Jan 19, 2024
    • Feature PR Review/Test Deadline: Friday, Feb 9
    • Feature PR Merge Deadline: Friday, Feb 23
  • 8.0 Release Candidate:  Friday, March 1
  • 8.0 Testathon: March 4-15 (two weeks)
  • Bug Fix Deadlines
    • Bug Fix PR Creation Deadline: Friday, March 29
    • Bug Fix PR Merge Deadline: Friday, April 12
  • Documentation & Release Week: April 15-19 
  • 8.0 Release Announced: Monday, April 22, 2024


  • Discussion Topics If you have a topic you'd like to have added to the agenda, please just add it. 
    1. Developer Meetings in Dec/Jan.  Who will be around?
      1. Thurs, Dec 21 - CANCELLED. (Tim Donohue  is around until Dec 21, but we will not hold a meeting.)
      2. Thurs, Dec 28 - CANCELLED (Tim Donohue  unavailable)
      3. Thurs, Jan 4 - CANCELLED (Tim Donohue  unavailable)
      4. Thurs, Jan 11 - First meeting of 2024!
    2. Open Repositories 2024. Proposals due on December 15.  EXTENDED UNTIL JAN 12
      1. Anyone need feedback on your OR2024 proposals? DSpace at OR2024
      2. Please include a description of any DSpace-specific proposals you are submitting on DSpace at OR2024
    3. Merging OpenAIRE Correction Service PRs prior to 2024: and
      1. As noted last week, Tim Donohue recommends these to be "1 Approval" pull requests. 
      2. While they are large, they've received a lot of feedback over the last year.  We have several other features (OpenAIRE Metadata Suggestions & COAR Notify support) which depend on this initial framework. 
    4. 8.0 release topics
      1. Any 8.0 PRs developers need feedback on prior to the holidays?
    5. (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 specified 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 (exceptions may be made for very small fixes)
    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!