Developers Meeting on Thurs, January 18, 2024

Time/Location

18 Jan 2024 from 15:00-16: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. 8.0 release topics
     1. REMINDER: Feature PR Creation Deadline is TOMORROW (Friday, Jan 19) 
     2. Any high priority questions or required feedback regarding new features?
        1. Should we migrate to Spring Boot 3 / Tomcat 10 in DSpace 8.0?  See https://github.com/DSpace/DSpace/issues/8713
           1. This is a massive migration from "javax.*" to "jakarta.*", as it also requires upgrading Spring, Spring Security and Hibernate (at a minimum)
              1. Tim has begun a branch but it is not yet functional: https://github.com/DSpace/DSpace/compare/main...tdonohue:DSpace:update_major_dependencies?expand=1
              2. Tim's branch depends on this PR to remove the old REST API: https://github.com/DSpace/DSpace/pull/9258
           2. However, Spring Boot v2 is EOL for OSS Support (with commercial support still provided through Aug 2025).  Spring 5 is still under support until end of 2024 (and until end of 2026 for commercial support).
  2. (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)
  • Thursday, January 18. - Discuss new ESLint rules suggested in https://github.com/DSpace/dspace-angular/pull/2343  Are these reasonable to everyone?   Should we apply this PR after all 8.0 features are merged?

Attendees

• Tim Donohue 

• Art Lowel (Atmire) 

• Andrea Bollini (4Science)

• Giuseppe Digilio (4Science) 
• Paulo Graça
• Mark H. Wood 
• Grazia Quercia (4Science)
• Corrado Lombardi (4Science) 
• Julian Timal (eScire) 
• Martin Walk 
• Melissa Anez 
• Oliver Goldschmidt 
• Hrafn Malmquist 

Current Work

Project Boards

• DSpace 8.0 board: https://github.com/orgs/DSpace/projects/27
• DSpace 7.6.x 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 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): https://github.com/DSpace/DSpace/issues/8120 
      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!

Notes

• Discussion of Should we migrate to Spring Boot 3 / Tomcat 10 in DSpace 8.0?  See https://github.com/DSpace/DSpace/issues/8713
  • Consensus is we MUST schedule this for 8.0, otherwise 8.0 will be difficult to support
  • Will likely require ~3 weeks of extra time
  • Needs to happen BEFORE testathon
  • Tim will notify Steering as soon as possible (Done)
  • During this 3 weeks, we can also perform work to get Angular upgraded (that would have been hard to fit in otherwise). See https://github.com/DSpace/dspace-angular/issues/2752
    • Discussion that ideally we'd merge ESLint work FIRST: https://github.com/DSpace/dspace-angular/pull/2343
    • Then, we'd merge standalone components (highly recommended in Angular 17): https://github.com/DSpace/dspace-angular/pull/2750
    • Then, we'd upgrade to Angular 17.