meetup notes

- [ ] Put [videos](https://www.youtube.com/watch?v=v0iSJMGXGUg&ab_channel=MariusvandenBeek) and [slides](https://docs.google.com/presentation/d/1S4v9tY5muRLV6q15WgkGRN4uzn_ebXAF41CCum9hSKs/edit) on IWC repo
- [ ] Include overview of workflow in README
- [ ] Static site

New workflows:
- [ ] Openms workflows, no news so far, holiday time
- [ ] DIA workflow proteomics, @bgruening and @foellmelanie might want to contribute ?
- [ ] VGP workflows @Delphine-L is working on this
- [ ] [Maker workflow](https://github.com/galaxyproject/iwc/pull/47) WIP

Some of the new workflows might need more processing power than we can get from github hosted runner.
(Though we might try and use the tool test data for the most expensive step ?)
Some ideas:
- Submit to real servers ?
- A pulsar endpoint ?

Would like to make it easier to find workflows from within Galaxy:
- More central TRS
- what to do about missing tools ?
- Request a tool for missing tools, send to admin ?
- Give link to install / ephemeris yaml … open issue see if someone jumps at it

For next roadmap.
- Rewrite workflow extraction, extract with labels, preview, bugs

Publishing to IWC requires coding / git experience. Lower submission threshold:
- Graphic interface for definition of test file.
- Atomic renaming, to rename tests. Extract test from invocation.

The issue names no specific source file, test, or entry point; begin by separating the checklist into independently scoped work items and reviewing the linked Maker workflow pull request. Confirm the intended roadmap with maintainers before starting, and consider the work done only when one selected item has a defined implementation target and verification steps.

Written by the indexing model from the issue text.