Call Details
- Time: 11:00am Eastern Time (find your time here)
- Join Zoom meeting: https://duraspace.zoom.us/j/814345256
- Or iPhone one-tap : US: +16468769923,,814345256# or +16699006833,,814345256#
- Or Telephone: US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 (Meeting ID: 814 345 256)
- International numbers available: https://zoom.us/u/YQRCN
- - Indicates who will be taking minutes
Attendees
- Andrea Bollini (4Science)
- Bill Branan
- Courtney C. Mumma
- Danny Bernstein
- Heather Greer Klein
- Nicholas Woodward
- (your name here)
Agenda
(If you have an agenda suggestion/addition, please leave a comment!)
- Communicating as a group: Slack invitations sent out. Anyone else that should be invited to the channel?
- Status of current/planned development
- DuraSpace
- Multipart upload
- Streaming (July-Aug) and transcoding (Aug-Sept)
- 4Science
- S3 One as a distinct storage provider
- Other storage providers (ExoScale, Cynnyspace, others?)
- Cross region duplication
- TDL
- DuraSpace
- TDL pain points
Release notes need to be more complete - this is an on-going action for the team, not something to be fixed
Secondary storage provider should have options to create spaces and store content (DURACLOUD-1201)
Synctool: need a way to clear the stored config (to perform a clean start)
SyncTool: there should be tooltips that help in understanding the options
Management Console: Need options to customize emails for registration
Mill: Deployment scripts should be open sourced
More informative error handling
Upgrading javascript dependencies in the UI - discussion of this suggested that there may not be sufficient benefit for the cost
- Customer requested features (DuraSpace, TDL)
- Features that have been requested
- For each feature, assign someone to ensure the feature request is captured in JIRA
- Operational needs
- From last time: better release notes, more informative error handling, better sync tool tooltips, options to customize emails for registration in management console.
- Reviewing and prioritizing JIRA list; using labels to indicate high priority
- Activity planning for community sprint in October
Reminders
- Sprint planning day: October 5th
- Development sprint: October 15-26
- Kanban board to track activity