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 8, 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

No meeting on Thurs, August 15, 2024

Tim Donohue  will be out of the office from August 12-20, returning on Weds, August 21.  Therefore, no developer meeting will be held on Thus, August 15.  The next meeting will be on Thurs, August 22.

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

Next developers meeting

  • There will be no meeting on August 15, 2024
  • The next meeting will be held on August 22, 2024

Review of ongoing discussion topics

  • 9.0 development priorities
    • There are currently no news from the Steering Group regarding 9.0 development prioritization
    • A subgroup of Steering (9.0 Planning Group) is discussing recommendations and will pass these on to Steering at the end of this week
    • As a reminder, Steering tends to set general development priorities and does not provide a list of specific features (compare the Priority List for 8.0)
  • Optimization of workflow around code reviews and pull request
    • A previous discussion about this resulted in the creation of this wiki page: Incentivizing Code Reviews and PR Testing
      • Reviewed some of the main ways to speed up workflow listed on this page (trading pull requests, Pull preview as a service, GitPod)
      • All developers are encouraged to review this page; if anyone has additional ideas, please add them to the page or send them to Tim
      • If anyone has tried suggestions listed on this page, please share your notes as to your experience with the suggested solution
  • High CPU with DSpace 7 SSR
    • Looking for more volunteers to tackle this issue
  • Using both public/private REST API URLs for better performance
    • Has been assigned to 4Science
    • Currently no updates on this ticket
  • Simplifying the installation process
    • This is a larger task which will likely require several smaller fixes
    • Smaller, step-by-step improvements are welcome to move this along

Changes Group2Group Cache computation (#9760)

  • Connected to performance-related discussion
  • Could be a promising performance fix if implemented
  • Changed to high-priority

Review of 9.0 Project Board

  • General reminders
    • We need developers to review or test what is on the board (category "needs reviewers assigned" or "under review")
    • The main purpose of assignments is so that someone is tasked; others can review even if not assigned to a specific ticket
    • A number of items on this board have merge conflicts and need attention from developers.
  • "Reviewer approved" column
    • Tim will take a look at this column today or tomorrow and see if he can get some of these merged
    • Other Committers are encouraged to keep the number of items in this column as small as possible
  • "Needs Reviewer Assignment" column
    • Reviewed, discussed and assigned several tickets in this column
      • #8932 – Needs further discussion; will be discussed at a future developers meeting
      • #3078 – Assigned to Art (with backend ticket #9610)
      • #3076 – Assigned to Kim (with backend ticket #9608)
      • #9650 – Assigned to Pascal
      • #2971 – Assigned to Tim (with backend ticket #9489)
      • #3026 – Assigned to Art (with backend ticket #9562)
      • #3035 – Assigned to Art
      • #3054 – Assigned to Tim
      • #3065 – Assigned to Tim
      • #3075 – Assigned to Art
      • #3140 – may be replaced by #3199 if #3199 is approved


  

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