Skip to content

Commit 329de56

Browse files
bgrueningnsoranzo
andauthored
Apply suggestions from code review
Co-authored-by: Nicola Soranzo <nicola.soranzo@gmail.com>
1 parent 2cd965a commit 329de56

File tree

1 file changed

+5
-5
lines changed
  • content/news/2026-03-13-galaxy-webhooks-tool-deprecations

1 file changed

+5
-5
lines changed

content/news/2026-03-13-galaxy-webhooks-tool-deprecations/index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,19 +16,19 @@ contributions:
1616
Galaxy instances accumulate history. That is a strength, but it also creates a familiar problem:
1717
Some tools remain scientifically valid and still need to run for old workflows to enable
1818
reproducibility, while newer alternatives are often faster, have better defaults or are easier to
19-
use. Removing the older tool outright risks breaking reproducibility. Leaving it untouched means
19+
use. Outright removing the older tool risks breaking reproducibility. Leaving it untouched means
2020
users keep selecting them out of habit.
2121

2222
One practical answer is a soft deprecation layer in the Galaxy tool form itself.
2323

24-
Galaxy already supports site-specific UI extensions through [webhooks](https://docs.galaxyproject.org/en/master/admin/webhooks.html). The same pattern can be used to add a contextual information to
25-
specific tools. When a user opens an older (still functional tool) Galaxy can display a short
24+
Galaxy already supports site-specific UI extensions through [webhooks](https://docs.galaxyproject.org/en/master/admin/webhooks.html). The same pattern can be used to add contextual information to
25+
specific tools. When a user opens an older (still functional) tool, Galaxy can display a short
2626
notice explaining that the tool is retained for compatibility, why it is no longer the preferred
27-
choice, and which replacement should be used instead.
27+
choice, and which replacement tool should be used instead.
2828

2929
We want to: preserve execution, but improve defaults.
3030

31-
The `FastQC` to `Falco` transition on the European Galaxy server is a good example. `FastQC` has
31+
The `FastQC` to `Falco` transition on the European Galaxy server is a good example. `FastQC` is a quality control tool for high-throughput sequence data which has
3232
been executed more than two million times over the years and is still deeply embedded in many
3333
sequencing workflows. But `Falco`, published in 2021 as a reimplementation of `FastQC`, is roughly
3434
three times more efficient. When `Falco` first appeared on the European Galaxy server in June 2024,

0 commit comments

Comments
 (0)