Versions Compared

Key

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

...

Agenda

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

  1. Communicating as a group: Slack invitations sent out. Anyone else that should be invited to the channel?
  2. Status of current/planned development
    1. DuraSpace
      1. Multipart upload
      2. Streaming (July-Aug) and transcoding (Aug-Sept)
    2. 4Science
      1. S3 One as a distinct storage provider
      2. Other storage providers (ExoScaleCynnyspace, others?)
      3. Cross region duplication
    3. TDL
  3. Kanban board
  4. TDL pain points
    1. Release notes need to be more complete - this

  5. is
    1. will need to be an on-going action for the team

  6. , not something to be fixed
    1. Secondary storage provider should have options to create spaces and store content (DURACLOUD-1201)

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

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

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

  7. Mill: Deployment scripts should be open sourced
    1. More informative error handling - more details needed here

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

    1. /effort

  8. DuraCloud documentation, sharing access and responsibility

    1. User documentation (wiki)
    2. Deployment documentation (github)
  9. Customer requested features (DuraSpace, TDL)
    1. Features that have been requested
    2. For each feature, assign someone to ensure the feature request is captured in JIRA
  10. Operational needs
    1. From last time: better release notes, more informative error handling, better sync tool tooltips, options to customize emails for registration in management console.
  11. Reviewing and prioritizing JIRA list; using

  12. labels
  13. labels to indicate high priority

  14. Activity planning for community sprint in October

Reminders

  1. Sprint planning day: October 5th
  2. Development sprint: October 15-26
  3. Kanban board to track activity

Minutes

Actions

  •  

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

  •   Nicholas Woodward to write up ticket for 2.c. (need a way to perform a clean start using the UI)
  •  Nicholas Woodward  to check in with Courtney regarding what is needed on 2.d
  •  Nicholas Woodward  to capture details for email customization in a Jira (2.e)