-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove nf-core branding from pipeline template #1548
Comments
What was brought up in the discussion as well, is to add a flag when creating the pipeline to avoid the branding. Maybe it is easier to have options in the various jinja templates that avoids creating the files/sections related to branding. |
What kind of stuff do you guys consider branding? I can think of obvious things like the logo in the readme, but not so much beyond that. Do you care about things like |
We should collect a list of any filenames, variables, comments, images that are using "nf-core" / "Nfcore" / etc and ideally replace as much as we can either with |
Naming them for their purpose irrespective of nf-core gets my vote 👍🏼
Good question 🙂 Things I thought of:
I think it would be fair to add a footer in the README that says, "generated with the nf-core tools template" or a similar message on non-branded projects. This is quite common, provides some attribution, but doesn't cause confusion on whether a project is nf-core or not. |
Closing due to merge of #1551. |
Description of feature
It would be awesome if we can have an option to remove the nf-core branding when creating pipelines and for this to work with all of the existing tooling we have.
A few members in the community including myself have created a number of pipelines now using the template but they arent likely to be contributed back to nf-core. Having this option saves having to manually replace bits everywhere.
We have some docs to do this manually on the website here but the idea is to replace most of this with a single command! 🔥
@robsyme (just sent you an invite to become a member of the community 🚀 ) has offered to help with the implementation.
I will let him fill in the details but some preliminary discussion was initiated on Slack here
The main complication will be how we get downstream tools like the linting, sync etc to play nicely with non-nf-core branded pipelines. We should add tests for this via Github Actions.
The text was updated successfully, but these errors were encountered: