Page History
...
- Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it.
- DSpace & DSpace-CRIS potential merger discussions
- DSpace and DSpace-CRIS Planning Groups - wiki pages to follow along with ongoing discussions.
- Revisiting Audit Trail discussions. What is "good enough" for DSpace 10?
- See discussions in ticket at https://github.com/DSpace/DSpace/issues/8824
- Other topics
- Add your topics here.
- DSpace & DSpace-CRIS potential merger discussions
- Board Review:
- 10.0 Project Board - Review PRs collaboratively or Assign new PRs to volunteers to code review and/or test.
- Backlog Board - Are there any tickets here stuck in the "Triage" column? We'd like to keep this column as small as possible.
- Maintenance Board (9.x, 8.x, 7.6.x) - Known bugs can be found here, along with any backported bug fixes.
- Upcoming Topics: (Let us know if there are topics you want to discuss in future weeks)
- (Revisiting on Thurs, Oct 23) Updates on Nx / modularization discussion. Prototyping Nx vs Angular CLI Workspaces?
- Preparation PR (preparing for possible Nx migration): https://github.com/DSpace/dspace-angular/pull/4629
- Original PR (example full migration): https://github.com/DSpace/dspace-angular/pull/4019
- Restore Angular dynamic decorators: https://github.com/DSpace/dspace-angular/pull/4528 (somewhat dependent on Nx / modularization discussions)
- Follow-up on "aggressive bot" discussion: https://github.com/DSpace/dspace-angular/issues/4565
- PR to update our built-in "rate limiter": https://github.com/DSpace/dspace-angular/pull/4620
- (Revisiting on Thurs, Oct 23) Updates on Nx / modularization discussion. Prototyping Nx vs Angular CLI Workspaces?
...
See Trading reviews on Pull Requests for how to get immediate attention to that PR!
Notes
- DSpace & DSpace-CRIS potential merger discussions
- No major updates. Technology group meets later today.
- Both groups are working on documenting final recommendations to Steering. Final decisions on merger will be made by Steering and Leadership Groups. Timeline for decision is not yet set.
- Revisiting Audit Trail discussions. What is "good enough" for DSpace 10?
- Key concern is using Solr as the "primary storage" for Audit Trail. We want to avoid existing frustrations encountered with Usage Statistics (which also use Sol for primary storage).
- Lots of good discussion about best approach to move forward.
- Tim summarized the discussion on the issue ticket in this comment: https://github.com/DSpace/DSpace/issues/8824#issuecomment-3386250414
- Please add additional feedback to that ticket, if you have any.
- Clarifications added to DSpace Software Support Policy recently by Committers
- On dspace-devel, there was a good question about how we manage Angular upgrades to older supported DSpace releases: https://groups.google.com/g/dspace-devel/c/rT1WA_JjkX4
- This brought up a discussion among Committers about updating our DSpace Software Support Policy to clarify how we manage Angular upgrades (and upgrades of dependencies in general)
- New bullet point added under "Support for Security Updates → Version(s) Supported" which notes the "Limits to support for dependency updates". See DSpace Software Support Policy
- Basic idea is that we can only guarantee security updates to DSpace's own code. When it comes to updating dependencies, it may not be possible to always update dependencies when the update is not "backwards compatible".
- This comes up most frequently with Angular because Angular releases are only supported for 18 months, and unfortunately are not often "backwards compatible".
- This means older DSpace supported releases (7.x and 8.x currently) are running unsupported versions of Angular. They cannot be upgraded to latest Angular because doing so isn't backwards compatible, and would be the equivalent of upgrading to DSpace 9.x.
- Basic message: We recommend running the latest major release for the most secure DSpace experience. Older releases may be on unsupported versions of Angular.
- If you have questions, bring them to the dspace-devel email thread (see above), or to the #dev channel on Slack, or to a future meeting.
Overview
Content Tools