Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

Developers Meeting on Thurs, Aug 29, 2024

Time/Location

 from 14:00-15:00 UTC

Location: https://lyrasis.zoom.us/my/dspace?pwd=RTk4QUhISnhPRi9YenVrTFJKbDllQT09 (Meeting ID: 502 527 3040).  Passcode: dspace

Agenda

Attendees

Current Work

Project Boards

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")

Goals for 9.0

To be decided by DSpace Steering Group with feedback from Leadership Group. 

Early brainstorms at DSpace Release 9.0 Status.  Please feel free to add your own brainstorms or link in tickets that you wish to be considered. 

Goals for 8.1 / 7.6.3

Deadline is TBD for both 8.1 and 7.6.3.  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)

  • Bug/security fixes only.  These minor releases will not include any new features.
    • New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
    • Accessibility fixes are also allowed in bug fix releases, provided they don't significantly modify component behavior or similar.
  • Bug fix PRs should be created against "main" branch where possible. The "main" branch has the most strict code style rules. (i.e. PRs created against dspace-7_x  are becoming more difficult to port forward.)
  • Per our support policy, bug fixes are only guaranteed to be ported back to 8.x.  That said, where possible, we'll try to backport bug fixes (especially significant ones) to 7.6.x.
    • Keep in mind, if a specific bug fix is important to you in 7.6.x, then it is best to create two PRs (one for main and one for "dspace-7_x").  If you are able to provide a backport version of the PR, then we will merge it alongside the "main" branch version.
    • NOTE: In many scenarios, a backport to "dspace-8_x" should be possible to automate using the "port to [branch]" labels & the "Port merged Pull Request" GitHub Action

Try "Pull Request Trading" for a quicker review

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!

Notes

Updates on 9.0 prioritization

No final direction from governance yet; 9.0 will most likely focus on the first three items on DSpace Release 9.0 Status

  • Performance improvements
  • Easier installation
  • Code cleanup / maintenance

Developers can claim any tickets related to these items.


Ongoing Discussion

  • Incentivizing code reviews and PR testing – no updates
  • High CPU with SSR – updates in comment section on GitHub (from vitorsilverio; disable SSR in all pages not in sitemap)
    • Quick fix / patch to reduce high CPU load. See https://github.com/DSpace/dspace-angular/issues/3110#issuecomment-2314951449
      • That team also mentioned this fix doesn't appear to impact SEO from Google Scholar or similar.
    • Still need to find long-term solution, as our overall goal is to improve performance of SSR. But, for those who need a quick fix, the approach above seems reasonable.
    • Anyone who tries this approach, please comment on the ticket with your experiences.
  • Public / private rest APIs – no updates
  • Simplifying installation process - no updates
  • REST API occasionally loses authentication status: https://github.com/DSpace/DSpace/issues/9781 
    • looking for volunteers to help understand why this happens, look into the issue
    • Assigned to Andrea


Upcoming Topics

Using multiple database sessions per request (#8932)

  • Mark and Andrea shared ways to approach this; will summarize discussion as comments added to ticket


9.0 Project Board

  • Backlog of tickets is growing
    • Tim suggested using a portion of dev meetings to review tickets that have been on the board for a long time together
    • Possible goal of discussing at least one small PR in every dev meeting
  • Discussed #3272 together
    • Tim will capture discussion in the ticket
  • Discussed #3266 together
    • Added Art as reviewer, will add feedback












  

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.