Sprint 3: Oct 1-12, 2018

Sprint Summary

Our third (virtual) community sprint featured eight developers and three coaches, representing eleven institutions and five countries. Six sprint participants had participated in a previous sprint. It's wonderful to see their continued progress and support for DSpace, while also seeing two new people join the effort!

During the two-week sprint, seven Pull Requests (PRs) were developed, approved & merged into DSpace 7, with another seven PRs still in-progress. On the Angular UI side, we saw new translations of the existing UI (Czech, Dutch and German) along with bug fixes / minor enhancements.  On the REST API side, we saw the creation of new endpoints (for creating communities and groups), enhanced Submission functionality, OpenSearch support and numerous bug fixes.

Sprint Participants

Thanks to our Sprint #3 Participants and their institutions! We appreciate your hard work during this sprint, and we hope to see you continue to contribute to DSpace.

Sprint Coaches

Thanks also to our Sprint #3 Coaches!  Your help and support during the sprint was noted as a great positive in the participant feedback (see below)

Sprint Schedule

Sprint Goals

  1. Approve/merge submission & workflow codebases in REST API and Angular UI (4Science team, Tim and others)
  2. Improvements to Angular UI and REST API
    1. See Sprint Tickets below
  3. Improve developer documentation / getting up-to-speed documentation.

Sprint Tickets

Angular UI tickets

All Angular UI tickets are managed in GitHub Issues (under the DSpace/dspace-angular project). You will need developer access to claim individual GitHub tickets (contact Tim Donohue or Art Lowel (Atmire))

There are two ways to view the available tickets – either in GitHub directly, or via our dspace-angular Waffle Board.  Both views point at the same tickets, so changes in one are reflected elsewhere.

REST API tickets

All REST API tickets are managed in DuraSpace JIRA (as the REST API is being developed on the current "master" branch of the DSpace codebase). You will need developer access to claim individual JIRA tickets (contact Tim Donohue)

JIRA tickets (All "REST API v7" tickets with the "community-sprint3" and "ready" label)

 

Additional, unassigned REST API v7 tickets can be found in JIRA.  However, we recommend selecting a ticket with the "community-sprint3" label.