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.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Developers Meeting on Thurs, Oct 24, 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


Daylight Saving Time Ending soon (for many)

Daylight Saving Time is ending soon throughout the world:

  • Europe: DST ends on Oct 27
  • North America: DST ends on Nov 3

Upcoming DSpace Developer Meeting Times:

  • Oct 24 (today) at 14:00UTC (current time)
  • Oct 31 at 15:00UTC  (Temporarily, one hour later for North America / anyone still in DST)
  • Nov 7 at 15:00UTC (Back to the same local time for everyone who observes DST)

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

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


Action items









  

  • No labels

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