react-native-draggable-flatlist
react-native-draggable-flatlist copied to clipboard
computerjazz
State of Support for this Library (last merged PR was on Feb 22, 2023)
Hi @computerjazz!
Noticing that few PRs have been approved and merged over the last two years. You're probably super busy, but I'm wondering if, for the benefit of the many who use this great library, you could share your intent with it.
Thanks!
Hi @angusryer,
I consider react-native-draggable-flatlist basically feature-complete. My goal has always been for this package to do one thing and do it well — and to that end I intend to keep its surface area as minimal as possible. You won't see multi-column drag and drop or other features that would require a large-scale rewrite (if anyone DID take on a large-scale rewrite I have some thoughts about whether FlatList was the right choice as a backing list to begin with, but that's another story...).
The PR QA/approval process for this package is tedious, since animations can run differently across devices and platforms. I've already spent way too much of my life dragging cells on the example project, watching for subtle flickering and jumping, so I tend to only pay attention to PRs that look unambiguously safe, minimal, and critical.
I use it this package in several personal and professional projects, and I intend to support it to the extent that those projects demand. If anyone in the community has a strong interest in being its champion I'd consider handing over the keys, and if that happened I would probably step away completely.
Thanks for the reply, @computerjazz!
Understood. So, in essence, you'd probably love it if someone of the right experience and gumption stepped up and offered to tug the rope. Not sure my time can be split, although the interest is there. I will reference this issue in other conversations to spread the word. Maybe this'll get noticed and the lib will continue to grow.
Thanks for putting in the hours finding all those flickers!
We rely on this project as a core part of our UX, so if you're looking for a new maintainer, I'd love to take you up @computerjazz .
If anyone in the community has a strong interest in being its champion I'd consider handing over the keys, and if that happened I would probably step away completely.
Before you hand over the keys to anyone, make sure you trust them. Be wary of the "Become a Maintainer" attack vector. You certainly do not want to repeat the history of the XZ Utils backdoor.
Sadly the project is falling apart since the amount of issues is growing and none gets resolved. It just doesn't work on the latest React Native / Expo since many months now.
As you mentioned in your post @computerjazz, you are open for a new champion to hand over the project. Do you already have a possible (reliable) candidate?
As I read my comment again, I realize it might have a bit too much "Dutch directness" in it, I'm sorry.
I really appreciate the effort you've put into this project. A lot of people, including myself, benefit from it, and that deserves a lot of respect. Thanks for everything and I hope your work can be continued. ❤
Hey no worries @BenGroot and thanks for the followup -- I would love for a champion to take this project over. Nobody has volunteered lately.
Thanks for you reply @computerjazz I hope you can find the best champion available.
Would it be "OK" for you if we would help a bit in this process?
I thing one way to get some attention would be to add the search request including the current status on the top of the readme.
Selecting the right person to trust might be challenging. Is there a way to, after the champion is selected, to gradually hand over control? So that the risk is limited?
@callaars Thanks for sharing your interest! Might be good to tell a bit more about yourself if @computerjazz agrees 😄
I'm the head of mobile engineering at Sunsama and we have a stake in this library, so continued support for us is paramount.