- (30 mins) General Discussion Topics
- REMINDER: Tomorrow is our deadline for Bug PR Creation (exceptions can be made for very high priority bugs)
- Any new updates / brainstorms about improving initial response speed of DSpace 7 UI ? See DSpace 7 UI Optimization Analysis
- In recent weeks, we discussed analyzing whether it'd be possible to cache REST API responses for anonymous users. Art Lowel (Atmire) 's team was going to dig into this as a possible solution to the discussion in https://github.com/DSpace/dspace-angular/issues/1954
- May want to also revisit Caching of SSR pages?: https://github.com/DSpace/dspace-angular/pull/2033
- A few very annoying bugs in pre-7.5 that users have noticed:
- https://github.com/DSpace/DSpace/issues/8512 - Global "Browse by" results don't work properly for Community/Collection Admins. As soon as you login as a Community/Collection Admin, global "Browse by" options become filtered to your Community/Collection and you can no longer see everything in "Browse by". (UPDATE: fix PR now available https://github.com/DSpace/DSpace/pull/8653)
- https://github.com/DSpace/DSpace/issues/8649 - "./dspace cleanup" command has major performance issues (may also impact 6.x) as it appears to be missing a "context.commit()"
- (NO UPDATES at this TIME) Any updates on Demo Site issues (https://demo7.dspace.org/ and https://api7.dspace.org/server/)?
- LYRASIS is still working on migrating demo site to our infrastructure (and using Docker). Likely not to be completed until Jan/Feb 2023 at the earliest
- In meeting on Dec 15, we narrowed down issues as likely being on the backend. Backend is throwing occasional 500 exceptions (possibly rate limiting?). 4Science team was going to look closer at logs to see if we can figure out why this is occurring.
- (Other topics?)
- (30 mins) Planning for next week
- Review the Backlog Board - Are there any tickets here stuck in the "Triage" column? We'd like to keep this column as small as possible.
- Review the 7.5 Project Board - Assign tickets to developers & assign PRs to reviewers.
- Paid (by DSpace project) developers must keep in mind priority. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.
- Volunteer developers are allowed to work on tickets regardless of priority, but ideally will review code in priority order