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, March 15, 2017

 

Today's Meeting Times

  • DSpace Developers Meeting / Backlog Hour: 20:00 UTC in #duraspace IRC or #dev-mtg Slack channel (these two channels sync all conversations)
    • Please note that all meetings are publicly logged
    • DAYLIGHT SAVING NOTE: For those areas that have just entered daylight saving time, this meeting will be one hour later. So, for example, 20:00UTC is now 4:00 pm EDT.

Agenda

Quick Notes / Reminders

  • NEXT DSpace 7 UI MEETING: TOMORROW, March 16 at 16:00 UTC (12:00pm EDT) in Slack

Discussion Topics

  1. DSpace High Priority Tickets

    1. High Priority (Blocker, Critical or Major) and flagged for release (in 6.1 or 7.0, etc)

      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 (in 6.1 or 7.0, etc)

      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. Other Tickets needing discussion (Please feel free to add any you wish to discuss under this topic)
  3. 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.