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, July 26, 2017

 

Today's Meeting Times

Agenda

Quick Notes / Reminders

  • NEXT DSpace 7 UI MEETING: TOMORROW, July 27 at 15:00 UTC (11:00am EDT) in Slack

Discussion Topics

  1. NOTE: Any developers can now be assigned JIRA tickets. Get in touch with Tim Donohue to be added to the JIRA "dspace-developer" group, which gives you developer level rights, including editing DSpace tickets, self-claiming them, etc.

  2. Updating demo.dspace.org to 6.1: demo6.dspace.org Notes   Any volunteer?

  3. DSpace High Priority Tickets

    1. High Priority (Blocker, Critical or Major) and flagged for release

      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. Need Code Review, Flagged for Release

      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.

  4. DSpace + Spring: Slack Discussion on whether DSpace codebase should move more towards the Spring way of doing things (e.g. Dependency Injection via beans) or the traditional DSpace patterns (e.g. classloaders with little DI).
    1. This was asked on dspace-devel: https://groups.google.com/d/msg/dspace-devel/oBWibfQUXzI/y05K-wpLAgAJ
  5. DS-3372 and DS-3587: discussion required, should we add more SQL dialect support? MySQL, MS SQL? Are we ready to support, test and maintain these dialects in the future?
    1. Also asked on dspace-devel: https://groups.google.com/d/msg/dspace-devel/UfTU7AFZjs0/UOgiSnJKAgAJ
  6. Other Tickets needing discussion (Please feel free to add any you wish to discuss under this topic)
  7. Reviewing JIRA Tickets or PRs
    1. Please feel free to bring any that need eyes / immediate discussion
    2. JIRA Backlog of "Received" tickets
    3. All open PRs

Ticket Summaries

  1. Help us test / code review! These are tickets needing code review/testing and flagged for a future release:

    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.