Sprint 1: May 7-18, 2018

Sprint 1 Summary

Our first (virtual) community sprint featured eight developers and four coaches, representing nine institutions and five different countries. Two sprint participants even created their first pull request to DSpace!

During the two-week sprint, ten Pull Requests (PRs) were developed, approved & merged into DSpace 7, with another four PRs still in-progress. Work concentrated on bug fixes and building out administrative functionality, primarily in the REST API layer.

• Completed
  • REST API: #2050, #2051, #2052, #2053, #2057, #2060
  • Angular UI: #243, #263, #267, #268
• In-Progress
  • REST API: #2061, #2064, #2066
  • Angular UI: #264

Sprint 1 Participants

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

• Terrence W Brady (Georgetown University, USA)
• Bill Tantzen (U of Minnesota Libraries, USA)
• Pascal-Nicolas Becker (The Library Code, Germany)
• Pablo Prieto (Almat, Mexico)
• Michael Marttila (Georgetown University, USA) 
• James Silas Creel (Texas A&M, USA)
• Michael Spalti (Willamette University, USA)
• Giuseppe Digilio (4Science, Italy)

Sprint 1 Coaches

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

• Art Lowel (Atmire, Belgium) 
• Andrea Bollini (4Science, Italy) and Luigi Andrea Pascarelli (4Science, Italy)
• Tim Donohue (DuraSpace)

Sprint 1 Feedback

Feedback from participants (provided during Sprint Wrap Up meeting). Feedback has been anonymized / aggregated.

• Positive:
  • Very helpful to receive more hands-on experience. Greate way to get started with DSpace 7
  • Appreciated ability to get immediate feedback (day to day) during sprint on Slack, etc.
  • Enjoyed that Sprint helped prioritize this effort (on their local schedule) / helped them set aside time for concentrated work/attention on DSpace
  • Learned a lot
  • Felt well supported by Sprint coaches.
  • HAL Browser for new REST API is awesome
• Could be improved / Challenges
  • Lots to learn. Getting around DSpace code took a while (for those newer to DSpace)
  • Some tickets could use more information on how to get started / recommended approach (especially useful for newer developers).  But, lots of feedback provided from coaches & on Slack as they dug in.
  • Integration Tests took getting used to.  May want to improve documentation on creating them / detailing how to run tests, etc.
  • Some were working with Spring for first time (in new REST API).  More training / documentation on Spring concepts & how they are used in REST API could be useful in getting up-to-speed more quickly
  • DSpace Developer environment (with an IDE) took some time to get setup. Wiki docs could be improved / updated, but Dev Show and Tell - IDE Showcase video was helpful to some
  • Not as much effort on the Angular UI during this Sprint. We need to work on more balance for future Sprints.  We could even consider doing some future sprints specific to either REST API or Angular UI, to ensure consistent effort on both layers.

Sprint 1 Schedule

• Sprint 1 Meetings (Please do your best to attend all three meetings. If you cannot attend a meeting, please touch base with Tim Donohue for any updates, etc.)
  • Sprint 1 Kick Off Meeting (one hour): Monday, May 7 at 14:00UTC (10:00am EDT) in DSpace Meeting Room
  • Mid-Sprint Meeting (one hour): Monday, May 14 at 14:00UTC (10:00am EDT) in DSpace Meeting Room
  • Sprint Wrap-Up (Closing) Meeting (one hour): Friday, May 18 at 14:00UTC (10:00am EDT) in DSpace Meeting Room
• Daily Standups are on #dev-sprint Slack. Just provide your daily updates via text chat, prior to 15:00UTC each day.
• More information on Sprint Schedule / Meetings can be found at Sprint Schedule

...

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 search tickets (All unresolved, unassigned "REST API v7" tickets)  (TODO: Andrea Bollini (4Science) will be labeling recommended tickets with "Sprint 1"tickets with the "community-sprint1" and "ready" label)

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

Sprint Task Estimates (outdated)

...