-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add more maintainers #1315
Comments
Myself and others @ domain are also happy to help where we can - we are heavy users of react select |
I completely agree with the sentiments expressed in this issue, but I think a good way to contribute for now would be to open the other issues and start helping people. |
@JedWatson, thanks very much for creating this excellent tool. I'm using it in multiple places within my app. However it appears to be suffering from lack of attention: for example there are two separate PRs to add an "alwaysOpen" prop to the component, neither of which has been merged. This tool is being used by many people so, please either add more maintainers to this repo or start responding to people's PRs. Thanks, |
Hey guys, I'm starting a fork of react-select, the goal is to eventually take over the project. I'll probably post my updates in #1403. |
@silvenon, that seems like the direction this needs to go, but have you reached out to @JedWatson via email or social media about it? Either way, I'm happy to help if we need contributors to get this project thriving again. |
Good idea. I'll try tweeting him first. |
Consolidating this to #1481 |
Hey guys,
by the number of pull requests and the history of some enhancements that are taking a long time to land (optgroups is one), I suggest adding more maintainers to this repo.
It looks like tons of people are using this package already so it would be nice if all wasn't on a shoulders of one (although great) guy.
Maybe someone from a big company, like Hubspot (which recently made a public fork so people can have optgroups) could be a maintainer?
The text was updated successfully, but these errors were encountered: