<@UT486V1V1> any thoughts on maintenance for this ...
# hgtseqp
Phil Ewels
11/06/2025, 4:17 PM@Francesco Lescai any thoughts on maintenance for this pipeline? I wonder if we should consider archiving it if there is no-one realistically available to maintain it now (though clearly there is some interest in running it).
Phil Ewels
11/06/2025, 4:17 PM@Mark Pampuch - not sure if you'd be interested in doing any of the maintenance work here (basically, merging in all of the template updates)
Phil Ewels
11/06/2025, 4:20 PM@Maxime Garcia may volunteer as tribute
f
Francesco Lescai
11/06/2025, 4:21 PMhey Phil, @Simone Carpanzano has been working on it up until last hackathon.
we made a decision NOT to update the template, since the release has been working, and it’s a massive amount of work with quite frequent updates.
We actually discussed last year about all these manual merges the template PR forces maintainers to work on.
Francesco Lescai
11/06/2025, 4:22 PMrealistically, we’re happy to maintain the pipeline with minimal efforts. but at the same time, if nf-core requires a maximal kind of effort, then I’m happy to re-think the position of this pipeline. sure.
Francesco Lescai
11/06/2025, 4:23 PMI must confess that - as the first pipeline published with nf-core community as co-author - I don’t believe a special treatment is needed, but archiving it would feel as a pretty strong message
Francesco Lescai
11/06/2025, 4:24 PMthat said, I’m happy to take this (and a number of other things) offline in front of a tea 🙂
p
Phil Ewels
11/06/2025, 4:30 PMAh no worries, if someone is working on it then no need to talk about archiving
Phil Ewels
11/06/2025, 4:31 PMI was just looking at
devPhil Ewels
11/06/2025, 4:32 PMsince the release has been workingexcept.. it's not 😉 It won't launch via Seqera Platform and soon will stop launching with Nextflow versions released in 2026 (where the new syntax parser will be switched on by default)
Phil Ewels
11/06/2025, 4:33 PMThe software will be getting slowly out of date as well. As a easy first pick, MultiQC is at v1.13 and we're on v1.32 now, so the reports it generates will be missing a lot of new functionality there.
Phil Ewels
11/06/2025, 4:34 PMI sympathise that it's lots of work, the best case scenario is to try to find folks who are are using the pipeline and / or are motivated to keep it update as a community effort nf core ❤️ (potentially @Maxime Garcia and / or @Mark Pampuch in this case?)
f
Francesco Lescai
11/06/2025, 4:50 PMit’s not that I don’t see your point (don’t get me started on the platform…). most of the updates have been bottlenecked by the effort required for the template updates. that’s the honest answer here.
they’re frequent, and definitely not effortless, with a lot of manual merge error-corrections needed.
as inevitable as they might be, I don’t have a team of developers dedicated to that, we tend to focus on research 😅
the code is open-source for a reason, i.e. people are most than welcome to improve it and contribute to maintain, and even take over. and the pipeline is there because we do believe in the value of the community.
any other “organisational” decision is up to nf-core.