Page History

...

• (30 mins) General Discussion Topics
  
  1. Planning for 7.6. Summary of discussions out of yesterday's Steering Meeting
     1. Steering recommendations:
        1. 7.6 should be the final 7.x release with any new features.  Starting with 7.7, only bug fixes / security fixes will be allowed in 7.x
        2. 7.6 should concentrate on feature parity with 6.x.  Donated features should only be accepted if they align with that feature parity goal.
        3. Brand new features (not previously in 6.x) should be rescheduled for 8.0.  However, 8.0 development would begin as soon as 7.6 is completed, so these features could be added to the codebase as soon as 7.6 is completed.
     2. Features Steering feels are required for 7.6 which need an estimate
        1. Bulk access control management (previously called "Advanced Policy Manager" in 6.x) - The ability to modify policies on several items/bitstreams at once. (UI ticket #781,REST ticket #2848)
           1. Ideally, we should scope this to be as simple as possible to achieve the same "use cases" in DSpace 7. The feature can be redesigned but also should be simplified.
           2. Known Use Cases include: (Neither of these are currently possible in 7.5)
              1. Access restricting (or giving access to) all Items in a Collection, 
              2. Access restricting/embargoing (or giving access to) all Bitstreams of all Items in a Collection.   
              3. Replace all polices or append to existing policies in either use case
              4. (4Science addition: modify all policies within a single Item to restrict or access restrict all in a single Item. Similar to Submission or Workflow you could use access settings.)
        2. (NOTE: All other outstanding 6.x features are considered optional, but anyone can choose to donate these features to 7.x in time for 7.6)
  2. Demo Site maintenance (https://demo7.dspace.org/ and https://api7.dspace.org/server/)?  
     1. UPDATE: LYRASIS is still working on this, but some restructuring of plans has had to occur because of internal deadline changes.  Likely not to be completed until March or April.
     2. In the meantime, can we ensure that it is still possible to send updates to both the frontend & backend per instructions at Updating DSpace 7 Demo Sites ?
  3. (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.5 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

...