2019-05-06: Development Planning

Kacper, Craig, Mike L

  • v0.7
    • RC2 is deployed
    • Tommy did a round of testing
    • Bug review
    • Environment customization (repo2docker)
      • Use Craig’s version, but he needs to tidy up
    • Publish to DataONE
      • Testing and test case review
    • Import from BagIt
      • https://github.com/whole-tale/girder_wholetale/pull/259
      • Need review
    • UI Notification improvement
      • https://github.com/whole-tale/dashboard/pull/461
      • Needs Craig’s review
    • Dataset citation
  • v0.8
    • Restart notications
      • Still needs dashboard work
      • https://github.com/whole-tale/gwvolman/pull/66
    • Build and restart notifications
      • Refactor build notification handling based on https://github.com/whole-tale/gwvolman/pull/66/files
      • Update UI to handle both
    • Kacper’s repo2docker
    • 3 party integration through oauth (Kacper)
      • We will use primarily for ORCID and possibly Agave or anything that requires authenticated access to data
      • After repo2docker
    • UI refactor continued
      • Copy on Launch (PR issued)
        • Needs review
      • Compose > Create modal + select data widget (Adam)
        • Somebody other than Mike needs to engage
      • Run instance refactor to tale (ML)
        • https://github.com/whole-tale/dashboard/pull/459
        • Needs review
      • Browse refactor (ML)
        • Mostly done, 1:1 with mockups
      • Notification handling refactor (ML)
        • “Parity with Girder”
        • e.g. https://github.com/whole-tale/gwvolman/pull/66
      • Manage/catalog refactor (ML)
        • Note http://www.crc.nd.edu/~kfurse/wholetale-css-mock-up-sui_f2018/browse-catalog-meta.html
      • Killing all the dead code (ML)
      • Compute environments (Tommy)
        • Depends on browse refactor
    • Other UI
      • Globus logout (under debate)
      • API keys support (for DVN and Zenodo publishing)
        • Add key-value store as UI widget
        • User settings is a sub-endpoint, but could add one specifically for API keys
        • Needs Kristina’s input
      • Changing the environment (remix)
    • Agave
      • Agave Oauth provider
        • PR needs review https://github.com/whole-tale/girder/pull/5/files
      • Agave data provider
        • In progress
    • Other already on plan
      • More real Tales?
      • TACC/Remote execution w/ labels
      • Run tale from DataONE
      • Publish to Dataverse
      • Publish to Zenodo
      • Provider refactor/redesign
      • Remote zip files (WIP)
      • Kubernetes
      • Accessing data with authentication (TDAR)
      • User namespacing system (1.4.3) (Craig)
        • Identifiers – slugs?
        • Needs requirements/design
      • Tale validation framework?
        • Run tale without home directory
      • Brown Dog integration (1.6.2)
      • iRODS = Agave ingest
      • Autodetecting changes
      • Tracking and storing provenance
        • Depends on prov task group input
      • Usability test (Craig to coordinate)
      • Terms of use (needs requirements)
      • Licenses (needs requirements and design)
      • Migrate plugins from 2.x to 3.0 (Kacper)
  • Assignments:
    • Kacper (repo2docker, Oauth, …)
      • Winding down on WT to start on CIS
    • Mike L (Finishing browse refactor, manage/catalog refactor, notification parity)
    • Adam (Create modal, select data …)
    • Tommy (prioritized bug fixes, environments, api keys)
    • Mike H (Kubernetes continued)
    • Elias (Implemented Agave oauth)
    • Craig ()
  • Issues:
    • Create modal needs additional input/review
      • Can’t reproduce
    • Tommy merged his own PR
    • UI team meeting:
      • Weds
        • Mike has 9-10am meeting
        • Kacper 11-noon
        • 10-11am or 1-2pm
      • Thursday
        • CHEESE meeting
        • Wide open