galaxyproject / galaxyproject/foundry
Improved Structure and Schemas for Mold Artifacts
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 3
- Avg merge
- 1d 22m
- Merged PRs (30d)
- 63
Description
Originally I wanted structured YAML between every step - but we have resorted to a lot of Markdown. That seems to work okay - but I think we could do better.
- https://github.com/galaxyproject/foundry/issues/40
- https://github.com/galaxyproject/foundry/issues/48
- https://github.com/galaxyproject/foundry/issues/49
- https://github.com/galaxyproject/foundry/issues/50
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the related issues #40, #48, #49, and #50 to understand the current Markdown-based artifact structure and the proposed improvements. Define what structured YAML and schemas should cover between steps, and consider the work complete when the artifact format and its intended usage are clearly specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown, yaml
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100