Time/Location
from 14:00-15:00 UTC
Location: https://lyrasis.zoom.us/my/dspace?pwd=RTk4QUhISnhPRi9YenVrTFJKbDllQT09 (Meeting ID: 502 527 3040). Passcode: dspace
Daylight Saving Time is ending soon throughout the world:
Upcoming DSpace Developer Meeting Times:
|
|
Agenda
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!
Daylight Savings Reminder:
Next week’s meeting will be at 15:00 UTC, which means a temporary shift by one hour for North American participants.
Europe remains unchanged.
Meeting will settle at 15:00 UTC going forward until next year.
Tim will post reminders in Slack and agenda notes.
Merger Discussions:
Strategic and technical groups are finalizing initial reports for Steering.
Expectation: potential decision within a month.
Steering and Leadership will review feedback and either return questions or move toward decision-making.
Demonstrated: Angular CLI workspace-based prototype.
Created a customization library using standard Angular CLI commands (ng generate library).
Custom components (e.g., featured items component) added as proof of concept.
Integration tested with the main DSpace Angular app.
Key Points from Art’s Demo:
Each library is generated quickly (1–2 minutes setup).
Libraries can be built together or separately, but currently configured to build together for convenience.
Suggests moving main app code into libraries to respect boundaries and improve modularization.
Noted issue: components in main app still require relative imports rather than library imports.
Recommends separating tests and scripts into dedicated libraries.
| Aspect | Angular CLI Workspaces | NX |
|---|---|---|
| Setup Complexity | Simple, no new dependency | Adds major new dependency |
| Build Speed | Slower (no caching) | Faster (supports caching, modular build) |
| Tooling | Basic Angular tools | Extra tools: dependency graphs, strict boundaries |
| Development Convenience | Straightforward; minimal learning curve | Enforces strict rules; higher learning curve |
| Maintenance | Easier; no added layer | Potentially slower upgrades |
| Opinionated Decisions | Flexible | Enforces “best practices” automatically |
| Migration | Could migrate to NX later, but initial attempt failed due to custom Webpack | Provides ready migration structure |
Custom Webpack build is deprecated.
→ Consensus to migrate to ESBuild (used by Angular and NX).
Test structures should be split from modules.
Scripts folder violates module boundaries → needs conversion into its own library.
Automated index file generation (using Barrelsby or similar) required; currently manual.
Art Lowel:
Slightly prefers Angular workspaces (simpler, no extra dependency).
Open to NX if consensus supports it.
Emphasizes removing Webpack and modularizing either way.
Giuseppe Digilio (4Science):
Prefers NX due to tooling and caching advantages.
Main priority: agreement on moving to library-based architecture, regardless of framework.
Later clarified preference to modularize gradually, not by moving everything into one library.
Kim Shepherd:
Asked whether NX’s opinionated design could restrict flexibility or improve consistency.
Concerned about potential over-restriction for custom development.
Sasha and Martin:
Both opposed adding NX — adds tooling complexity to already heavy frontend stack.
Tim Donohue:
Neutral, leans toward simplicity.
Concerned about increasing complexity for new developers.
Wants both prototypes (NX and workspaces) available for direct comparison before deciding.
✅ Agreed:
Move DSpace frontend toward a modular, library-based structure.
Proceed to merge current PR (library-based refactoring: core, config, utils) after resolving conflicts.
Create tickets to:
Replace custom Webpack with ESBuild.
Refactor scripts into a library.
Move app-level code into libraries (future step).
Draft PR of Art’s workspace prototype will be shared for side-by-side comparison with NX PR.
⚙️ Pending Decisions:
Whether to adopt NX or stick with Angular CLI workspaces.
How to handle app directory structure (single app module vs multiple smaller libraries).
| Task | Owner | Due / Notes |
|---|---|---|
| Update and merge current modularization PR (core/config/utils) | Giuseppe / Art | High priority |
| Draft PR for workspace prototype (for comparison) | Art | Share via Slack/Chat |
| Create ticket to replace custom Webpack with ESBuild | Art | For DSpace 10 |
| Create tickets to refactor scripts + app directory | Art | Planned for DSpace 10 |
| Review both NX and Workspace prototypes | Tim, Giuseppe, Committers | Before next meeting |
| Decide on approach (NX vs Workspaces) | Team consensus | Next few weeks |
| Communicate final time change for meetings | Tim | Slack + agenda |
All agree on moving away from monolithic Angular frontend toward modular structure.
Core debate remains NX vs Angular CLI workspaces.
Workstreams are now clearly defined:
Merge existing PR
Replace Webpack
Prototype comparison
Decide final architecture for DSpace 10