2012-02-06 DfR Technical Meeting

Regular Attendees

• Andrew (off the road again - hemi-powered covered wagon)
• Bill
• Brad
• Chris
• Dan
• Jonathan

General

• Call In To: Free Conference Call HD - DuraCloud Line

  Please note that we will be using the Free Conference Call HD line for this call. Information about calling into this line is available from the link above.

• - Indicates who will be taking minutes

Discussion Topics

Planning Board
Task Board

Actions from last meeting

Last meeting

Budgetary Estimates - Jonathan
Prepare Epics - Dan and Brad
Prepare Stories with Estimates - All
Get the Jira Up to Date - Dan

Related Information
DfR Software Next Steps - Jan 2012
2012-01-03 - Architecture Meeting, Temple University

Status

• Jonathan
• Andrew
  • DuraCloud/Shib architecture updates
• Bill
• Brad
  • Unicon call
• Chris
• Dan
  • Worked out a strawman approach to Jira and most of the team +1 (Andrew on the road)
• Jonathan

Minutes

• Project and Partner overview (Jonathan)
  • Narative document to go out to partners, please read and make suggestions and/or corrections
  • Had advisory meeting on Friday, went pretty well, with Michael Altman, Sayeed Chadhury, Sandy Payette, Madeline Wessel
    • Micah's narative response, not really seeing distinction between box or dropbox, need to clarify how we are different
    • Will be hard to sell the service is it's not clear what our differentiators are
    • Need to determine how we will handle the restore feature, need to get feedback from interested parties
    • We should really emphasize the privacy and security features: Be clear about what kinds of data should be stored in this system
      • Jonathan: Is the onus here on those pushing data in, or on those providing the storage system?
      • Dan: We have tools to create redacted versions of content, could be done by the researcher or within DfR
  • Need to start developing the public wiki
    • Would like to see Carissa become more familiar with DfR and perhaps help with this effort
  • Have not resolved Fluid issues
    • If we pay as a subcontractor, would be required to pay a 40% overhead fee
    • Email into Sloan to try to resolve this
    • Still need to determine how Fluid will be involved with the Smithsonian work, need to arrange a discussion
  • Dan: Would be useful to have a wiki page listing partner relations and the DfR advisors
• UNICON
  • Big pointer to Apache Shiro
  • Would suggest a big CAS server as the center-piece
    • Plug-ins are well proven for CAS, for Shibboleth and for social media connections
  • Standing by to hear if we'd like their help as design consultants and/or implementors
  • We need to do our homework to determine how we'd like to do the work
• Looking at issues (Planning Board)
  • We have a number of epics, stories, and other jira types currently in the mix - determined in the chat last week (and captured on the wiki)
  • Trying to keep the process simple at this point
  • Have epics with some stories, need to continue to generate stories and break those down to tasks
  • Need to get story points assigned to epics
  • We have about 138 working days available until the end of the grant
    • Jonathan used 30% overhead to subtract from the actual work days
    • Note that none of us are 100% on DfR
  • Want to avoid tying working days and story points too closely
  • Not planning to schedule anything today, just attempting to budget
  • DfR-18 - Determined 20 story points
  • Would like to be able to get some of the stories under way for development
  • DfR-7 and DfR-12
    • Assuming that integration will be at the file system level
    • Assuming that integrations with systems like Box or DropBox will be done via the file system (i.e. no additional work needed)
    • Windows/Mac/Linux all necessary (what about iOS or Android?)
    • client side encryption included
    • auth integration with Shib included
  • Need to prioritize stories and start getting group-based story point estimates

Actions