Call Details

• Time: 10:30am Eastern Time
• Join Zoom meeting: https://duraspace.zoom.us/j/390759464
•  - Indicates who will be taking minutes

Participants

• Bill Branan 
• Heather Greer Klein
• Nicholas Woodward
• Courtney C. Mumma
• Danny Bernstein

Reference

• Priority list: JIRA priority list
  • Can see list of all selected items on Kanban board
• Documentation:
  • Wiki docs: https://wiki.duraspace.org/display/DURACLOUD
  • Github deployment docs: https://github.com/duracloud/deployment-docs
  • Github project intro docs: https://github.com/duracloud/duracloud/blob/master/README.md

Notes

Week 1, Day 1 (10/15)

• Attendees: Bill, Nick, Danny
• Danny starting DURACLOUD-956
• Process: 
  • Test the change prior to creating the PR
  • Another developer handles the PR merging, with testing as well
  • Is there a template for the PR? Not yet, something to look. Danny to grab this from Fedora.
  • Create a PR, then put this into the JIRA as you move it to In Review. When closing the Jira, add link to the commit that resolved the issue.
  • How do we want to be handling PR merging
• Code changes, when is testing done?
  • Depends on the change. Some aren't possible to test locally. Best to test locally when that's possible.
• Courtney and Heather did meet and divided up tasks for documentation updates
• Nick starting DURACLOUD-1196 and DURACLOUD-623
• Discussion of DURACLOUD-1192, would be nice to have Heather or Courtney on the call. Decision to wait for discussion.
• Discussion of DURACLOUD-1205
  • When starting the SyncTool UI, the UI needs to get loaded before the clear button could be displayed. This is a problem because often the UI can't be displayed when something is wrong with the config.
  • Could we have an option on the loading screen? This would display before the config is loaded.
  • The loading dialog is a Swing component, which could be extended to ask the user if they want to clear config
  • There is an option to automatically start the app on OS startup, want to make sure not to cause problems in this scenario
    • If the user doesn't make a choice in a given amount of time, then the app starts with existing config. So there would be a countdown to startup, and if no action is taken, the app starts normally.

Week 1, Day 2 (10/16)

• Any tweaks we want to make to PR template: https://github.com/duracloud/duracloud/blob/master/.github/PULL_REQUEST_TEMPLATE.md?
  • Decision: This looks fine
• Nick trying to find where to get the MC host value. Seems to be in duracloud-config.properties.

Week 1, Day 4 (10/18)

• How best to use the Range header
  • Want to speed up transfers, by having parallel transfers. But we're not doing this now, so wait on it.
    • This would require more disk. Would need to keep track of order (probably temp files with a naming scheme).
    • If you do the checksum at the end, and it's not right, you'd have to throw it all away.
  • Being able to restart from where we run into a problem (re-start). This reduces the amount of content we need to re-download.
    • Danny is close to being done with this. Update to the contentstore API.
• Nick: Local deployment
  • Local deploy of DuraCloud 5.0 wars seems to work fine
  • Will swap out the Oracle JDK, to see if that makes a difference
• Nick: Picking up config file, but the file isn't available from the classloader as it's an external file
  • Use @PropertySource annotation instead, to pull from system property. Still use independent class to load the config data.

Actions

• Danny Bernsteinto share a copy of the PR template used by Fedora