Page History

...

Agenda

• (55 mins) General Discussion Topics
  1. DSpace 7.4 will be a Maintenance Release, but will accept donated features. It will also try to include features which were initially developed for 7.3, but were not included in that release (see list below under bullet 3).
     1. DRAFT deadlines are above.
  2. Assigning Development Work for 7.4: See also 7.4 Project Board
     1. Maintenance tasks we feel should be included in 7.4 (Below, please include links to tickets or brief descriptions of issues you feel need to be prioritized highly)
        1. Curation Tasks are not very usable from the Admin UI: their results are only sent to dspace.log https://github.com/DSpace/dspace-angular/issues/1322 and they cannot restore deleted objects https://github.com/DSpace/DSpace/issues/7956 and cannot run on items https://github.com/DSpace/DSpace/issues/8384
        2. Resource Policy edit form is confusing & have usability issues.  See for example https://github.com/DSpace/dspace-angular/issues/1704 and https://github.com/DSpace/dspace-angular/issues/644 (which is not policy specific but is reproducible when editing a policy)
        3. Improve password requirements/management. See for example these tickets https://github.com/orgs/DSpace/projects/18?card_filter_query=label%3A%22authentication%3A+password%22
        4. Provide a way to manage/cleanup Processes, e.g. https://github.com/DSpace/DSpace/issues/7974 and https://github.com/DSpace/dspace-angular/issues/1343 and https://github.com/DSpace/dspace-angular/issues/1660
        5. Issues with file download from submission/workflow, see https://github.com/DSpace/dspace-angular/issues/1644 and https://github.com/DSpace/DSpace/issues/8378
        6. General caching issues, e.g. https://github.com/DSpace/dspace-angular/issues/644 and https://github.com/DSpace/dspace-angular/issues/742 and https://github.com/orgs/DSpace/projects/18?card_filter_query=label%3A%22performance+%2F+caching%22
        7. Statistics display issues, e.g. https://github.com/orgs/DSpace/projects/18?card_filter_query=label%3A%22component%3A+statistics%22
        8. (Possibly) Restrict system managed metadata fields from editing: https://github.com/DSpace/DSpace/issues/8299
  3. Assigning Reviewers for 7.4: See also 7.4 Project Board
     1. Feature PRs which missed 7.3 (will be considered for 7.4)
        1. Recent Submissions Listing on Homepage (Tier 2, donated, smaller PR): https://github.com/DSpace/dspace-angular/pull/1632
        2. SAF (Simple Archive Format) Import/Export from UI (Tier 3, highly-prioritized by Steering, medium PR): https://github.com/DSpace/DSpace/pull/8318
        3. OpenAIRE Graph "quality assurance" (notification broker) feature (Tier 4, donated, large PRs): https://github.com/DSpace/dspace-angular/pull/1562 and https://github.com/DSpace/DSpace/pull/8184
           1. As a large, donated feature, this PR requires discussion/approval for 7.4. (NOTE: It has been reviewed already by two Committers)
        4. OpenAIRE "suggestions" (publication claim) feature (Tier 4, donated, large PRs): https://github.com/DSpace/dspace-angular/pull/1638 and https://github.com/DSpace/DSpace/pull/8280
           1. As a large, donated feature, this PR requires discussion/approval for 7.4. (NOTE: It has not yet been reviewed)
        5. Flexible additional metadata for MyDSpace page (Donated, small PR): https://github.com/DSpace/dspace-angular/pull/1621
        6. Amazon S3 support improvements (Arguably this is an improvement, small PR): https://github.com/DSpace/DSpace/pull/8356
        7. Port + Refactor event consumer curation code (Queuing Curation Tasks) (donated, small PR): https://github.com/DSpace/DSpace/pull/8151
• (5 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.

...