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 8 Current »

Developers Meeting on Thurs, March 6, 2025

Time/Location

 from 15:00-16:00 UTC

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


Meeting time will remain at 15:00UTC until all countries have entered Daylight Saving Time

The USA/Canada start Daylight Saving Time (DST) on March 9.  However, Europe doesn't begin DST until March 30.  Until all countries have begun DST, our meeting time will remain at 15:00UTC.

After today, for anyone in the USA/Canada, this meeting will occur one hour later for the next three weeks. Our upcoming meeting schedule looks like this:

  • March 6 (today) at 15:00 UTC (10:00am EST)
  • March 13 at 15:00UTC (11:00am EDT - One hour later in USA/Canada, as they both will be in Daylight Saving Time)
  • March 20 - No Meeting (Tim will be on vacation most of this week)
  • March 27 at 15:00UTC (11:00am EDT)
  • April 3 at 14:00UTC (10:00am EDT).  As of April, all countries will be in DST, so the meeting will move back to its normal time of 10:00am ET.


9.0 Release Schedule

  • New Feature Development Deadlines
    • (tick) Feature PR Creation Deadline: Friday, February 21, 2025
    • Feature PR Review/Test Deadline: Friday, March 14
    • Feature PR Merge Deadline: Friday, March 28
  • 9.0 Release Candidate:  Friday, April 4
  • 9.0 Testathon: April 7-18 (two weeks)
  • 9.0 Translation updates: April 7-18 (during Testathon)
  • Bug Fix Deadlines
    • Bug Fix PR Creation Deadline: Friday, May 2
    • Bug Fix PR Merge Deadline: Friday, May 16
  • Documentation & Release Week: May 19-23 
  • 9.0 Release Announced: Monday, May 26, 2025

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. 

Priorities listed at DSpace Release 9.0 Status. 

Goals for 8.2 / 7.6.4

Deadline is TBD for both 8.2 and 7.6.4.  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

General business

  • The US will move to daylight savings time March 9, 2025, please remember that we will keep this meeting at 15:00UTC until April
  • For participants from North America, this will mean a time shift of the meeting time; see the meeting time reminder table above

9.0 Release Schedule

  • By next Friday, we expect that all feature PRs have had a basic review/test, to allow developers enough time to work in feedback
  • If you know you won't be able to review it, please let Tim know
  • See the release schedule above

Discussion Topics

  • The two merger planning groups are still getting up to speed
    • If you're interested in reading the meeting notes, please see
  • 9.0 release
    • Bootstrap 5 was merged; please check if there are no merge conflicts that were created by accident
    • Next dependency update is Angular 18 PR; as of today it has been updated so that it can be tested and reviewed; Tim and Giuseppe will test
      • There is currently an end-to-end test issue, but Atmire is working on it
    • Will need to get to Migration to Angular Control Flow syntax after that (#3997)
      • Need to get thorough testing going 
      • May slip the March 14 deadline, as it depends on what comes before it
    • Migration to NX & refactor into libraries
      • Not sure if this will make it into 9.0, as it depends on the other three getting in quickly
      • If it doesn't make it into 9.0, we should get it prepped so that it can go into 10.0

Ongoing discussions

9.0 Board

  • The four PRs in the "Needs Reviewer Assigned" column still need reviewers; they may not get into 9.0 if we can't find anyone who can review
  • All REST exposed config endpoint #9140
    • This hasn't been moved forward, Tim moved it to "stalled/on hold"
    • Probably won't go into 9.0
  • feat: use the metadata with correct language #3078
    • Krzysztof will update, Art will re-review
    • This one is related to  PATCH request on /metadata now supports multiple values #9610
      • This may not be necessary, may end up being closed altogether
      • #3078: will need to update the patch operation
  • Duplicate data from an existing Item to a new WorskpaceItem, aka clone/copy item #3076
    • Backend #9608
    • Need to update to move those forward
  • [Port dspace-7_x] Bump follow-redirects from 1.15.5 to 1.15.6 #2892 
    • Up to Mark if he can get to it for 9.0
  • Display Altmetric badges on simple item view #2496
    • Merge conflict, needs to be updated
  • Make the default tab for browsing communities and collections configurable in DSpace 8 #3164
    • Has work from the developer to occur if they want to move it forward, otherwise it will get dropped and left behind
  • Make the CC license field component configurable in DSpace 8.0 #3165
    • Has work from the developer to occur if they want to move it forward, otherwise it will get dropped and left behind
  • Difficult to find users to delete from group in large groups #9793
    • Needs automated tests from the developer
  • provide new CoverPage implementation #9844
    • This looks fine to move forward as is; there are still some minor things, but we can table those and talk about it later on
    • Once the dev gets back to it, Tim will be glad to re-review it
    • This replaces the existing cover page functionality; We should add a notice to the release notes that old cover page templates need a migration
  • Enhanced Login flow for ORCID Authorization feature #294 
    • Need to get the merge conflicts resolved, otherwise hard to test
    • Tim has started doing code review, at least on backend
    • Art has volunteered to test
    • Will be in a good spot once merge conflicts have been resolved
  •  ORCID Push Queue: add support for Products and Patents #9853
    • Adds new entity types for products and patents
    • Flagged as low priority – may want to delay these until the discussions around the merger is clearer; concern about entity types in 9.0 that don't have clear use cases, not requested from DSpace community
    • If anyone is interested in reviewing these, please let Tim know
    • Giuseppe: this is ported over from DSpace-CRIS
    • Does this PR affect the potential merger since DS CRIS use product and patent entities?
      • Yes, most likely; this should only be added if the merger seems clear
    • Happy to discuss this further
  • Integration of Google reCAPTCHA into DSpace Feedback Form #9866
    • Waiting on developer to solve merge conflicts
    • Others have permissions to rebase it, could move it forward, but may want to hear from the developer before touching their code
  • Expose CC license properties, relates to PR DSpace/dspace-angular#3165 #9882
    • Skipped, related to RestAPI; waiting on front-end code
  • Generic External Bitstream Storage Based on Apache JClouds #9915
    • Has merge conflicts
    • Atmire and Pascal are working on it 
    • This improves streaming performance from downloads and makes them faster
    • Will have two S3 implementations in DSpace if this one gets merged - should think about deprecating the other
      • Recommend a migration process in documentation if this gets merged
    • If anyone could test this on an AWS account, that would be great
  • Add a generic ItemPageLicenseFieldComponent #3338
    • Need to get the merge conflict resolved, then reviewed
  • Geospatial maps for item pages, search, browse #3540
    • There are test failures on this; backend has merge conflicts
    • Waiting on reviewers once merge conflicts have been resolved
  • Upgrade to angular v18 #3717
    • Once merged and ready to go, Tim will ping everyone on slack as it may create merge conflicts on other PRs
  • Made edit metadata tab fields dynamic and added entity type support #3722
    • This is related to the edit metadata tabs and the entity type on metadata
    • Has merge conflicts, need Alex at Atmire to update it soon
      • Tim has also volunteered to help out
  • Add solr based autocomplete option to submission form input #10237
    • This is not working properly at the moment, waiting on feedback from developer
    • If anyone knows this developer, let them know, otherwise won't get moved forward
  • Display the access status (embargo) for the bitstream #10294
    • Rest contract: Added the new accessStatus endpoint for bitstreams #300
    • Assigned to Tim and Yury from Atmire
      • Will get to in the next few days, so that we can get it moved forward
  • Add a curation task to copy fields #10333
    • If anyone interested, additional testers are always welcome
    • Tim will get to it, it is on his list
  • Request-a-copy improvements: Support access via secure links #10407
    • Request-a-copy improvements: Support access by secure link #3984
    • Looking quite good, Tim has reviewed it
    • Lots of feedback on both front- and backend
      • Developer has made suggestions to move it forward
  • CSV export for Filtered Items content report #3987
    • Related to CSV export for Filtered Items content report #10410
    • If anyone else is interested in testing, Tim could use help with testing
    • Related to administrative reports in DSpace 8, allowing them to export to CSV
  • added alternative content patch operations #10431
    • Providing alternative upload for audio-video content (accessibility)
    • Requires added alternative content tag and controls on bitstreams #4016 
    • Don't want to add additional endpoints for a single metadate field
    • Need feedback from the developer
  • Migrate from legacy java.util.Date and java.util.Calendar to java.time.* Date classes #10432
    • Waiting on testers or reviewers
      • Mark, Kim, and Nick: please get to this when you have a moment, if you have questions, please let Tim know
  • Refactor menu resolvers 9.0 #3994
    • Code Refactor, marked high-priority, need to figure out how to move it in once the other things have been merged that are already on the list (Angular 18, control flow syntax)
    • Moved on to main list of big PRs
    • In meantime, Giuseppe and Tim will start to do code reviewing
  • OpenAlex Integration #10433
    • Assigned to Tim only at the moment, if anyone else is interested in helping to test this, please volunteer
    • Tim will also ping Agustina
  • New solr plugin: AccessStatus to enable filtering results by item access status #10434
    • Has early testing from Pierre, it's on 4Science plate at the moment
  • REST Matomo Tracking integration for Bitstream views #10435
    • Related to Add support for Matomo #4018
    • Would love testing from Atmire to try this out
  • New requestitem bitstream strategy #10436
    • Kim may want to look at this; not sure if this will impact what he's working on as well, might worth glancing at 
      • Kim: has seen it; this is about adding approval access based on bitstream metadata, closely tied to email attachments
      • Doesn't seem to affect the other work
    • Added Yury as well
  • New feature for Search bar improvements #4022
    • Assigned to Tim, there is concern about the approach, changes to the search bar
    • If anyone else has time and is interested, please try it out 



Action items











  

  • No labels

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