Idea #15105
open
[Spike] Evaluate alternatives for Composer functionality in Workbench2
Added by Tom Morris about 5 years ago.
Updated about 2 months ago.
Release relationship:
Auto
- Status changed from New to In Progress
- Status changed from In Progress to New
- Story points set to 1.0
- Target version changed from To Be Groomed to Arvados Future Sprints
Had a sit-down yesterday with Kaushik Ghose from Seven Bridges at Bio-IT World.
Discussed future of Composer.
Expressed the need for a major refactor to isolate and abstract data providers and execution backends (and to a lesser extent, electron-specific features). This would require throwing out the existing Seven Bridges platform integration (since we obviously can't/won't do the work to support it). Suggested that we could do the refactoring work and contribute it back as a proposed "Composer v2". SBG would continue their ongoing maintenance of cwl-ts and cwl-svg (for example, adding upcoming cwl v1.1 support) as separate components that are used by Composer, Workbench 2, SBG platform and others.
He supports this plan, with a few requests:
- To continue to support the Electron desktop build along with a pure web build
- To include some acknowledgement / branding of the Rabix project in Arvados Composer
- To document new the data provider / execution interfaces to support their efforts to re-add Seven Bridges platform support
- Release set to 20
- Target version deleted (
Arvados Future Sprints)
- Release changed from 20 to 60
- Target version set to Future
Also available in: Atom
PDF
Updated by Tom Morris 
Updated by