Page History

...

Agenda

• Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it. 
  
  1. Notice upcoming Dev Meeting Times.  This is the odd time of year where different parts of the world are exiting DST at different times.
  2. Open Repositories 2025 (Chicago) - Call for Proposals is posted. Proposals Due on December 18.
  3. DSpace and DSpace-CRIS Intent to Investigate Merger. Any questions/feedback?
     1. If merger occurs, it won't occur until 10.0 at the earliest.
     2. If merger occurs, the final product will still be called DSpace & be community controlled. Essentially, DSpace will be adding all the features of DSpace-CRIS.
     3. Overall goal is to bring our communities together & work as one.
  4. DSpace 9.0 release (due April 2025)
     1. Proposed Release Timeline (coming soon from Tim Donohue see above)) 
     2. 9.0 Board is created: https://github.com/orgs/DSpace/projects/31/
     3. Early ideas/brainstorms captured at DSpace Release 9.0 Status
  5. Ongoing Discussions:
     1. Incentivizing Code Reviews and PR Testing
     2. High CPU with DSpace 7 SSR: https://github.com/DSpace/dspace-angular/issues/3110
     3. Using both public/private REST API URLs for better performance: https://github.com/DSpace/dspace-angular/issues/1485 (Assigned to 4Science)
     4. Simplifying the Installation Process: https://github.com/DSpace/dspace-angular/issues/3184
  6. Other topics
     1. Pitch for new PR checklist item: It would be great for devs to have a way to follow new tools, libraries, concepts and patterns introduced with each DSpace release (e.g. if I introduced a new ng dependency for dspace-angular, or the first use of JDK15/17 'record' in java).
        To keep track of these things while keeping extra effort for devs and release teams at a minimum, I thought we could consider a new PR checklist item:
        "If I have introduced a new library / framework / pattern / concept, I have written a short clear description of the new concept in the PR description with links to source documentation, for inclusion in release notes" (or something like that) - when we merge, we can copy the note to a wiki page in preparation for the release along with a link to the PR that introduced it. - Kim S.
• Board Review:
  • 9.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.
  • 8.x and 7.6.x Maintenance Board - 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)
  

  • Discussion: How does the correlation id work? Do we need to change it? https://github.com/DSpace/dspace-angular/issues/3335

  • Discussion: how to keep message catalogues in sync? https://github.com/DSpace/dspace-angular/issues/3334
  • Discussion/proposal around refactoring and simplifying Live Import and External Data frameworks: https://github.com/DSpace/DSpace/issues/9758
    (nothing concrete yet but would be great to get thoughts added to this issue and maybe find some collaborators)

...