-
Notifications
You must be signed in to change notification settings - Fork 88
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
New organization and maintainer 🎉 #408
Labels
Comments
100terres
added a commit
that referenced
this issue
Aug 23, 2022
see: #408 BREAKING CHANGE: The project is moving to a new home! From react-forked organization to hello-pandea. Here's the new project name on npm: @hello-pangea/dnd
LGTM Super excited for the future of this repo :) |
100terres
added a commit
that referenced
this issue
Aug 24, 2022
see: #408 BREAKING CHANGE: The project is moving to a new home! From react-forked organization to hello-pandea. Here's the new project name on npm: @hello-pangea/dnd
100terres
added a commit
that referenced
this issue
Aug 24, 2022
see: #408 BREAKING CHANGE: The project has a new home! From react-forked organization to hello-pangea. You should install @hello-pangea/dnd package instead.
100terres
changed the title
New organization and maintainer 🎉
[WIP] New organization and maintainer 🎉
Aug 24, 2022
100terres
changed the title
[WIP] New organization and maintainer 🎉
[v16] New organization and maintainer 🎉
Aug 25, 2022
100terres
changed the title
[v16] New organization and maintainer 🎉
[v16.0.0] New organization and maintainer 🎉
Aug 25, 2022
This was referenced Aug 27, 2022
Blog post is live: https://dev.to/100terres/whats-up-with-rfd-578a |
+1 thanks for this hit the react 18 error today and this was a super simple swap out helped a ton. |
100terres
changed the title
[v16.0.0] New organization and maintainer 🎉
New organization and maintainer 🎉
Sep 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello fellow GitHubers 👋
As some of you might have noticed, it can be difficult to manage a complex open source project alone and it can have an impact on how long it takes to fix issues. Like for the issue with react 18! Again sorry to have kept you waiting for weeks without any answer. 😞
To make sure it doesn't happen again and to help with all the work ahead of us on this project, we are welcoming a new maintainer @Xhale1 🎉 Thanks to him we have a working version with react 18. (I love the open source community ❤️)
We also plan in the future (sooner than late) to give second life to other un-maintained projects we like and want to keep alive. Some of those projects might not be react related. For this reason we'll rename and move the project to a new organization. This organization is named hello-pangea! If you want new feature and bug fixes, you should plan to migrate to
@hello-pangea/dnd
. The migration will be as simple as doing a find and replace!If you want to be a part of this new adventure let us know on discord 👉 https://discord.gg/zKhPpmvCEv
Thank you for your support!
Here's a rough list of what's needed to begin this new chapter:
@react-forked/dnd
to@hello-pangea/dnd
https://github.com/react-forked/dnd
tohttps://github.com/hello-pangea/dnd
hello-pangea/dnd
repo tohello-pangea/dnd-old
dnd.react-forked.com
todnd.hellopangea.com
@react-forked/dnd
on npm to let people know they should use@hello-pangea/dnd
instead of@react-forked/dnd
mentioning the blog post (using npm deprecate command)The text was updated successfully, but these errors were encountered: