Is the Nextflow Registry intended for individuals as well as organizations?

Hi all,

Thanks for putting so much effort into the new changes for Nextflow. I have what is probably an easy question: Who is the intended audience for registering and using the module registry? In talks and presentations, it sounds general; but when looking at the registry, it seems very much geared towards organizations and teams. nf-core modules dominate the recently updated which is expected given how many are maintained, but I haven’t really seen any updates that seem like an individual user.

So, all of that is to say: How should individual users who regularly use Nextflow approach this resource? The pipeline composition portion of Ben’s talk recently seems like a great step forward, but the duplication of modules almost necessitates a user having their workflows / processes in the registry.

Thanks as always, keep up the great work!

You are more than welcome to claim a personal namespace on the registry. The registry namespaces basically function like GitHub orgs/users. Once you claim a namespace (and your claim is approved), you can publish whatever you want within that namespace because it’s isolated from everything else.

FWIW, you don’t need the registry to do pipeline composition. I didn’t mention this in my talk, but you could use e.g. git submodules to clone a pipeline into a meta-pipeline repo.

Thanks Ben, I’ll go ahead and send in a request and try it over the next few days. I had essentially taken a similar approach to the nf-core modules repo for maintaining those processes / subworkflows, so I’ll be interested to see how I can gradually implement the recent announcements into development.