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.
- (25 mins) General Discussion Topics
- (10 mins) Establishing a Code Review guide (to train others on code reviews & good coding practices)
- Making the PR Templates the definitive reference for reviewers (and developers)
- New Code Testing Guide to document how to write good tests (and therefore how to review for good tests)
- (15 mins) Asking all developers to record estimated PR "completion date" (PR deadline) for all beta 3 work in DSpace 7 Release Plan spreadsheet
- Goal is to better track internal prioritization/resourcing & estimated progress on current beta release.
- Also looking to potentially re-scope beta3 into what can be done by end of June. Other tasks will move to beta4, as beta3 has gotten too large.
- PR deadline should ideally be on a Tuesday (beginning of week). This allows us to anticipate which weeks which PRs will be done, and attempt to assign code reviewers prior to the Thursday meeting.
- 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 mins) Establishing a Code Review guide (to train others on code reviews & good coding practices)
- (35 mins) Planning for next week
- Assigning PRs for Review
- (As necessary) claim tasks for next week from DSpace 7 Release Plan spreadsheet
...
7.0 Release Goals
These resources define the prioritization and general schedule we are working towards
...
- (REST Contract) (beta 3) related to the scripts & processes PR above (related to PR 2648 below) https://github.com/DSpace/Rest7Contract/pull/99 (Andrea Bollini (4Science) REREVIEW, Tim Donohue -
minor feedback) (Once contact is updated Tim Donohue will rereview and merge)
- (NEW) (REST Contract) (beta 3) Refactoring Authority support / value-pairs / controlled vocabularies: https://github.com/DSpace/Rest7Contract/pull/128 (Tim Donohue, SECOND REVIEWER WELCOME) will rereview, Ben Bosman )
- (REST Contract) Minor Logout changes to support Logout Page https://github.com/DSpace/Rest7Contract/pull/124 (Andrea Bollini (4Science)
just a typo to fix) READY TO MERGE AFTER MEETING
- (NEW) (REST) (beta3) Pre authorize annotations for subresources https://github.com/DSpace/DSpace/pull/2778 (
Craig Rosenbeck , Andrea Bollini (4Science) )
- (REST) (beta3) New user registration & forgot password https://github.com/DSpace/DSpace/pull/2763 (Tim Donohue -
One comment remaining to be addressed REREVIEW, Andrea Bollini (4Science) waiting for a better status before review REREVIEW)
- (REST) (beta3) Scripts & processes: importing and exporting csv's https://github.com/DSpace/DSpace/pull/2648 (Andrea Bollini (4Science) - REREVIEW, Tim Donohue -
Needs to address feedback in original REST Contract, other minor feedback added REREVIEW after contract and merge)
- (REST) (beta3) DS-4042: Fix implementation and add IT for wrong PATCH request in submission: https://github.com/DSpace/DSpace/pull/2760 (Tim Donohue
, Ben Bosman REREVIEW)
- (REST) (beta 3) CC License support: https://github.com/DSpace/DSpace/pull/2764 (Tim Donohue - REREVIEW , Craig Rosenbeck
minor feedbackPER KEVIN'S QUESTION)
- (REST) (beta 3) Performance issues with finding Collections a user can submit to https://github.com/DSpace/DSpace/pull/2771 (Kevin Van de Velde (Atmire), -
minor feedback Tim Donohue -
minor feedback - look at 4122 and make sure it has Kevin's details)
- (REST) (beta 3) DS-4486 Add support/tests for Collection/Community role-based groups for Community/Collection Admins https://github.com/DSpace/DSpace/pull/2774 (Kevin Van de Velde (Atmire) REREVIEW, Tim Donohue )
- (Angular) (beta3) Scripts & Processes Admin UI https://github.com/DSpace/dspace-angular/pull/636 (Tim Donohue, Giuseppe Digilio (4Science), Craig Rosenbeck)
- Depends on REST PR #2648 (see above)
- (Angular) Add multi-field sorting https://github.com/DSpace/dspace-angular/pull/634
(Giuseppe Digilio (4Science)Status colour Blue title 1 approval feedback added, Tim Donohue -
questions on how to review/test. No specs in PR)
- (Angular) New User Registration https://github.com/DSpace/dspace-angular/pull/687 (Art Lowel (Atmire)
with a few UX suggestions that can move to a ticket, Giuseppe Digilio (4Science)
better to test once REST PR is merged)
- Depends on REST PR #2763 (see above)
- (Angular) (beta3) Refactor registry service https://github.com/DSpace/dspace-angular/pull/697 (Tim Donohue will give quick second review, Giuseppe Digilio (4Science)
added feedback REREVIEW)
- (NEW) (Angular) (beta4) Fix context sensitive menus https://github.com/DSpace/dspace-angular/pull/700 (NEEDS REVIEWERSGiuseppe Digilio (4Science) , Tim Donohue will give second review)
- (NEW) (Angular) (beta3) Fix issues with edit collection and community pages https://github.com/DSpace/dspace-angular/issues/701 (NEEDS REVIEWERS)
after build fix, Giuseppe Digilio (4Science) )Status colour Blue title 1 approval - (NEW) (Angular) (beta3) CC License support https://github.com/DSpace/dspace-angular/pull/703 (Giuseppe Digilio (4Science) , Tim Donohue )
- depends on REST PR #2764
- (Backend) (low priority) DS-626 : Exchange usage data with IRUS https://github.com/DSpace/DSpace/pull/2664 (
Craig Rosenbeck, Tim Donohue - REREVIEW, others can take a look)
- (Backend) (low priority) (tentative 7.2) DS-4440 GDPR - Anonymize Statistics Feature: https://github.com/DSpace/DSpace/pull/2692 (Andrea Bollini (4Science), Ben Bosman, Tim Donohue) --nice to clear this one
- (Backend) (low priority) [DS-4149] porting XOAI additional indexer https://github.com/DSpace/DSpace/pull/2756 (Paulo Graça
feedback added, Andrea Bollini (4Science) )
- (Backend) [DS-3940] SHERPA v2 API (master port): https://github.com/DSpace/DSpace/pull/2773 (Andrea Bollini (4Science)
feedback added, Kevin Van de Velde (Atmire)
feedback added)
- (NEW) (Angular) BUG FIX https://github.com/DSpace/dspace-angular/pull/702
(Art Lowel (Atmire)Status colour Blue title 1 approval ) Tim Donohue to MERGE after meeting
PRs Needing Updates / On Hold
...
- Initial Performance Testing from Chris. Needs revisiting / retesting prior to 7.0.
- https://cwilper.github.io/dspace-perftest/
- These performance tests were run prior to the work on "projections" (to limit the data returned by the REST API). Therefore, it is likely performance is much improved, but needs verification testing.
- (REST Contract) Edit Homepage News: https://github.com/DSpace/Rest7Contract/pull/45
- Delayed. General agreement (in meeting on March 21, 2019) that storing HTML in metadata fields is not really ideal behavior. Metadata (from a librarian standpoint) tends to be free of format-related markup (as that allows for easier sharing, understanding of metadata. Currently Community & Collection homepage information is HTML-based and is stored in metadata that is appropriate for a minor subset of information (like the title) but it is better to move large/rich text to bitstreams.
- Proposal here is to consider storing HTML-based markup (for Site, Community & Collection homepages) in Bitstream(s) associated with the object in question. May allow for more CMS-lite behavior in the future
- Timeline for this is uncertain. Possibly in 7 or 8. May depend on how/whether it can be scoped.
Notes
- We will try the Tuesday PR deadline and see if it is helpful
- Greater focus on time for PR discussion was appreciated
- Agreed to add to DSpace 7 Release Plan spreadsheet the following:
- claiming unclaimed Beta 3 tickets (unclaimed could be moved to Beta 4);
- adding TUESDAY deadlines for PRs, so reviewers might be pre-assigned before the Thursday meeting
- adding estimates where they are missing (less important if there is a PR deadline added)
Overview
Content Tools