Call Details

Attendees

Agenda

(If you have an agenda suggestion/addition, please leave a comment!)

  1. Status of current/planned development: Kanban board
  2. TDL pain points
    1. Release notes need to be more complete - this will need to be an on-going action for the team

    2. Secondary storage provider should have options to create spaces and store content (DURACLOUD-1201)

    3. Synctool: need a way to clear the stored config (to perform a clean start)

    4. SyncTool: there should be tooltips that help in understanding the options

    5. Management Console: Need options to customize emails for registration

    6. More informative error handling - more details needed here

    7. Upgrading javascript dependencies in the UI - discussion of this suggested that there may not be sufficient benefit for the cost/effort

  3. DuraCloud documentation, sharing access and responsibility

    1. User documentation (wiki)
    2. Deployment documentation (github)
  4. Reviewing and prioritizing JIRA list; using labels to indicate high priority

  5. Activity planning for community sprint in October

Reminders

  1. Sprint planning day: October 5th
  2. Development sprint: October 15-26

Minutes

  1. Nicholas Woodward is not seeing the missing storage statistics that we are seeing on the DuraSpace side.
  2. Proof of  concept for streaming work is moving along nicely.  
    1. Still some open questions related to managing security for distributions
    2. It's looking like we will be adding in hls streaming alongside the rtmp method, rather than removing it right away.  RTMP will be deprecated.
  3. TDL Pain points:
    1. Synctool clean starts - Nic to create ticket.
    2. More Synctool tooltips? 
    3. Email templates for customizing management console new user emails
    4. Updating / upgrading the UI vs green field development
      1. If we ever got serious about faceted search,  green field might be the way to go.
  4. Documentation 
    1. Feel free to jump in and make improvements tot he user and deployment documentation
    2. As releases have become more granular we simply update the wiki when new code is released.
    3. Nicholas Woodward and Courtney C. Mumma : any interest in improving the documentation? 
  5. Use labels to indicate ("duraspace-priority",  "4science-priority", "tdl-priority") community interest in particular jiras.
  6. October sprint planning to happen later.

Actions

  • No labels