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.

Overview

DSpace Developer meetings are a time when Committers and interested Developers can discuss new software features, upcoming releases of DSpace software, and generally plan out the roadmap of DSpace. All meetings are public. We welcome anyone and everyone to attend, speak their opinions or just listen in on the discussions. Please note that we archive all discussions (see Meeting Archives), as a service for those who are unable to attend.

Meeting Schedule 

DSpace Developer meetings take place on the following schedule:

  • Every Thursday (except where noted in agendas) from 14:00-15:00 UTC (10am-11am EDT) in https://lyrasis.zoom.us/my/dspace?pwd=RTk4QUhISnhPRi9YenVrTFJKbDllQT09 (Meeting ID: 502 527 3040). 
  • All meetings are held for 1 hour. 
  • Slack is used for meeting reminders, sharing agendas and day-to-day discussions.
    • #dev:  For ongoing, day-to-day (between meetings) updates / discussions / questions.
    • #angular-ui : For DSpace (Angular) UI updates, discussions and/or questions.
    • #rest-api : For DSpace REST API updates, discussions and/or questions.

Meeting topics often include:

  • Recent updates on upcoming DSpace releases, bug fixes or features
  • Reviewing of recent reported issues/bugs/feature requests
  • Occasionally we vote or make decisions on upcoming DSpace technology plans/roadmap (see Developer Voting Procedures for more info)

If you are unable to attend a meeting, please feel free to add your own notes/comments to the meeting's wiki page.

Developers Meeting on Thurs, October 5, 2023

Time/Location

 from 14:00-15:00 UTC

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

Meeting on Thurs, Sept 28 is cancelled.  Tim Donohue will be out of the office from Tues, Sept 26 - Fri, Sept 29 (attending a Lyrasis All Staff meeting).  He will be occasionally checking email, but will not be around in Slack, etc.

Agenda

Attendees

Upcoming Topics

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

  • (Your idea goes here)

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: 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.
    • New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
  • 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.)

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

Meeting Archives


General Developer meeting went on hiatus from Aug 2019 to June 2023

This Developers meeting went on hiatus  from August 2019 to June 2023.  It was replaced by the DSpace 7 Working Group (2016-2023).  See that page for archives of meetings during that time.

Developer meetings began again in July 2023. See meeting notes below

Historical Notes and Transcripts from all Developers Meetings are available off of the Developer Meeting Archives page.

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.