Call Details

• Time: 11:00am Eastern Time (find your time here)
• Join Zoom meeting: https://duraspace.zoom.us/j/740695413
•  - Indicates who will be taking minutes

Attendees

• Andrea Bollini (4Science)
• Bill Branan
• Heather Greer Klein
• Nicholas Woodward
• Courtney C. Mumma

Agenda

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

1. Review priority list, determine what is in scope for sprint: JIRA priority list
   1. Can see list of all selected items on Kanban board
2. Review existing documentation, consider the greatest needs
   1. Wiki docs: https://wiki.duraspace.org/display/DURACLOUD
   2. Github deployment docs: https://github.com/duracloud/deployment-docs
   3. Github project intro docs: https://github.com/duracloud/duracloud/blob/master/README.md

Reminders

1. Development sprint: October 15-26

Minutes

• Priority list; look at items marked selected for development, these will be part of the sprint
  • Rebuilding the sync tool would not be a two week activity, but we could do planning and design work. We would really need to talk to users for these features. 
  • Could we use those two weeks for user feedback? Adding a ticket for initial customer discussion of sync tool needs. Want to simplify. Would like to make retrieval equally easy.
  • For 1192, requires more consideration of how best to address this design issue. AWS has you type your space name. A bolder, bigger warning that you are deleting a space would also potentially help. Bill: like the idea of following AWS lead and requiring space name. Would affect multi-space deletion. Moved to selected for development
  • 1177 MC emails are what TDL would like to customize. Moved to selected for development. Will prioritize the list at the beginning of the sprint. 
  • 1160: not actually a TDL priority
  • 1150: no longer a priority
  • 1087: need to consider at what granularity we would want to address errors. More important to determine user sync tool needs
  • 1074: nice to have but not a priority for this sprint
  • 922: important but can't be addressed in this sprint
  • 831: also a nice to have, impacted by need. Is this something users want to do? Something to capture from user needs
  • 623: straightforward
• Documentation greatest needs: 
  • wiki is the most complete, but most in need of review. 
  • Github documentation is incomplete
  • How do we ant people to interact with the documentation? Developer vs user. User documentation on the wiki, deployment on Github. Makes it easier to review changes when on Github. 
  • ACTION: Courtney and Heather will walk through documentation for users, TDL and the DuraSpace. Select documentation that needs addressed, and which will be priorities for development.
    
    

Actions

• Courtney and Heather will walk through documentation for users, TDL and the DuraSpace. Select documentation that needs addressed, and which will be priorities for development.