2019-09-30: Development Planning

Kacper, Craig

  • v0.8 release
    • Bug fixes (All)
    • PRs (All)
    • Release deployment (Craig/Kacper)
  • v0.9 features
    • Zenodo provider (Kacper)
    • Zenodo publisher (Kacper)
    • Agave integration (Elias)
    • User settings page with API key support (Mike L / Kacper)
      • External oauth integration (Kacper)
    • Publishing workflow changes
  • v1.0
    • Angular migration (Mike L)
    • Kubernetes Helm chart (Craig)
    • Dataverse publisher (Kacper)
  • Beyond
    • PresQT publisher (Craig)
    • Sharing (read, write, none)
      • UI mockups (in-progress, Kristna)
      • UI work (1 mo , Mike L)
      • Backend work (1 week, Kacper)
      • Email/notification subsystem (1 week, Kacper)
    • Create tale from Git repo
      • UI mockups (1 day, Kristina)
      • UI work (2 days, Mike L)
      • Backend work (1 week, Kacper)
    • C2Metadata:
      • Integrate C2Metadata with BrownDog (~, Craig)
      • Integrate C2+BD with WT (~, Craig)
      • Stata support (~, Craig)
        • Arrange a license with stata (system-wide license)
          • Discuss BYO – would need UI
        • Implement a stata environment in WT
      • Matlab support (2 weeks, Craig)
        • Add Matlab environment
        • Need cases for extending matlab (Matlab buildpack)
      • Provenance special sauce (~, Tim)
      • Metacat extension for C2Metadata (~, Tommy)
    • Prov WG output
      • “Reproducible run”
        • UI mockups
          • Button that runs an entrypoint
          • UI to display output (e.g., container logs)
        • UI work (Mike L)
        • Backend (Mike H)
          • A way to run a tale non-interactively
          • Capture outputs / run information
        • Design
      • System provenance capture
        • Part of reproducible run backend (Kacper)
      • Preserving images (needs design, Mike H)
        • Run Docker locally, store everything that has a DOI
          • Must be used in reproducible runs
          • Must be published?
        • Are we minting our own DOIs?
          • If we preserve the image, why do we need a publisher?
      • Provenance queries (Tim)
      • UI for r2d config (Mike L.; potential non WT contribution)
    • Direct linking to tales (DOI resolution)
    • Publishing refactor (drafts, curated workflows)
    • RO-Crate migration