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")
Deadline is TBD for 9.2, 8.3 and7.6.5. 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 PRsshould 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 9.x. That said, where possible, we'll try to backport bug fixes (especially significant ones) to 8. x and 7.6.x.
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?
Tim will be out of office next week; there will be no dev meeting next week
Our next meeting will be on Aug 21
Merger discussion
On the technical side, a plan is developing how a merger could occur
The strategy group is in the process of finalizing the Strategic Vision Document, which will soon be shared with broader community
No final decisions have been made
We will continue to share more updates as they develop
DSpace 10.0
No updates, first deadlines don't come until later this year
Other Topics
Aggressive bot discussion via Google Scholar
Please add information how you are dealing with aggressive bots on the ticket in GitHub
There is a PR that helps update the rate limiter; this is a light way to lessen the impact of aggressive bots
This only counts server side hits, does not affect client side
Currently allows for 500 requests per minute; Tim has done some testing to limit this to 20 r.p.m.
There are a lot of contingencies here, it's going to difficult to make this perfect, but there may be a sweet spot we could aim for
Please provide feedback if you have used this rate limiter and have found a good value
Important Note: we need to be careful about browser caching, as caching may prevent catching all requests in tests and provide inaccurate test results
Kim was added as a reviewer to the PR
Question: What values for rate limiter are used in the sandbox.dspace.org? Answer: The specific rate limiter built into DSpace has default values; need to ask to find out more details
If we could document or recommend tools for especially smaller sites with less resources, this would be a good goal for future discussions and agendas
Fedora is also spearheading a platform agnostic discussion series around the impact of AI bots on repositories
Initial preparation work for NX migration PR was done by 4Science, to prepare for migration to NX
Goal of this preparatory PR is to isolate part of the application in order to create the first library after migration to NX; this PR contains mostly patch changes
This is mostly moving the code around; everything works as is, code was restructured to remove dependencies
Art and Tim will try to review this initial PR; anyone else interested, please feel free to help out
We are waiting to see what happens with the NX migration PR; It would be good to have a decision whether we move to NX before continuing work on the decorator PR
Giuseppe will lead discussion on NX migration proposal at an upcoming meeting (Aug 21)
Especially as to the benefits of switching to NX from a developers perspective
In the meantime, everyone is encouraged to review the initial PR and the wiki page on the initial proposal to prepare questions for Giuseppe
10.0 Board
There are two PRs in the Reviewer Approved column; first one: Sascha should resolve the merge conflicts so it can be merged; the second: please help out with this one in case Tim doesn't get to it in the next couple of days