React-select: Need help for maintainance?

Created on 1 Dec 2016 · 17Comments · Source: JedWatson/react-select

Hi @JedWatson,

It seems that you do not have the time to maintain this package by yourself, do you need help?
To be honest, I do not have time to invest much time in it myself but I can help in opening the management :)

IMHO, the best approach would be to migrate this repo in a GitHub organization (because it allows other people to add maintainers if you're not available) and to add a bunch of maintainers.

Who can and wants to help?

Source

julien-f

👍29

Most helpful comment

Hey everyone - thanks for all the constructive offers to help, and sorry for the complete lack of response, I ended up taking a much needed complete break over the holidays. (I have about 2k unread GitHub notifications at the moment, just to put things in perspective! It really gets on top of you)

I'm back at work this week so I'll jump in tomorrow & put a plan in place - would love to get some assistance triaging the issues / fixes that are important or good to go then we can figure out how to take better care of maintenance longer term.

@silvenon what timezone are you in? It might be helpful to jump on Skype / hangouts to sync up. I'm in Sydney so UTC+10

Thanks!

JedWatson on 9 Jan 2017

🎉7

All 17 comments

@julien-f awesome alternative to those awful "Is this project abandoned?!" issues. 👍 I want to help, I believe this is the best React select solution.

silvenon on 1 Dec 2016

@julien-f :+1: I'm interested to work on it since I have used it everywhere

BreahnaDavid on 7 Dec 2016

See also https://github.com/JedWatson/react-select/issues/1315. Some issues I see have been fixed and can be closed as well.

turnerniles on 7 Dec 2016

@turnerniles You're right, this issue is a duplicate! :)
But I'm reluctant to close it as it increases the visibility of the problem overall.

julien-f on 7 Dec 2016

@JedWatson you here? :)

julien-f on 14 Dec 2016

I think one of us should fork the repo and start merging in contributions, but I'm not ready to take that on just yet. 😅

silvenon on 14 Dec 2016

Yeah, Looks like @JedWatson is MIA. Has anyone done a fork yet? There are 113 PRs so a fork could have a ton of features/bug fixes immediately. I'm willing to help!

sontek on 22 Dec 2016

I created one just now: silvenon/react-select. I have lots of free time ATM, so I'll do as much work as possible. I'll start by rewriting tests to Jest, so we can start off with a strong test suite.

silvenon on 22 Dec 2016

🎉1

@silvenon Thanks for doing it! You might want to reach out to the people in tickets:

https://github.com/JedWatson/react-select/issues/1432
https://github.com/JedWatson/react-select/issues/1315

Since they were also wondering why it isn't supported anymore.

sontek on 23 Dec 2016

👍2

@silvenon Looks like you haven't made any progress either?

sontek on 1 Jan 2017

@sontek I decided to wait for @JedWatson input first, so I know in which direction we should proceed. https://twitter.com/jedwatson/status/812549810758643712 Thanks for the ping.

silvenon on 1 Jan 2017

👍1

@silvenon How long are you planning to wait before proceeding?

shinzui on 9 Jan 2017

@shinzui no longer 😄 I asked him whether he's willing to transfer ownership, move the repo to an organization or (last resort) I continue with my fork. If I get no response, tomorrow I'll start working on the fork.

silvenon on 9 Jan 2017

@silvenon what timezone are you in? It might be helpful to jump on Skype / hangouts to sync up. I'm in Sydney so UTC+10

Thanks!

JedWatson on 9 Jan 2017

🎉7

@JedWatson I'm in Zagreb, UTC+1. I'm also "silvenon" on Skype, so feel free to add me and propose a time when you're free.

silvenon on 9 Jan 2017