DSpace Developer meetings are a time when Committers and interested Deve=
lopers can discuss new software features, upcoming releases of DSpace softw=
are, and generally plan out the roadmap of DSpace. All meetings are=
public. We welcome anyone and everyone to attend, speak their opi=
nions or just listen in on the discussions. Please note that we archive all=
discussions (see Me=
eting Archives), as a service for those who are unable to attend.
Meeting Schedule
DSpace Developer meetings take place on the following schedule:
To determine which time we are meeting at during a given week, please v=
iew the DSpace Pu=
blic Events Calendar (iCal version). You can also subscribe =
to the meeting schedule via that calendar.
Also, see the world clock=
to determine the meeting time where you live.
All meetings are held for 1 hour.
Slack is used for meeting reminders, sharing agendas and day-to-day di=
scussions.
There will be no meeting on Thursday, March 14 as Tim Donohue is on vacation/holiday from March 13-17. He w=
ill return to the office on Monday, March 18.
DAYLIGHT SAVING TIME has begun in USA. This meeti=
ng will be one hour later than normal (11:00am - 12:00pm E=
DT), until Europe also enters DST on March 31.
Preparing Documentation for Testathon: Would anyone be wi=
lling to start helping to draft the 8.0 Release Notes? O=
r help start to update the Install / Upgrade docs?
Possibly exclude some components from SSR? E.g. DSpace-CRIS excludes the Search component from SSR as these are not necessa=
ry for SEO. (Need to verify this has no negative impacts on accessibi=
lity or similar.)
(Other topics?)
Board Review & assignments:=20
Backlog Board- Are there an=
y tickets here stuck in the "Triage" column? We'd like to keep this c=
olumn as small as possible.
8.0 Project Board- A=
ssign new PRs to volunteers to code review and/or test.
7.6.x Project Board - Assign new PRs to volunt=
eers to code review and/or test.
Upcoming Topics:(Let us know if there are topics you want=
to discuss in future weeks)
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 =E2=86=92 Review R=
equests")
Goals for 8.0
This were decided by Steering in their meeting on June 28, 2023.
Duplicate Detection in Submission ported from DSpace-CRIS (The Library =
Code)
Include new features which empower users in the admin UI. Make th=
ings easier for Admins.
Accepting community contributions of any 6.x features which missed 7.x<=
/li>
Improve documentation, training to allow for greater community contribu=
tions. (Ease setup/install/customization, etc.)=20
Per DSpace 7 WG meeting on June 29, 2023, this may include dependency up=
grades/maintenance (Angular, Spring, Solr, Tomcat, etc). May also inc=
lude necessary code updates/refactors to ease in ongoing maintenance. =
Release Goal: May 13, 2024
In parallel to 8.0, proof of concepts / planning regarding modularizati=
on:=20
Bug/security fixes only. Release will occur when suffici=
ent fixes have been made to warrant a release.=20
New "themeable components" (for dspace-angular) are allowed in bug fix =
releases, provided that they don't significantly modify component behavior =
or similar.
Bug fixes should have one Pull Request
A PR against either the "dspace-7_x" maintenance branch OR the "main" b=
ranch.
(In the case of complex bug fixes, it is possible this automatic port a=
ction will fail. In that situation a manual port PR may need to be created.=
)
Try "Pull Request Trading" for a quicker review
Do you have a PR stuck in "under review" that you really want to see mov=
e forward? Or maybe it's someone else's PR but you want to get it mor=
e attention?