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

Add more maintainers #1315

Closed
hakunin opened this issue Oct 18, 2016 · 7 comments
Closed

Add more maintainers #1315

hakunin opened this issue Oct 18, 2016 · 7 comments

Comments

@hakunin
Copy link

hakunin commented Oct 18, 2016

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?

@jooj123
Copy link
Contributor

jooj123 commented Oct 19, 2016

Myself and others @ domain are also happy to help where we can - we are heavy users of react select

@MarkLeMerise
Copy link

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.

@tnrich
Copy link
Contributor

tnrich commented Nov 30, 2016

@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.
#1015
#817

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,
Thomas

@silvenon
Copy link

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.

@MarkLeMerise
Copy link

MarkLeMerise commented Dec 23, 2016

@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.

@silvenon
Copy link

Good idea. I'll try tweeting him first.

@JedWatson
Copy link
Owner

Consolidating this to #1481

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

6 participants