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, July 25, 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

Continued discussion of ongoing topics

  • The 9.0 Release Board has been created on GitHub
    • The "Needs Reviewers Assignment" Section contains features that did not make the 8.0 release and were moved here from the 8.0 board (labeled "new feature")
    • Tim briefly discussed some of these features and encouraged developers to test and review these; instructions on how to review pull requests can be found on the wiki: Testing DSpace Github Pull Requests
  • The DSpace Release 9.0 Status board is currently under discussion by a subgroup of the Steering Group
    • The subgroup will identify high priority features to recommend to the Steering Group as priority for 9.0 development; DSpace Governance (Steering and Leadership) will make the final decision which features will be prioritized in DSpace 9.0
    • The Governance Groups will propose development at a more general, higher level; they will not set specific tickets or give and exact list of features (see the DSpace Release 8.0 Status for comparison)
  • Discussed ongoing agenda items (GitHub tickets)
    • #3110
      • No current updates on this ticket, recommended that developers continue analysis and add any ideas and possible solutions to the ticket's discussion section
    • #3183
      • No updates
    • #3184
      • Communication between the backend and the frontend of the installation needs improvement; this is one of the most reported technical issues users report through support channels
      • Discussed different ideas and options of improving the process, including #1485, which is also connected to performance of Server-Side Rendering.  #1485 needs updated analysis, as it's unclear if the main issue is on the backend (REST API returning incorrect "_links") or on frontend (inability to manage multiple backend URLs) or both.  Needs a volunteer to investigate further.





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