Page tree

Versions Compared


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


  • (30 mins) General Discussion Topics
    1. Cancelling or rescheduling next week's meeting.  Thurs, Nov 25 is USA Thanksgiving & Tim will be unavailable to attend.  We can either cancel or move it to Weds, Nov 24 at 15UTC
    2. Planning 7.2 Release Features
      1. Tickets have been assigned based on last week's meeting & moved to "In Progress" column of our board. By coincidence, both teams claimed the same amount of work.
        1. Atmire: 194 hrs estimated dev work (includes 100hrs for migrating Live Import sources, see below)
        2. 4Science: 194 hrs estimated dev work
      2. (Discussion) Migrate extra DSpace-CRIS “Live Import” (Scopus, Web of Science, CrossRef & OpenAIRE) sources to DSpace core: (roughly 100 hrs?)
        1. Is there an updated estimate?
        2. If we can pay for this out of the DSpace budget, would 4Science prefer to do this porting themselves?  Or are they OK with others being paid to port features from DSpace-CRIS? If this is reassigned, we'll need to address the imbalance of work above.
    3. Upgrading to Angular (v10 goes EOL on Dec 24): 11 now ( (roughly estimated at 40-60hrs)If this work can be paid development (pending Steering approval), anyone interested in starting this work pull/1403) & Angular 12 later (likely in 7.3)
      1. Is anyone interested in starting an Angular 12 (or 13) upgrade in January, for possible inclusion at the very beginning of 7.3?
    4. Are there features which we know will need additional review/tester help?
      1. Testing DSpace 7 Pull Requests (DRAFT) - Step by step instructions to help anyone (even non-technical folks) test a PR using Docker & GitHub CLI
    5. (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.2 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.