Meeting Schedule and Attendance
DSpace Developer meetings are a time when Committers and interested Developers can discuss new software features, upcoming releases of DSpace software, and generally plan out the roadmap of DSpace. All meetings are public. We welcome anyone and everyone to attend, speak their opinions or just listen in on the discussions. Please note that we archive all discussions (see Meeting Archives), as a service for those who are unable to attend.
DSpace Developer meetings take place on the following schedule:
- Every Wednesday, alternating between 15:00 UTC and 20:00 UTC (every other week) in #duraspace IRC channel or in #dev-mtg Slack channel (these channels sync all discussions)
- To determine which time we are meeting at during a given week, please view the DSpace Public Events Calendar (iCal version).
- Also, see the world clock (for 15:00 UTC or 20:00 UTC) to determine the meeting time where you live. If you are unsure how to connect to IRC, see our list of IRC Resources & Clients
- All meetings are held for 1 hour (although, admittedly, discussion sometimes extends beyond that)
Meeting topics often include:
- Recent updates on upcoming DSpace releases, bug fixes or features
- Reviewing of recent reported issues/bugs/feature requests (see JIRA Cleanup Sessions for more info)
- Occasionally we vote or make decisions on upcoming DSpace technology plans/roadmap (see Developer Voting Procedures for more info)
If you are unable to attend a meeting, please feel free to add your own notes/comments to the meeting's wiki page.
Meeting on Hiatus starting August 2019
This meeting is on temporary hiatus and will no longer be held on a regular (weekly) basis. This meeting will resume as soon as one (or more) of the following occurs:
- The DSpace 7 Working Group finishes its work & ramps down
- Or, the DSpace 6.4 release effort ramps up.
- Or, an interim chair for this meeting is located (as Tim is unavailable to chair this meeting until DSpace 7 finishes up)
In the meantime, ad hoc discussions or meetings are encouraged to occur via the #dev channel in Slack. Developers wanting status updates (e.g. on DSpace 7), or looking for feedback/advice on ongoing work are encouraged to ask for support on that channel, and we would be glad to help out.
Anyone is also welcome & encourages to attend (or "lurk") on DSpace 7 Working Group or DSpace 7 Entities Working Group meetings (both occur weekly). You need not have a microphone or camera to attend, and can take part or ask questions via text chat in Zoom.
Today's Meeting Times
Friendly reminders of upcoming meetings, discussions etc
- DSpace 7 Working Group: Next meeting is Thurs, Aug 1 at 14:00 UTC.
DSpace 7 Entities Working Group: Next meeting is Tues, Aug 6 at 15:00 UTC.
- DSpace Developer Show and Tell Meetings: On hold until interesting topics arise.
- 2019 DSpace North American User Group Meeting is coming up Sept 23-24.
If you have a topic you'd like to have added to the agenda, please just add it.
- Quick Updates from other meetings
DSpace 6.x Status Updates for this week
- 6.4 will surely happen at some point, but no definitive plan or schedule at this time. Please continue to help move forward / merge PRs into the dspace-6.x branch, and we can continue to monitor when a 6.4 release makes sense.
- This general Developers Mtg will go on hiatus, until one (or more) of the following occurs
- DSpace 7 Working Group finishes work / ramps down
- Or, DSpace 6.4 effort ramps up
- Or, an interim chair for this meeting is found.
- (In the meantime, Tim will provide status updates on DSpace 7 efforts via Slack and/or email lists. Also, anyone is welcome to drop in on DSpace 7 Working Group or DSpace 7 Entities Working Group just to "lurk" or listen in on efforts.)
- Ongoing Work
- Upgrading Solr Server for DSpace (Mark H. Wood )
- Auto-reindexing in Solr:
DS-3658Getting issue details...
- Should this only happen for major releases? Should it be configurable? Can we find a more precise trigger? When do we need to reindex?
- Dump/restore tool for the a
uthoritycore. - DS-4187Getting issue details... STATUS Or should we use
- Auto-reindexing in Solr: - DS-3658Getting issue details... STATUS
- DSpace Docker and Cloud Deployment Goals (Terrence W Brady )
Update sequences on initialization
- DSpace Launcher Dashboard - Deploy a PR on AWS for Testing
- There is a 2 minute video that illustrates this proposal.
- Docker for production - next steps
- Upgrading Solr Server for DSpace (Mark H. Wood )
- Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)
These topics are ones we've touched on in the past and likely need to revisit (with other interested parties). If a topic below is of interest to you, say something and we'll promote it to an agenda topic!
- Brainstorms / ideas
- Management of database connections for DSpace going forward (7.0 and beyond). What behavior is ideal? Also see notes at DSpace Database Access
- - DS-4276Getting issue details... STATUS
- In DSpace 5, each "Context" established a new DB connection. Context then committed or aborted the connection after it was done (based on results of that request). Context could also be shared between methods if a single transaction needed to perform actions across multiple methods.
- In DSpace 6, Hibernate manages the DB connection pool. Each thread grabs a Connection from the pool. This means two Context objects could use the same Connection (if they are in the same thread). In other words, code can no longer assume each
new Context()is treated as a new database transaction.
- Should we be making use of
SessionFactory.openSession()for READ-ONLY Contexts (or any change of Context state) to ensure we are creating a new Connection (and not simply modifying the state of an existing one)? Currently we always use
SessionFactory.getCurrentSession()in HibernateDBConnection, which doesn't guarantee a new connection: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/core/HibernateDBConnection.java
- Should we be making use of
- Bulk operations, such as loading batches of items or doing mass updates, have another issue: transaction size and lifetime. Operating on 1 000 000 items in a single transaction can cause enormous cache bloat, or even exhaust the heap.
- Bulk loading should be broken down by committing a modestly-sized batch and opening a new transaction at frequent intervals. (A consequence of this design is that the operation must leave enough information to restart it without re-adding work already committed, should the operation fail or be prematurely terminated by the user. The SAF importer is a good example.)
- Mass updates need two different transaction lifetimes: a query which generates the list of objects on which to operate, which lasts throughout the update; and the update queries, which should be committed frequently as above. This requires two transactions, so that the updates can be committed without ending the long-running query that tells us what to update.
Help us test / code review! These are tickets needing code review/testing and flagged for a future release (ordered by release & priority)Click here to expand...
Key Summary T Created Updated Assignee Reporter P Status Fix Version(s)
Newly created tickets this week:Click here to expand...
Key Summary T Created Assignee Reporter P Status
Old, unresolved tickets with activity this week:Click here to expand...
Key Summary T Created Updated Assignee Reporter P Status
Tickets resolved this week:Click here to expand...
Key Summary T Created Assignee Reporter P Status Resolution
Tickets requiring review. This is the JIRA Backlog of "Received" tickets:Click here to expand...
Key Summary T Created Updated Assignee Reporter P
Notes and Transcripts from all recent Developers Meetings are available off of the Developer Meeting Archives page.