Technical training workshop (similar to past). Training 7.x & 8.0
Need for more Angular Training (Webinar / Online training)
Andrea Bollini (4Science) had and idea about a "DSpace Developer Discussion" workshop. Talk about Technical Roadmap & upcoming work. Give updates on major projects/plans.
Other known workshops
General Developer workshop (Kim) - not DSpace specific. Full day workshop
DOIs in DSpace (by DataCite with Library Code & 4Science). 1/2 day workshop
Presentation Proposals
Migration to Entities/Relationships (Dev Track) - Library Code
What is possible with Entities/Relationships (Demo oriented) - Library Code
Developer Meetings in Dec/Jan. Who will be around?
Thurs, Dec 14 - Will have a meeting
Thurs, Dec 21 - Will discuss in meeting on Dec 14
Thurs, Dec 28 - CANCELLED (Tim Donohue unavailable)
Thurs, Jane 4 - CANCELLED (Tim Donohue unavailable)
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.
Duplicate Detection in Submission ported from DSpace-CRIS (The Library Code)
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:
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?