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, December 7, 2023
Time/Location
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
8.0 Release Schedule
- New Feature Development Deadlines
- Feature PR Creation Deadline: Friday, Jan 19, 2024
- Feature PR Review/Test Deadline: Friday, Feb 9
- Feature PR Merge Deadline: Friday, Feb 23
- 8.0 Release Candidate: Friday, March 1
- 8.0 Testathon: March 4-15 (two weeks)
- Bug Fix Deadlines
- Bug Fix PR Creation Deadline: Friday, March 29
- Bug Fix PR Merge Deadline: Friday, April 12
- Documentation & Release Week: April 15-19
- 8.0 Release Announced: Monday, April 22, 2024
Agenda
- Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it.
- Open Repositories 2024. Proposals due on December 15.
- Wiki page to gather proposal ideas: DSpace at OR2024
- 8.0 release topics
- Updates to the OpenAIRE Correction Service PR: https://github.com/DSpace/DSpace/pull/8184 Ready for review & testing again.
- (Other topics?)
- Open Repositories 2024. Proposals due on December 15.
- 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: (Let us know if there are topics you want to discuss in future weeks)
- November 16 - Revisiting the REST Content Reports work in https://github.com/DSpace/dspace-angular/pull/2163 and https://github.com/DSpace/DSpace/pull/8598
Attendees
- Tim Donohue
- 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.1 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.
- Move forward major features which missed 7.x.
- COAR Notify support (4Science & Harvard): https://github.com/DSpace/DSpace/issues/8120
- Development proposal page: Implementation of the COAR Notify protocol in DSpace 8
- OpenAIRE integration with notification broker/claim service (4Science)
- Porting "REST-Based Quality Control Reports" from old REST API to new one. (U of Laval, Canada)
- Duplicate Detection in Submission ported from DSpace-CRIS (The Library Code)
- COAR Notify support (4Science & Harvard): https://github.com/DSpace/DSpace/issues/8120
- Include new features which empower users in the admin UI. Make things easier for Admins.
- Accepting community contributions of any 6.x features which missed 7.x
- Improve documentation, training to allow for greater community contributions. (Ease setup/install/customization, etc.)
- 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.
- Release Goal: April 2024
- In parallel to 8.0, proof of concepts / planning regarding modularization:
- Angular : library-based architecture proposal (4Science)
- DSpace Preservation-enabled Storage via OCFL (Lyrasis, post-8.0)
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)
- A PR against the "dspace-7_x" maintenance branch to apply to the next 7.6.x release.
- A PR against the "main" branch to fix this same bug for the 8.0 release.
- (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!