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, Mar 21, 2024


No meeting on March 14

There will be no meeting on Thursday, March 14 as Tim Donohue is on vacation/holiday from March 13-17.  He will return to the office on Monday, March 18.

Time/Location

 from 15:00-16:00 UTC

DAYLIGHT SAVING TIME has begun in USA.  This meeting will be one hour later than normal (11:00am - 12:00pm EDT), until Europe also enters DST on March 31.

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

8.0 Release Schedule

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

Agenda

Attendees

Current Work

Project Boards

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: May 13, 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