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.
Sprints
Sprint #1 (May 7-18, 2018)
Sprint Planning / Details
Participants
(NOTE: Please refrain from signing up until the Sprint dates are finalized. This will ensure you are able to contribute during the Sprint. An announcement will be sent to mailing lists & Slack when signup is open/available. In the meantime, you are welcome to comment on this Sprint or the framework via comments to this Wiki page)
- Terrence W Brady
- [Your Name here]
Sprint Coaches
Coaches should be available during the full sprint for help getting up to speed / answering questions / debugging issues / pair programming requests, etc.
- 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)
- Code Style Guide (for 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
- Sprint Participants (or a representative from your organization) should attend the Sprint Week Kickoff Meeting in DSpace Meeting Room.
- 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)
Standup Template[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 recommend questions be asked publicly in Slack. You may mention specific individuals by name to alert them to your message. But, please avoid private, one-on-one messaging (unless you are actively pair-programming on a task). That way other sprint participants/coaches 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.