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.

Developers Meeting on Weds, Feb 28, 2018

 

Today's Meeting Times

Agenda

Quick Reminders

Friendly reminders of upcoming meetings, discussions etc

Discussion Topics

If you have a topic you'd like to have added to the agenda, please just add it.

  1. (Ongoing Topic) DSpace 7 Status Updates for this week

    1. DSpace 7 Working Group (2016-2023) is currently concentrating on building out search, submission, authentication and MyDSpace functionality
    2. DSpace 7 Dev Status spreadsheet: https://docs.google.com/spreadsheets/d/18brPF7cZy_UKyj97Ta44UJg5Z8OwJGi7PLoPJVz-g3g/edit#gid=0
    3. New Java Code Style Guide (enforced on "master" branch only)

  2. (Ongoing Topic) DSpace 6.x Status Updates for this week

    1. DSpace 6.3 Release Planning has general notes

    2. Currently, we are looking for individual(s) interested in leading / contributing to getting a 6.3 release out the door. Many "usual suspects" are busy with 7.x efforts.
      1. Some discussion that this might be plausible to do via a 1-2 week sprint, but still needs a Sprint Coordinator.
  3. DSpace Entities Working Group draft analysis (from RCAAP in Portugal).
    1. RCAAP analysis/proposal is at: https://docs.google.com/document/d/1bb83KKLi9Q29OXF59WV5KYepcPPZWtSzpQftTDAjFnk/edit
    2. Tim interested in more feedback on these ideas, as part of the proposal includes significant data model changes, potentially in a short period of time. (Additional developer resources may also be available to support this effort, if the effort is included as part of DSpace 7 or minimally done in parallel.)
    3. What is the best forum to discuss this proposal in more detail?
    4. How can we get Committers / interest developers "up-to-speed" enough to provide feedback here?

  4. Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)

    1. DSpace 6 performance issues with items containing a lot of bitstreams? https://groups.google.com/d/msg/dspace-tech/ZSxdm5EkT6E/iYixh3_TAAAJ
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Tabled Topics

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!

  1. Management of database connections for DSpace going forward (7.0 and beyond). What behavior is ideal? Also see notes at DSpace Database Access
    1. 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.
    2. 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.
      1. 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


Ticket Summaries

  1. Help us test / code review! These are tickets needing code review/testing and flagged for a future release (ordered by release & priority)

    key summary type created updated assignee reporter priority status fixversions

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Newly created tickets this week:

    key summary type created assignee reporter priority status

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Old, unresolved tickets with activity this week:

    key summary type created updated assignee reporter priority status

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  4. Tickets resolved this week:

    key summary type created assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  5. Tickets requiring review. This is the JIRA Backlog of "Received" tickets: 

    key summary type created updated assignee reporter priority

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Meeting Notes

Meeting Transcript

 

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