Versions Compared

Old Version 4

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version Current

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • (30 mins) General Discussion Topics
    1. Tentative plans for a DSpace 7 Online Workshop the week of November 14.  (Loosely based on "Getting Started with DSpace 7" workshop held for OR2021)
      1. Possible workshops (Spread across 3 days. Each session may be ~60min of content & 30min of questions)
        1. Session 1 - (Audience: people using DSpace) 7.4 updates & Using DSpace (Repo mgrs is audience)
          1. Tim & Melissa? 
        2. Session 2 - (Audience: people setting up a DSpace) branding Angular UI + backend configuration (light customizations / configuration - simple changes).  Higher level install/upgrade tips.
          1. Tim? & Corrado
        3. Session 3 - (Audience: people developing on DSpace) Development / Integrations (Angular or REST).  Theme support.  How to use the REST API & REST API best practices. 2hrs?
          1. Should be an introduction to DSpace development (not a deep dive).  Perhaps similar Angular & REST content to "Getting Started with DSpace 7" workshop held for OR2021
          2. Andrea & Art (Art will be back from holiday on Nov 15. This session should be on 17th or 18th)
    2. Bitstream's SequenceID cannot be guaranteed unique in an Item: https://github.com/DSpace/DSpace/issues/8466
    3. Support for new Entity Type (COAR "Resource Type"): https://github.com/DSpace/dspace-angular/issues/1645
      1. PRs https://github.com/DSpace/DSpace/pull/8439 and https://github.com/DSpace/dspace-angular/pull/1747
  • (30 mins) Planning for next week
    • Review the Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
    • Review the 7.4 Project Board - Assign tickets to developers & assign PRs to reviewers.
      • Paid (by DSpace project) developers must keep in mind priority. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.
      • Volunteer developers are allowed to work on tickets regardless of priority, but ideally will review code in priority order

...

  • Overview of our Triage process:
    1. Initial Analysis:  Tim Donohue will do a quick analysis of all issue tickets coming into our Backlog Board (this is where newly reported issues will automatically appear).
    2. Prioritization/Assignment: If the ticket should be considered for this release, Tim Donohue will categorize/label it (high/medium/low priority) and immediately assign to a developer to further analysis. Assignment will be based on who worked on that feature in the past.
      1. "high priority" label = A feature is badly broken or missing/not working. These tickets must be implemented first, as ideally they should be resolved in the next release.  (Keep in mind however that priorities may change as the release date approaches. So, it is possible that a "high priority" ticket may be rescheduled if it is a new feature that cannot fit into release timelines.)
      2. "medium priority" label = A feature is difficult to use, but mostly works.. These tickets might be resolved prior to the next release (but the release will not be delayed to fix these issues).
      3. "low priority" label = A feature has usability issues or other smaller inconveniences or a non-required feature is not working as expected.  These tickets are simply "nice to have" in the next release.  We'll attempt to fix them as time allows, but no guarantees are made.
    3. Detailed Analysis: Developers should immediately analyze assigned tickets and respond back within 1-2 days. The developer is expected to respond to Tim Donohue with the following:
      1. Is the bug reproducible?  (If the developer did not understand the bug report they may respond saying they need more information to proceed.)
      2. Does the developer agree with the initial prioritization (high/medium/low), or do they recommend another priority?
      3. Does the bug appear to be on the frontend/UI or backend/REST API?
      4. Does the developer have an idea of how difficult it would be to fix? Either a rough estimate, or feel free to create an immediate PR (if the bug is tiny & you have time to do so).
      5. Are you (or your team) interested in being assigned this work?
    4. Final Analysis: Tim Donohue will look at the feedback from the developer, fix ticket labels & move it to the appropriate work Board.  If it is moved to the Project Board, then the ticket may be immediately assigned back to the developer (if they expressed an interest) to begin working on it.
      1. If the ticket needs more info, Tim Donohue will send it back to the reporter and/or attempt to reproduce the bug himself.  Once more info is provided, it may be sent back to the developer for a new "Detailed Analysis".

Notes

  • Discussion of Nov Webinar
    • No new notes other than making sure to schedule webinar's around any presenter conflicts
  • Discussion of Bitstream's SequenceID cannot be guaranteed unique in an Item: https://github.com/DSpace/DSpace/issues/8466
    • Notes on discussion added as a comment to the ticket itself
  • Discussion of Support for new Entity Type (COAR "Resource Type"): https://github.com/DSpace/dspace-angular/issues/1645
    • We delayed the discussion of this new Entity Type
    • But, we also noted that this brings up a general topic that we really need to schedule time for.  What is the plan for Entities going forward?
    • However, we can & should discuss what we may want to do with Entities in DSpace 7.  Do we wish to allow for new Entities in 7.x (if so they may need to also go past Steering)?  Do we place any limitations on the types of Entities which could be added to 7.x
    • Tabled all this for next week as we didn't have time for the discussion on Entities.