Page History

...

• Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it. 
  1. DSpace & DSpace-CRIS potential merger discussions
     1. DSpace and DSpace-CRIS Planning Groups - wiki pages to follow along with ongoing discussions.
     2. DSpace-CRIS and DSpace Differences  - List of known feature/architectural differences between DSpace 8 and latest version of DSpace-CRIS
  2. DSpace 8.2 and 7.6.4 maintenance releases
     1. Tentative Release Date of July 3.   Are the releases ready?July 8 or 9.
     2. Maintenance Board (9.x, 8.x, 7.6.x)
  3. DSpace 10.0
     1. 10.0 Board: https://github.com/orgs/DSpace/projects/32
     2. 10.0 Priorities: DSpace Release 10.0 Status (Depends heavily on a final decision around potential merger with DSpace-CRIS)
  4. Upcoming Refactoring & Modularization Work
     1. Migration to NX and modularization: https://github.com/DSpace/dspace-angular/pull/4019  (See also DSpace Angular : library-based architecture proposal)
     2. Upcoming PR from Atmire to make Angular decorators built dynamically again.  During migration to Angular standalone components, dynamic builds  of decorators were replaced with static maps.
  5. Other topics
     1. Question for Angular experts – can we explain more about the transferState changes in PR 3953 ? -kim
     2. Discuss tests + configuration, where things can go wrong re: https://github.com/DSpace/DSpace/issues/8538 - kim
• 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)

...

See Trading reviews on Pull Requests for how to get immediate attention to that PR!

Notes

10.0 Release

• There is a tentative schedule (top of this page), which still needs to be finalized and approved by Steering, DCAT

DSpace & DSpace-CRIS potential merger

• No updates or reports at the moment
• An update about the merger will soon be sent out to the community

Maintenance Releases

• Won't be able to get them out today – there is a security issue that has been reported in DSpace 7.x, 8.x and 9
  • We have been digging into that to understand it better and want to apply fixes before releasing maintenance versions
• We are aiming now at July 8 or 9 to get the release out the door
  • Because of the extended deadline, there is a little bit more time to get fixes into the maintenance releases

DSpace 10.0

• Lot of bug tickets on 10.0 board if you are looking for anything to do
• Also lots of PRs to review

Upcoming Refactoring & Modularization Work

• Migration to NX and modularization: No updates; further work will occur in the next three weeks
• Restore dynamic component decorators: Art gave update on progress of work
  • Q: Where is the map generated? A: in a folder with one file for each decorator
• Giuseppe assigned to decorators PR, Tim will take a look at this as well
  • Giuseppe will review Alex's PR and provide feedback
  • He will let Tim know if he wants to give an update in an upcoming dev meeting
• Want to try to get these two merged relatively quickly, need to think about which one to merge first
  • May make sense to merge the decorators PR first, as it's smaller.  But, Giuseppe will take a look at it to see if it can easily be worked into the NX PR. 
• Discussing how the NX PR is structured
  • Art notes we may want to consider using the default "libs" directory that NX uses.  Currently, the PR renames this folder to "modules".  Recommends we name "modules" back to "libs" 
  • The current PR is just the first phase.  This is where we is split parts of DSpace into libraries (in "modules" folder).  Currently just two libraries "core" and "shared/utils".  Everything else is still in the "src/app" directory.
  • Future Goal is to get the "src/app" folder as lean/empty as possible.  It should be possible for institutions to use the "src/app" folder for only the code they want to override .  This would let the "src/app" directory work similar to the Maven overlays that were used in DSpace 6 (and below) – "src/app" would let you overlay/override any defaults in the "modules" folder.
  • The main question is how to get to that goal.  This PR is just the first phase.
    • 2nd phase could be to move everything out of the "src/app" folder immediately into a single massive module.  Then 3rd phase would be to break that massive module apart into many different small modules
    • Or, 2nd phase could be to move things out of "src/app" folder little-by-little, into separate modules.  The goal would still be to get everything out of "src/app", but we'd just do it module by module.
• For anyone interested to check out how NX works, create a new NX app and play around with it
• There is a wiki page that discusses the NX proposal (as to why to even look at NX)

Other topics

• Question for Angular experts: can we explain more about the transferState configuration in PR 3953? 
  • State refers to NGRX state – before this PR, after server-side rendering, we would transfer state from server to client (through piece of JSON) to avoid having the client need to make the same requests already made by the server.
  • Q: Is there a situation where we want to set transferState to false? A: 4Science sets it to false in their production instances.
    • It might be useful to document better when to set this to false (and give a reason why)
  • Currently this configurate seems to exist just because there are scenarios where you might want to set transferState to false...but most may want to keep it as true.
• If anyone interested in discussing test configuration, there is an issue open to clean all of this up 

Action items