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 draft Beta 3 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)
        • No way to do this easily (without paying for an expensive plugin/tool)
      • 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)
    • Board structure/workflow
      • DSpace 7 Project Boards - Guide to how we've setup the Board.
    • 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 all DSpace 7 tickets from JIRA to GitHub Issues?
  • OTHER TOPICS WELCOME. Suggest by Tues, June 23
  • 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)
      1. Review current spreadsheet (from Andrea Bollini (4Science) ) : https://docs.google.com/spreadsheets/d/1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing 
         1. 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
         2. 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.
    • Proposal from Art Lowel (Atmire)on enhancing object cache in Angular UI.
  • (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 July 6-10)
• (30 (40 mins) Planning for next week
  
  • Assigning PRs for Review
  • (As necessary) claim tasks for next week from DSpace 7 Release Plan spreadsheet
  • Review of our Beta 3 Project Board

Attendees

• Art Lowel (Atmire) 

• Andrea Bollini (4Science)  

• Tim Donohue

• Lieven Droogmans 

• Giuseppe Digilio (4Science) 
• Ben Bosman
• Paulo Graça 
• Heather Greer Klein  

...

• DSpace 7 Release Goals : overview of goals/timelines & beta release process
• DSpace 7 Release Plan spreadsheet:  our planning spreadsheet which details which features are scheduled for each Beta release.

Current Work

...

= Highest Priority tasks (please prioritize these reviews/tasks over others).

 = review done, changes were requested or bugs found.

= review done, approved.

= review done, merge conflict or other minor changes requests

...

Claim a Ticket!

If you do not have access in JIRA or GitHub to officially claim the ticket you wish to work on, contact Tim Donohue

• Available Angular UI Tickets
  
  • Open issues in 7.0beta3 milestone (highest priority)
  • Open issues flagged as "Difficulty: low".  These may be a good starting point for newer developers.
• Available REST API Tickets
  
  • Unassigned tickets scheduled for 7.0beta3 (highest priority)
  • General REST API tickets flagged as "low hanging fruit".  These may be a good starting point for newer developers.
  • General REST API unassigned bug tickets.  Again, might be a good starting point for newer developers.

PRs Needing Review

...

...

Project Board

...

DSpace 7.0 Beta 3 Project Board: https://github.com/orgs/DSpace/projects/1

...

To quickly find PRs assigned to you for review, click these links

• REST API PRs assigned to you for review: https://github.com/DSpace/

...

• dspace/

...

1. https://github.com/DSpace/orcid-jaxb-api/pull/3

...

1. Depends on REST PR #2648 (see above) 

...

1. Depends on REST PR #2763 (see above)

...

• pulls/review-requested/@me
• Angular UI PRs assigned to your for review: 

• https://github.com/DSpace/dspace-angular/pulls/review-requested/@me

Delayed / Needs Discussion

1. 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)
   • 1. Review current spreadsheet (from Andrea Bollini (4Science) 
pull/697 (Tim Donohue will give quick second review, Giuseppe Digilio (4Science) reviewed again, feedback added)
2. (Angular) (beta4) Fix context sensitive menus https://github.com/DSpace/dspace-angular/pull/700 (Giuseppe Digilio (4Science) , Tim Donohue will give second review)
(Angular) (beta3) Fix issues with edit collection and community pages https://github.com/DSpace/dspace-angular/issues/701  StatuscolourBluetitle1 approval (Giuseppe Digilio (4Science)  feedback added)  (TIM CAN TAKE A LOOK & MERGE IMMEDIATELY IF FEEDBACK IS ADDRESSED)
3. (Angular) (beta3) CC License support https://github.com/DSpace/dspace-angular/pull/703  (Giuseppe Digilio (4Science)  feedback added, Tim Donohue ) REREVIEW once updates are done
   1. depends on REST PR #2764
4. (NEW) (Angular) (beta3) Forgot password: https://github.com/DSpace/dspace-angular/pull/707 (Art Lowel (Atmire) Giuseppe Digilio (4Science) )
   
   1. depends on REST PR #2763
5. (NEW) (Angular) (beta3) Simplify bitstream reorder: https://github.com/DSpace/dspace-angular/pull/709 (Tim Donohue  Tim will ping Bill)
6. (NEW) (Angular) Community and Collection Tree fixes https://github.com/DSpace/dspace-angular/pull/710 (Art Lowel (Atmire)  1 APPROVAL
7. (UPCOMING) (Angular) (beta3) Add support for features and authorizations: ETA Monday 2020-06-22 (NEEDS REVIEWERS) slack(Giuseppe Digilio (4Science) Tim Donohue) will send via slack
8. (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)
   
9. (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) 
10. (Backend) (low priority)  [DS-4149] porting XOAI additional indexer https://github.com/DSpace/DSpace/pull/2756 (Paulo Graça  feedback added, Andrea Bollini (4Science) )
11. (Backend) [DS-3940] SHERPA v2 API (master port
    • 1. ) : https://
    github
    • 1. docs.google.com/
    DSpace
    • 1. spreadsheets/
    DSpace
    • 1. d/
    pull/2773 (WAITING ON UPDATES FROM KIM) (Andrea Bollini (4Science) feedback added, Kevin Van de Velde (Atmire)  feedback added)(NEW) (Angular) (beta3) Collection dropdown refactoring  https://github.com/DSpace/dspace-angular/pull/708 (
    • 1. 1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing 
         1. Art Lowel (Atmire
    ) Tim Donohue
    • 1. 1. ) 
    1. Depends on REST PR #2771

PRs Needing Updates  / On Hold

1. (REST) (WAITING ON DISCUSSION, SEE 2020-05-18 DSpace 7 Transition BTE to Live Import Mtg) (tentative 7.1) [DS-4281]: Metadata suggestions in the live import https://github.com/DSpace/DSpace/pull/2712  (Tim Donohue , Andrea Bollini (4Science))
2. (REST) (WAITING ON UPDATES AFTER FINALIZING https://github.com/DSpace/Rest7Contract/pull/128) (beta 3) Controlled vocabularyMykhaylo Boychuk https://github.com/DSpace/DSpace/pull/2743 (REST Contract #120) (Tim Donohue, Kevin Van de Velde (Atmire) )
3. (Angular) (WAITING ON PROPOSAL FROM Art Lowel (Atmire) FOR RESOLVING CACHING MISBEHAVIOR IN SUBMISSION UI) Alternative links https://github.com/DSpace/dspace-angular/pull/652 (Giuseppe Digilio (4Science)  feedback added, Tim Donohue -  feedback added)

PRs Coming Soon

1. (beta 3) REST Language Support on the backend Mykhaylo Boychuk (blocked internally, it is under review by Andrea Bollini (4Science))

PRs Merged this week!

...

1. • 1. 1. : 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
        2. 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.
2. Proposal from Art Lowel (Atmire)on enhancing object cache in Angular UI.

...

Blocked

1. (Blocked PRs go here)

...

2. Initial Performance Testing from Chris.  Needs revisiting / retesting prior to 7.0. 
   1. https://cwilper.github.io/dspace-perftest/
   2. 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.
3. (REST Contract) Edit Homepage News: https://github.com/DSpace/Rest7Contract/pull/45
   
   1. 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.  
   2. 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
   3. Timeline for this is uncertain.  Possibly in 7 or 8. May depend on how/whether it can be scoped.

...