Jonathan Manning
09/18/2025, 1:56 PMJose Espinosa-Carrasco
09/18/2025, 2:03 PMJose Espinosa-Carrasco
09/18/2025, 2:03 PMJonathan Manning
09/18/2025, 2:06 PMJonathan Manning
09/18/2025, 2:07 PMJose Espinosa-Carrasco
09/18/2025, 2:08 PMJonathan Manning
09/18/2025, 2:10 PMJose Espinosa-Carrasco
09/18/2025, 2:13 PMJose Espinosa-Carrasco
09/18/2025, 2:14 PMJonathan Manning
09/18/2025, 2:18 PMEdmund
09/18/2025, 7:07 PMSimon Pearce
09/19/2025, 5:14 AMJames Fellows Yates
09/19/2025, 6:21 AMJames Fellows Yates
09/19/2025, 6:22 AMJames Fellows Yates
09/19/2025, 6:22 AMJames Fellows Yates
09/19/2025, 6:23 AMJames Fellows Yates
09/19/2025, 6:23 AMJonathan Manning
09/19/2025, 8:21 AMno reason why not to have other proteomics pipelines within nf-coreWhat about the one-pipeline-for-one-thing thing? Surely we can't have another one occupying exactly the same space?
why do the Altos people specifically want something within nf-coreI'm extrapolating slightly, but I think Altos perceive the workflow as no longer part of nf-core, they're a big supporter of the nf-core community, and they'd rather support development within that community framework than within the arbitrary fiefdom of another org
James Fellows Yates
09/19/2025, 8:30 AMJonathan Manning
09/19/2025, 8:39 AMJames Fellows Yates
09/19/2025, 8:40 AMMaxime Garcia
09/19/2025, 8:42 AMJames Fellows Yates
09/19/2025, 8:45 AMJames Fellows Yates
09/19/2025, 8:45 AMJames Fellows Yates
09/19/2025, 8:45 AMJonathan Manning
09/19/2025, 8:48 AMRike Hanssen
09/19/2025, 10:54 AMI can't remember if we transferred the repo to them or not, but we shouldn't have. It sets a bad precedent if you can just throw up your hands and walk away with an nf-core repo.it was never moved to nf-core but was always a fork. This is from earlier days when we were less stringent on enforcing it
James Fellows Yates
09/19/2025, 10:54 AM