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

Detach fork and make a standalone sandpaperL2D package #93

Closed
milanmlft opened this issue Jul 3, 2024 · 3 comments
Closed

Detach fork and make a standalone sandpaperL2D package #93

milanmlft opened this issue Jul 3, 2024 · 3 comments

Comments

@milanmlft
Copy link

I think that this fork has diverged enough from https://github.com/carpentries/sandpaper to warrant detaching it. This would allow us to have our own version numbering, releases, and make it possible for someone to have both the Carpentries and L2D packages installed at the same time in their local R environment, avoiding confusion.

We may have to go through GitHub support to preserver Issues, PRs and other metadata linked to this fork.

@milanmlft
Copy link
Author

@sabaferdous12 I don't see why you would want to create a new organisation? Also, that's not really related to this issue/suggestion, so could we have that discussion in a different thread?

@DrAdamLee
Copy link

I think that this fork has diverged enough from https://github.com/carpentries/sandpaper to warrant detaching it. This would allow us to have our own version numbering, releases, and make it possible for someone to have both the Carpentries and L2D packages installed at the same time in their local R environment, avoiding confusion.

We may have to go through GitHub support to preserver Issues, PRs and other metadata linked to this fork.

Hi Milan - this sounds like a very sensible idea, and would definitely make things a lot clearer, thank you!

@milanmlft
Copy link
Author

milanmlft commented Jul 4, 2024

Discussed this further with @dpshelio and decided against it. Instead we should improve the setup and write some documentation on good practices of how to deal with long-term forks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants