Hi, following some recent pipeline proposals (especially this one), I feel we should have clearer guidance on introducing pre-existing pipelines into nf-core. At the moment, the relevant guideline bars the inclusion of bespoke and proprietary workflows, but does not mention substantial general-purpose workflows initially developed outside the community. I think we should add a paragraph about this case, stressing two main aspects: • The priority for the existing nf-core pipeline in case of a clash, regardless of the relative size and complexity • The potential need for major modifications to follow the community requirements. I can try to draft a pull request, or we can discuss in the next meeting if you prefer.

yes, good point. please draft a pull request (if we don't come to it before, we should then also discuss it in the meeting)

Done, PR here. I'll appreciate community feedback on it, as we haven't discussed this in detail before and I've made inferences based on my understanding of the rules.

Looks good!

I don't think it needs a specific guideline, as it is more a corollary of existing guidelines

Agree that it doesn't need a dedicated guideline. But we could consider being more explicit in some existing guidelines. For example this one we could spell out that the first one wins https://nf-co.re/docs/guidelines/pipelines/requirements/workflow_specificity

The naming guideline already has a note about this topic, but the specificity guideline could also use one. Should we discuss it in the meeting?