Page History
...
(BEFORE MEETING IN #dev-sprint) Developer Stand Up - Developers give brief updates on their effort (or their team's effort).
- Update/see "Current Work" section below based on your status. Please feel free to update prior to meeting.
- Please highlight any new work (needing reviews/testing), any blockers (for you), and any discussion topics you may have.
- (20 30 mins) General Discussion Topics
- (10 15 mins) Revisit our draft Github Project Board for 7.0 beta3
- Updates from Heather Greer Klein and Tim Donohue on questions from last week
- Any way to sync JIRA tickets and GitHub Issues? (would be necessary if we wanted to continue to use both tools for time being)
- Any way to embed GitHub issue information into Confluence Wiki (in same manner as JIRA tickets)? For example, this feature in JIRA helps auto-create our Changes in 6.x in documentation.
- Not a perfect solution. But, you can embed issues or PRs via this Confluence Plugin: https://marketplace.atlassian.com/apps/1216734/github-macros-for-confluence (seems to meet use cases for basic lists of GitHub issues)
- Also able to auto-generate Release Notes (in markdown format) using https://github.com/github-tools/github-release-notes (Would allow us to post changelogs/release notes in GitHub directly instead of on the Wiki)
- Questions for the team:
- How is this Board working for you so far? Likes/dislikes?
- Should we bring this to the DSpace Committers to vote on moving all DSpace 7 tickets from JIRA to GitHub Issues?
- Updates from Heather Greer Klein and Tim Donohue on questions from last week
- (15 mins) Status check on 7.0 beta 3 release by end of June or early July
- Release possible by week of June 29?
- Or do we need to look at week of July 6? (NOTE: Tim is on vacation that week)
- Tabled Topics (will not be discussed this week, but possible for next week)
- Finalize / approve the initial list of all authorization features which we should implement for the /api/authz/features REST endpoint. This list of features should be limited to only features which are required to enable/disable User Interface functionality. (In other words, we can always add more features in the future. We just need to approve the list necessary for 7.0)
- Review current spreadsheet (from Andrea Bollini (4Science) ) : https://docs.google.com/spreadsheets/d/1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing
- Art Lowel (Atmire) : I don't see any immediate issues with the current set of features, but I would prefer a consistent naming scheme. I'd use canDoSomething for everything
- Tim Donohue added possible renames of these features based on Art's idea (see cell comments in spreadsheet). I like the "can[DoSomething]" naming scheme as well.
- Review current spreadsheet (from Andrea Bollini (4Science) ) : https://docs.google.com/spreadsheets/d/1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing
- Proposal from Art Lowel (Atmire)on enhancing object cache in Angular UI.
- Finalize / approve the initial list of all authorization features which we should implement for the /api/authz/features REST endpoint. This list of features should be limited to only features which are required to enable/disable User Interface functionality. (In other words, we can always add more features in the future. We just need to approve the list necessary for 7.0)
- (10 15 mins) Revisit our draft Github Project Board for 7.0 beta3
- (40 mins) Planning for next week
- Assigning PRs for Review
- (As necessary) claim tasks for next week from DSpace 7 Release Plan spreadsheet
...
Overview
Content Tools