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, August 24, 2023


 from 14:00-15:00 UTC

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


  • Discussion Topics If you have a topic you'd like to have added to the agenda, please just add it. 
    1. Demo Site Migration (Releasing later today if all goes as planned):
      1. The new site (running off dspace-7_x  Docker scripts) will launch.  Announcements will go to all lists.
      2. Includes also the official announcement of (runs off main Docker scripts), which is more for developers.
      3. Please let Tim Donohue know if you notice obvious issues.  Should have identical settings to except  that it doesn't support Shibboleth at this time.
    2. Pull Request "trading"
      1. Developers are encouraged to ask other developer(s) to review/test their PR in exchange for reviewing/testing a PR created by the other developer.  This allows both developers to get more immediate feedback!
      2. Tim Donohue will also take part in this PR "trading" but in a more general fashion.
        1. If you review or test any two similar-sized PRs (of your choice), I (Tim) will promise to review one of your PRs as soon as possible (Your PR go to the top of my "to do" list.)
          1. PRs you review or test can be any PR on one of our boards (7.6.1 Board or 8.0 Board). But, they must be from a developer at a different institution from your own.
          2. You must submit useful feedback on the PR you've reviewed/tested (via a comment on the PR or similar).  It can be positive or negative feedback (if you test it and it doesn't work for you, that still counts).
        2. If I don't notice your two reviews, please message me (privately is fine) via Slack or email & let me know which of your PRs you want me to review as soon as possible.
    3. 7.6.x release topics - bug-fixes only.   
      1. Any topics to discuss?
    4. 8.0 release topics
      1. Updates to the OpenAIRE Correction Service PR:  Ready for review & testing again.
    5. Ongoing discussions. Any brief updates / brainstorms from anyone? (Feel free to also add thoughts to the pages themselves)
      1. Angular : library-based architecture proposal (4Science)
      2. DSpace Preservation-enabled Storage via OCFL (Lyrasis, post-8.0)
      3. ORCID Login improvements - Discussion in late Aug or early Sept (4Science)
      4. Tabled developer discussion (from July 27 mtg): Should we allow "Making ___ component themeable" PRs to be added to 7.6.1?  They are not exactly bug fixes, but do allow for additional theming capabilities.
        1. For example: and
    6. (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.
    • 7.6.1 Project Board - Assign new PRs to volunteers to code review and/or test.
    • 8.0 Project Board - Assign new PRs to volunteers to code review and/or test.


Upcoming Topics

If you have a topic for a future meeting, please add it here.

  • 4Science proposed to present
    1. ORCID Login improvement on Auguest 2023 (exact date is to be determined)

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 2024
  6. In parallel to 8.0, proof of concepts / planning regarding modularization (e.g. 4Science angular proposal) and OCFL/preservation storage (Lyrasis proposal to be discussed in more detail).

Goals for 7.6.1

  • Bug/security fixes only.  Release will occur when sufficient fixes have been made to warrant a release.
  • Fixes should have two Pull Requests (exceptions may be made for very small fixes)
    1. A PR against the "dspace-7_x" maintenance branch to apply to the next 7.6.x release.
    2. A PR against the "main" branch to fix this same bug for the 8.0 release.
    3. (NOTE: Once one PR is reviewed & approved, the other will be merged at the same time.)