Time/Location
from 14:00-15:00 UTC
Location: https://lyrasis.zoom.us/my/dspace?pwd=RTk4QUhISnhPRi9YenVrTFJKbDllQT09 (Meeting ID: 502 527 3040). Passcode: dspace
|
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")
To be decided by DSpace Steering Group with feedback from Leadership Group.
Priorities listed at DSpace Release 10.0 Status.
Deadline is TBD for 9.2, 8.3 and7.6.5. Bug fix releases do not have fixed/scheduled deadlines. Instead, the developer team will determine when to create a release based on the significance of the issues to solve. (e.g. If major issues are fixed, then a bug fix release will occur more rapidly. If minor issues are found, then a bug fix release may be delayed until sufficient fixes have been made to warrant a release)
dspace-7_x are becoming more difficult to port forward.)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!
DSpace–DSpace-CRIS merger:
No major updates; both groups are still working toward a decision point.
Q&A webinar planned for late September.
Webinars:
Next week: First session in the new DSpace Deep Dive series
Topic: DSpace 9.x Overview + Q&A (repeat of Open Repositories presentation).
Will be recorded and posted for later viewing.
October: Planned webinar on migrating from bepress to DSpace.
Call for presenters: Anyone interested in sharing DSpace work is encouraged to contact Holger and volunteer for upcoming webinars, or just fill out the form on the website
Background:
Last week, Giuseppe presented why NX might be useful for DSpace.
Discussion continued due to limited time previously.
Tim Donohue’s findings:
Looked into NX GitHub activity: appears healthy and active.
NX supports multiple Angular versions (last 3), offering flexibility.
Kristoph feedback:
Suggested considering Angular CLI workspaces instead of NX.
Concern: NX migration may involve heavy restructuring, similar to previous Angular version transitions.
Believes Angular alone supports modularization and libraries without needing NX.
Giuseppe:
NX provides useful additional features: incremental caching, dependency graph, tooling.
Angular CLI lacks some of these.
Prefers NX but open to discussion.
Art:
Sees CLI workspaces as a possible intermediate step before NX.
Suggested experimenting with both approaches before deciding.
Proposed creating a simple prototype (e.g., adding a tab or menu) in both NX and CLI workspaces for comparison.
Francesco:
Has ~2 years of production experience with NX.
Initial learning curve and rigid structure, but ultimately useful for modularization and shared components.
Other concerns raised:
Pierre: Asked whether modularization will simplify or add complexity for new developers.
Tim: It may add slight complexity for contributors to DSpace core, but could make local customizations easier.
Mark:
Emphasized the need for clear documentation if new structures are adopted.
Preparation Pull Request (PR):
Current PR reorganizing imports and code paths is seen as a good first step, regardless of NX vs. CLI decision.
General agreement to move it forward with small adjustments.
Future work:
Consider prototyping add-ons or overlays in both NX and Angular CLI workspaces for comparison.
Document structural decisions carefully to support contributors and institutions.
Action Items:
Tim to summarize discussion and ensure feedback on current PR.
Giuseppe to clarify pathing decisions in PR (before his holiday or after return).
Art may explore a prototype comparison (depending on availability).
Community to continue discussion, aiming for clarity on benefits/complexity balance.