Sprints

Sprint #1 (May 7-18, 2018)

Sprint Planning / Details

DSpace 7 Community Sprint 1

Participants

Signups are now open! Please add your name below if you wish to participate in this Sprint during the weeks of May 7 and May 11.  

Expectations from Participants 

• We have no requirements for your availability during sprint weeks. However, we do ask that you attempt to clear your schedule enough to work on (ideally a few) tickets/tasks during the sprint. At the beginning of the sprint, we'll ask you for your estimated availability (e.g. 20% time, 40% time, etc), and work to steer you toward tickets achievable within your available time.
• You will be expected to manage your own work schedule, attend minimal meetings & report your ongoing progress (as described in the below Sprint Schedule).
• You will be expected to have some existing knowledge of DSpace concepts (on v6 or below) and a willingness to be proactive in learning any new DSpace 7 concepts (see Resources below), such as Angular and/or REST API. While you are more than welcome to use this Sprint as a learning experience, we will not have any formalized training/workshops during the Sprint week itself.  That said, video from last year's DSpace Angular workshop is available in the Resources below.
• You will be expected to be proactive in asking for help or asking questions if you get stuck  (see also Support Options below). Ongoing support will be available on Slack from Sprint Coaches (see below) and other participants. We also have a Zoom video conferencing room (DSpace Meeting Room) available for "face to face" discussions, screen sharing and/or pair programming.

Participant Signups

If you are only available on certain days/times during the sprint weeks, please feel free to note your availability below.

• Terrence W Brady
• Patrick Trottier
  • Availability: Unavailable between 22:00 and 1:00 UTC on Wednesdays.
• [Your Name here]

Sprint Coaches

Coaches should be available during both sprint weeks for help getting up to speed / answering questions / debugging issues / pair programming requests, etc.  If you are unavailable on specific days during the sprint, please note those days below.

• Art Lowel (Atmire)
• Andrea Bollini (4Science) and Luigi Andrea Pascarelli (4Science) (alternately)
• Tim Donohue

Resources

• DSpace 7 Angular UI
  • Codebase (master branch): https://github.com/DSpace/dspace-angular (See README for details)
  • Demo site: https://dspace7-demo.atmire.com/
• DSpace 7 REST API
  • Codebase (master branch): https://github.com/DSpace/DSpace (See README for more details)
  • Demo site: https://dspace7.4science.it/dspace-spring-rest/
  • REST Contract: https://github.com/DSpace/Rest7Contract
  • DSpace 7 REST: Coding DSpace Objects
• DSpace 7 Learning Resources
  • DSpace 7 - Angular UI Development : Getting started with DSpace 7 UI (aka dspace-angular) and how to contribute
  • DSpace 7 UI Technology Stack : Overview of technologies we are using, and links to third party resources
  • OR2017 DSpace Angular Workshop : Angular UI Training Workshop resources (slides and hands-on activities) from the OR2017 conference in Brisbane, Australia.
    • The beginning of this workshop was also presented as a tutorial at the 2017 North American User Group meeting (at Georgetown University). Video of that tutorial is available at http://youtube.com/watch?v=c4AJ8HeZzcw
• Contributing Code to DSpace
  • Code Style Guide (for Java / REST API)
    • For Angular UI we follow the official Angular.io Style Guide
  • Code Contribution Guidelines (currently more specific to Java / REST API)

Sprint Schedule

• Weekly Kickoff Meeting (each Monday)
  • Sprint Participants (or a representative from your organization) should attend the Sprint Week Kickoff Meeting in DSpace Meeting Room.
    • Anyone unable to attend must touch base with the Sprint Coordinator (Tim Donohue) via another means (Slack, DSpace Meeting Room, email, etc) for any necessary information.
  • The goal of the Kickoff meeting is to:
    • Touch base & finalize plans / goals for the Sprint week (i.e. ensure everyone is on the same page)
    • Ensure all participants have assigned tasks, and any necessary support/resources to begin their work
    • As necessary, go through expectations / protocols of the Sprint (e.g. Contributing code via PRs, Where to ask for help/support, Meeting schedule for week, etc)
    • Address or discuss any questions that sprint participants may have
• Daily Standups via Slack: On each day of the sprint (Tues-Fri), prior to 15:00 UTC, each participant should report their status update in the Slack #dev channel.  This will act as our daily "standup" meeting.

  • Template (feel free to copy and paste into Slack and fill in the details)

    [DSpace 7 Sprint] Tasks completed: * List ticket titles / links that you completed (since your last update) * Please include brief textual description Working on: * List ticket titles / links that you plan to work on next (or continue work on) * Please include brief textual description Blockers: * Is there anything blocking your progress today? Give a brief textual description

    
    

• Additional meetings may be scheduled as necessary

Support Options

• Sprint coaches are available for support. Keep in mind however that sprint coaches may be in a different timezone from you. Therefore we have a few guidelines to keep in mind:
  • Please ask your questions publicly on Slack. You may mention specific individuals by name to alert them to your message. 
  • Please avoid private, one-on-one messaging (unless you are actively pair-programming on a task). That way other sprint coaches/participants may also provide support and/or learn from your questions.
• Requests for help / questions should be asked on Slack. Please use the #dev-sprint channel.
• The DSpace Meeting Room may also be used to do pair programming / screen sharing / ad hoc meetings / support. Keep in mind we only have the one room, so be sure to share it with others if they need it.