Skip to content

More details to specifications/pipelines/requirements/workflow_specificity page #4320

Description

@ammaraziz

I think the workflow specificity page is a tad barebone. @ewels comment here fleshes out more of the rationale behind the nf-core approach:

nf-core/proposals#134 (comment)

This is quite unique to nf-core. All pipelines are community owned and it forces people to collaborate across domains and continents on the same codebases, leading to better maintained pipelines and clearer choices for end users. For this reason, we generally try to ensure that pipelines are as generic as they can be. If a pipeline can be used and maintained by multiple groups of people, that's generally a good thing - more usage for the code and more people willing to help with development.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions