Developers Meeting on Thurs, August 20, 2026

Time/Location

20 Aug 2026 from 14:00-15:00 UTC

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

• More connection options available at DSpace Meeting Room

Agenda

• Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it. 
  1. DSpace & DSpace-CRIS merger activities
     1. Merger Management Team - Next meeting is later today
  2. DSpace-CRIS Merger-related PRs for 11.0:
     1. Metadata extraction of PDFs using Grobid: https://github.com/DSpace/DSpace/pull/11852 (Initial feedback has been provided and addressed)
     2. Porting of missing CRIS external authorities (ROR, OpenAIRE, ZDB): https://github.com/DSpace/DSpace/pull/12473  (Under review & initial review provided)
     3. Configurable Layout of Entity/Item Pages
        1. Backend: https://github.com/DSpace/DSpace/pull/12789  (Waiting on initial review/testing)
        2. Frontend: https://github.com/DSpace/dspace-angular/pull/5963 (Waiting on initial review/testing)
     4. Configuration options for homepage:
        1. Frontend: https://github.com/DSpace/dspace-angular/pull/5983 (Is in a draft state. Once out of draft it will be ready for review & testing)
  3. Other Topics
     1. Discussion with Google Scholar team about most frequent indexing issues with DSpace sites. Top two reasons are they are accidentally blocking Googlebot, or they have SSR disabled. https://github.com/DSpace/dspace-angular/issues/4565#issuecomment-5207458560
        1. Google Scholar asked if there's any ways we could provide suggestions / best practices to sites on how to avoid blocking the good bots (like Googlebot).  Or are there tools we could recommend to sites to use to block the bad bots which also enable the good bots to get through.
     2. Add your topics here
• Recent issues marked "Needs Discussion" (if time)

  • (none at this time)

• Board Review:
  • 11.0 Project Board - Review PRs collaboratively or Assign new PRs to volunteers to code review and/or test.
  • Board of DSpace-CRIS Merger activities - Latest status of merger-related activities, which will complete in 11.0
  • Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
  • Maintenance Board (10.x, 9.x, 8.x) - Known bugs can be found here, along with any backported bug fixes.
• Upcoming Topics: (Let us know if there are topics you want to discuss in future weeks)
  
  • (none at this time)

Attendees

• Tim Donohue 
• Holger Lenz 
• Lia Eggleston 

• Art Lowel (Atmire) 

• Andrea Bollini (4Science)

• Giuseppe Digilio (4Science) 
• Paulo Graça
• Mark H. Wood 
• Kim Shepherd 
• Grazia Quercia (4Science)
• Stefano Maffei (4Science)
• Julian Timal (eScire) 
• Martin Walk 
• Pascal-Nicolas Becker 
• Pierre Lasou 
• Nicholas Woodward 
• Sascha Szott 
• Marsa Haoua 
• Jesiel Viana (LA Referencia) 
• Arturo Garduño Magaña
• Marcin Miłosz 
• Eike Löhden 
• Scholaris Team

Current Work

Project Boards

• DSpace 11.0 board: https://github.com/orgs/DSpace/projects/35
• DSpace 10.x, 9.x, and 8.x maintenance board: https://github.com/orgs/DSpace/projects/29

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