Prior Galaxy-related awards (CZI EOSS)
OS4LS is the inaugural OS4Science call, so no OS4Science prior awards exist. OS4LS is built by the EOSS team and inherits its structure, so EOSS is the relevant precedent corpus. The Galaxy project itself has been funded twice through EOSS. CZI’s public proposal pages are short (essentially the abstract); deeper detail would require asking the PIs directly.
1. Extending Galaxy for Large-Scale and Integrative Biomedical Analyses — EOSS Cycle 3
- PI: Jeremy Goecks (Oregon Health & Science University)
- Co-investigators: Enis Afgan (Johns Hopkins University), Nuwan Goonasekera (University of Melbourne)
- Cycle: EOSS Cycle 3 (awarded 2020)
- CZI page: https://chanzuckerberg.com/eoss/proposals/extending-galaxy-for-large-scale-and-integrative-biomedical-analyses/
Abstract (verbatim from CZI page, fragmentary):
“Extend Galaxy, a web-based computational workbench used by thousands of scientists across the world, so that it can analyze large datasets and connect with other analysis tools.”
Framing on CZI page:
“Galaxy is a web-based, open source computational workbench used by thousands of scientists across the world for a variety of biomedical data analyses, including genomics, proteomics, image processing, and systems biology.” Hundreds of deployed servers, 150+ public servers, three national servers, 250,000+ registered users, 500,000+ monthly analysis jobs.
Notes / unknowns: CZI’s published page does not list funding amount, aims, or deliverables. Goecks’ lab and the 2020 Nucleic Acids Research Galaxy update paper (PMC7319590) and the “Federated Galaxy: Biomedical Computing at the Frontier” paper (PubMed 34386295) are the publicly visible technical outputs that likely cite this award.
2. Automated Generation of Galaxy Tools — EOSS Cycle 6 (Wellcome co-funded)
- PI: Daniel Blankenberg (The Cleveland Clinic)
- Cycle: EOSS Cycle 6 (awarded 2024); co-funded by Wellcome Trust
- CZI page: https://chanzuckerberg.com/eoss/proposals/automated-generation-of-galaxy-tools/
Abstract (verbatim from CZI page, fragmentary):
“Develop software that is able to automatically integrate existing open source software into the Galaxy platform.”
Notes / unknowns: CZI’s published page does not list funding amount, aims, or deliverables. The Wellcome co-funding signals that EOSS6 expanded beyond the CZI-only pattern — a relevant precedent given OS4Science is itself multi-donor (Biohub, Wellcome, Kavli, ReSA). The natural-language framing (“automatically integrate existing open source software”) overlaps strongly with the User-Defined Tools / YAML tools work and with the workflow-state proposal’s direction.
Adjacent workflow-ecosystem awards worth reading
- Nextflow & nf-core — Cycles 2, 4, and a D&I cycle (Seqera Labs). https://chanzuckerberg.com/eoss/proposals/nextflow-and-nf-core/ (the D&I-cycle page is community-focused — mentorship, regional advocates, i18n — not technical interop)
- Common Workflow Language (CWL) — Cycles 2, D&I (Sarah Wait Zaranek, Curii). Framing: “portability of complex biomedical workflows across different clouds.”
- Snakemake — multiple cycles.
- Bioconductor — multiple cycles, training/sustainability/diversity/technical infra.
Higher-signal writeups (read these to calibrate proposals)
- “Insights and Impact From Five Cycles of EOSS” (Zenodo, 2024) — best single document on what made EOSS proposals succeed. https://zenodo.org/records/11201216
- Themes: technical + community pairing; demonstrated adoption; documentation/training as a first-class deliverable; cross-project collaboration; sustainability/maintainer support.
- CZI EOSS proposals catalog (~230 entries with one-paragraph abstracts). https://chanzuckerberg.com/eoss/proposals/
- CZ Biohub “Open Source Software for Science: Successes to Date” — narrative impact framing. https://www.czbiohub.org/life-science/open-source-software-science-impact/
- STAT sponsored summary of the 2024 impact report. https://www.statnews.com/sponsor/2024/11/26/new-report-highlights-the-scientific-impact-of-open-source-software/
- OS4Science launch announcements — establish the AI-readiness emphasis distinguishing OS4LS from EOSS:
What to ask Blankenberg / Goecks directly
The CZI pages are too thin to use as templates. Ask for: the actual proposal narrative, the aims list, budget framing (FTE allocation, fiscal-sponsor structure if any), how they handled the “demonstrated adoption” section, and what the annual-report indicators looked like in practice. Both PIs are reachable inside the Galaxy community.