Versions Compared

Key

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

...

  • (40 mins) Discussion Topics If you have a topic you'd like to have added to the agenda, please just add it. 
    1. Planning for 8.0 (Summary from Steering meeting yesterday)Goals for 8.0Move forward major features which missed 7.x. 
      1. COAR Notify support (4Science & Harvard)
      2. OpenAIRE integration with notification broker/claim service (4Science)
      3. Porting "REST-Based Quality Control Reports" from old REST API to new one. (U of Laval, Canada)
      4. Duplicate Detection in Submission ported from DSpace-CRIS (The Library Code)
    2. Include new features which empower users in the admin UI.  Make things easier for Admins.
    3. Improve documentation, training to allow for greater community contributions.  (Ease setup/install/customization, etc.)
    4. Angular upgrade/maintenance. Spring upgrade/maintenance. Solr upgrade/maintenance, etc.
    5. Possibly need cleanup of Submission Refactor to support Angular upgrade. https://github.com/DSpace/dspace-angular/issues/858
      1. Library used to create the Submission form may need updating?
    6. Timeline for 8.0 release: April 2024
    7. In parallel, proof of concepts / planning regarding modularization (e.g. 4Science angular proposal) and OCFL/preservation storage (Lyrasis proposal to be discussed in more detail).
    8. Planning for 7.6.x releases release topics - bug-fix fixes only.   
      1. Development process reminderTim will bring to Steering the suggestion to switch post-7.6 release numbering to 7.6.1, 7.6.2, 7.6.3 (for eventual bug fix release). This clarifies that 7.6 is the final feature release, and that every later release is a minor upgrade.
        1. Two development branches: dspace-7_x and main  & new "port to 7.x" and "port to main
         
        1. " labels
        2. Two project boards in GitHub: DSpace 7.6.x Maintenance and DSpace 8.0 Release
        Revisiting code review process brainstorms: See Incentivizing Code Reviews and PR Testing
    9. 8.0 release topics
      1. Anything new to discuss?
    10. (No Updates) Demo Site migration to Lyrasis (https://demo7.dspace.org/ and https://api7.dspace.org/server/)  
      1. Tim will work with Lyrasis to make this happen as soon as reasonably possible now that 7.6 is released.
      2. Demo site will be renamed back to "demo.dspace.org" (instead of "demo7.dspace.org"). 
    11. Future meeting discussions for 8.0
      1. 4Science proposed to present
        1. COAR Notify on July 13th 2023
        2. ORCID Login improvement on July 20th 2023
        3. Angular : library-based architecture proposal updated proposal on July 20th
    12. (Other topics?)
  • (20 mins) Board Review & assignments:
    • Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
    • 7.6.1 Project Board - Assign new PRs to volunteers to code review and/or test.
    • 8.0 Project Board - Assign new PRs to volunteers to code review and/or test.

...

  1. Move forward major features which missed 7.x. 
    1. COAR Notify support (4Science & Harvard)
    2. OpenAIRE integration with notification broker/claim service (4Science)
    3. Porting "REST-Based Quality Control Reports" from old REST API to new one. (U of Laval, Canada)
    4. Duplicate Detection in Submission ported from DSpace-CRIS (The Library Code)
  2. Include new features which empower users in the admin UI.  Make things easier for Admins.
  3. Improve documentation, training to allow for greater community contributions.  (Ease setup/install/customization, etc.)
    1. Per DSpace 7 WG meeting on June 29, 2023, this may include dependency upgrades/maintenance (Angular, Spring, Solr, Tomcat, etc).  May also include necessary code updates/refactors to ease in ongoing maintenance. 
  4. Release Goal: April 2023
  5. In parallel to 8.0, proof of concepts / planning regarding modularization (e.g. 4Science angular proposal) and OCFL/preservation storage (Lyrasis proposal to be discussed in more detail).

Goals for 7.6.1

  • Bug/security fixes only.  Release will occur when sufficient fixes have been made to warrant a release.
  • Fixes MUST be applied to the "dspace-7_x" maintenance branch (for either backend or frontend)
  • Fixes MUST be either cherry-picked to "main" branch (for 8.0) or copied into a PR against "main".

...