2019-06-03: Development Planning¶
Kacper, Craig
v0.7¶
- Backend PRs approved
- repo2docker
- Fork + autobuild + release
- Dockerfile in repo2docker_wholetale + autobuild + release
- Spark + OpenRefine testing
- Download/run local
- Release + deploy to stage + final test
- Deploy to prod + migration
Dev planning¶
- Plan for all-hands meeting
- Share/remix frontends
- Ability to add new base environments
- Matlab support …SPSS, SAS
- Import/re-run Tale from DataONE
- Ability to change environment
- Kubernetes
- Secure routes
- Additional publishing targets (Zenodo, Dataverse)
- Mockups
- API keys
- Oauth integrations
- Supporting anonymous review
- Needs requirements
- Anonymous review can run stuff and provide feedback to editor
- Editor can see if reviewer ran and did stuff
- Tale validation
- Was running without home
- Export locally
- Track provenance
- Needs requirements
- Migrate to Girder 3
- Issue, resolve, track identifiers
- Extract metadata
- Federated queries
- Organize into user-defined namespaces
- Cyverse + DesignSafe integration
- iRODS is now Agave!
- User experience testing
- Brown Dog integration (C2Metadata supplemental)
- Tales at Scale
- Native support for WT in Jupyter and RStudio?
- OAI-ORE
- CLI for Whole Tale?
- FUSE, R, Python libs for DOIs?
- Share/remix frontends
- Discussion of review workflow
- 3 actors: author, editor, reviewer
- Author creates tale and shares with editor
- Editor makes copy and shares with reviewer
- Reviewer runs editor’s copy of the tale
- Reviewer follows checklist
- Editor can copy feedback to original tale
- Q. How to iterate without creating a new copy each time?
- Q. We somehow need versioning?
- Discussion of publishing design
- Who’s doing what
- Kacper:
- Pending/rotting PRs:
- Import tale
- Copy on Launch
- Instance update
- Data directory
- Pending/rotting PRs:
- Craig:
- v0.7 PR review and testing
- Mike L:
- Notification refactor
- Browse refactor
- Pending PRs
- Run view refactor
- Copy on Launch
- Possible:
- Kubernetes review
- Mike H:
- Kubernetes POC
- Tommy: *
- Adam:
- Create tale is done
- Possible:
- Get involved with PR review (Copy on Launch and Run view refactor)
- Cleanup: Fix linter errors, Killing dead code
- Elias:
- Agave data provider in progress
- Things that can be worked on
- Refactor notifications in both backend and UI for register data, import tale, stop instance, publishing?
- Register data: refactor to use local jobs, UI changes to get away from black toast (delete dead code?)
- Import tale: refactor to use chained jobs; UI changes because custom progress/panel is unnecessary
- See also:
- https://github.com/whole-tale/girder_wholetale/issues/152
- API keys for publishing (need design/mockups)
- Manage/catalog refactor
- Note http://www.crc.nd.edu/~kfurse/wholetale-css-mock-up-sui_f2018/browse-catalog-meta.html
- Changing the environment (remix)
- UI selection is easy, but needs to trigger something on the backend
- https://github.com/whole-tale/girder_wholetale/issues/268
- More real tales (Tommy?)
- Compute environments (needs design/mockups)
- Killing all the dead code (ML)
- Compose shouldn’t build
- https://github.com/whole-tale/girder_wholetale/issues/288
- Maybe unnecessary
- Issue triage and closing
- Globus publish will be broken
- Refactor notifications in both backend and UI for register data, import tale, stop instance, publishing?
- Kacper: