Skip to content
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

Rename repo #30

Open
falexwolf opened this issue May 1, 2024 · 3 comments
Open

Rename repo #30

falexwolf opened this issue May 1, 2024 · 3 comments
Assignees

Comments

@falexwolf
Copy link
Member

I don't see us maintaining two repositories for Nextflow integration.

Can we just rename this one to nextflow-lamin so that we have a memorable short github URL for it?

I'll also rename https://github.com/laminlabs/redun-lamin-fasta; not a priority but during the next refactor.

@Zethson
Copy link
Member

Zethson commented May 1, 2024

Yes, let's do it

@Zethson Zethson self-assigned this May 31, 2024
@Zethson
Copy link
Member

Zethson commented Jun 3, 2024

We might also have

nextflow-lamin-module or nextflow-lamin-plugin in the not so distant future. These would need their own repositories or it would get messy here quick (they'd be written in Nextflow). I would actually not rename this for now.

@Zethson Zethson closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 2024
@falexwolf
Copy link
Member Author

But it'd still be nice to centralize things in one repo with a simple name. If we ever do something complicated like a plugin, that's going to be super technical and could have a longer name. Or it could also be managed in this repo mono-repo style, depending on the needs.

Hence, I'm still in favor of renaming, but I'm also not obsessed with it.

@falexwolf falexwolf reopened this Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants