Versions Compared

Key

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

...

  • (30 mins) General Discussion Topics
    1. Open Repositories 2022 (June 6-9 in Denver). Who is planning to attend? What would we want to plan for DSpace 7 ?
    2. DSpace 7.2/7.3 workshop: Leaning towards holding an online workshop/webinar instead of a workshop at OR2022. 
    3. DSpace 7.2/7.3 talks: Team noted it would be best to have at least one DSpace 7 talk at OR2022 in order to provide an update to the OR community.  Additional talks might be moved online perhaps alongside the online workshop? at OR2022 - What talk(s) are we submitting for OR2022?
    4. Review tentative 7.3 Release Schedule above. This is based on a new 4-month release window, but could conflict with OR2022 plans.
    5. Any assigned 7.3 work needing early discussion?
      1. Additional feedback on Administrative Control Panel: DEMO of third-party webapp for Spring Boot Actuators. Could we use this webapp as our Administrative Control Panel, or should we build our own UI in the Angular UI?
        1. Actuator PR: https://github.com/DSpace/DSpace/pull/8166
      2. Additional feedback on DSpace 7 Versioning with Entities: https://docs.google.com/document/d/1E7_zUse5ojI_N9hks53GS3NGboXKkxkF6ud1lPmcDP8/edit#
        1. Feedback from last week was the high level design looks good.  All agree.
        2. Asked Ben Bosman for a new diagram to outline the use case of two Publications linked via a relationship where Publication A is the review of Publication B.  If Publication B is then versioned into B2, it may be important for Publication A to somehow retain an "original" link to Publication B (as that was the version which was reviewed), even if B2 is now the latest version.
    6. (Other Topics?)
  • (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.3 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.

...