Versions Compared

Old Version 1

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. DSpace 7 demo site:  Turning "on" most optional functionality in the demo site (demo7.dspace.org), to allow new v7 users to see its behavior.
      1. Turning on "mediaViewer" in config.prod.yml
      2. Turning on "showAccessStatuses" in config.prod.yml
      3. Also, a request to add a description of what features are enabled on the demo site, similar to https://demo.dspace.org/xmlui/
    2. Tentative plans for a DSpace 7 Online Workshop the week of November 14.
      1. Possibly 3 hours, and structured similar to the online "Getting Started with DSpace 7" workshop held for OR2021
        1. 1 hour on 7.4 updates & install/upgrade tips. 
        2. 1 hour on branding/customizing the Angular UI.   
        3. 1 hour on REST API integrations? (Or another topic to be decided?)
      2. Possible workshops (Spread across 3 days. Each session may be ~60min of content & 30min of questions)
        1. 1 session - (Audience: people using DSpace) 7.4 updates & Using DSpace (Repo mgrs is audience)
          1. Tim & Melissa? 
        2. 1 session - (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. 1 session - (Audience: people developing on DSpace) Development / Integrations (Angular or REST).  Theme support.  How to use the REST API & REST API best practices. 2hrs?
          1. Possibly two sessions?
          2. Andrea & Art (and Tim)
      3. Tim could use help (and additional presenters) from Atmire & 4Science.  Will keep this on our agenda until all team members are back, so that we can discuss & finalize the details.
    3. (Please suggest a topic!  If no topics are suggested, we will primarily go through the project board to ensure PRs are moving along.)
  • (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

  • Demo site updating configs
    • Tim will create a new "demo" branch for the UI settings/tweaks.  Will contact Art once completed, and we'll switch demo7.dspace.org to run off that "demo" branch (similar to how api7.dspace.org runs off a "demo" branch of the backend)
  • Workshop discussion
    • See updated notes/brainstorms in the agenda above.