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

State of Support for this Library (last merged PR was on Feb 22, 2023) #542

Open
angusryer opened this issue Jul 9, 2024 · 4 comments
Open

Comments

@angusryer
Copy link

angusryer commented Jul 9, 2024

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!

@angusryer angusryer changed the title State of Support for this Library State of Support for this Library (last merged PR was on Feb 22, 2023) Jul 12, 2024
@computerjazz
Copy link
Owner

computerjazz commented Jul 23, 2024

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.

@angusryer
Copy link
Author

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!

@callaars
Copy link
Contributor

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 .

@Volper212
Copy link

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.

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