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

Forking This Repository #2327

Open
mbougarne opened this issue Nov 21, 2024 · 5 comments
Open

Forking This Repository #2327

mbougarne opened this issue Nov 21, 2024 · 5 comments

Comments

@mbougarne
Copy link

We want to create a new repository and start building it from scratch based on the functionality of existing code with TypeScript instead of JS and Flow, Tsup and EsBuild instead of Babel, ViTest in place of Jest, removing some packages, end support of some Node version like Node 16.x, stop supporting of React 16, add support to react 19, and other stuff. But we'll start from scratch and add the main code of Recoil to the new repository from this one with refactoring, updates, and bug fix. We'll try to address all the PR on this repo in the new one, with total respect to all the maintainers, we'll refer to this repository, and we'll go with the main website as a documentation.

Is this okay? I mean, it's ethical? To start from scratch based on this code and give credit to all the maintainers.

@uchar
Copy link

uchar commented Nov 24, 2024

I think the more unethical thing is that they start a project that thousands of people rely on, build layers of code on top of it, and then facebook suddenly stop developing it !!
As a result, a large portion of people apps needs to be refactored, and thousand hours of work will be wasted — a common practice for the Facebook team.

@uchar
Copy link

uchar commented Nov 24, 2024

I just migrate a project from recoil to jotai without any issue , API is very simillar

@freddydrodev
Copy link

We want to create a new repository and start building it from scratch based on the functionality of existing code with TypeScript instead of JS and Flow, Tsup and EsBuild instead of Babel, ViTest in place of Jest, removing some packages, end support of some Node version like Node 16.x, stop supporting of React 16, add support to react 19, and other stuff. But we'll start from scratch and add the main code of Recoil to the new repository from this one with refactoring, updates, and bug fix. We'll try to address all the PR on this repo in the new one, with total respect to all the maintainers, we'll refer to this repository, and we'll go with the main website as a documentation.

Is this okay? I mean, it's ethical? To start from scratch based on this code and give credit to all the maintainers.

I love the Idea

@mbougarne
Copy link
Author

@uchar I know Jotai and I used it before, but we depend a lot on Recoil, and not just us there are many as you said. That's why we go with that solution.

@tomodadomot
Copy link

There's no need to overthink or be overly cautious about it. You can even give it an original name that you like. OSS is about building and iterating. There’s no concept of destruction, just evolution.

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

4 participants