-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
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 !! |
I just migrate a project from recoil to jotai without any issue , API is very simillar |
I love the Idea |
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.
The text was updated successfully, but these errors were encountered: