This repository was archived by the owner on Apr 18, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 18, 2026. It is now read-only.
Call for Maintainers #752
Description
I'm looking for new maintainers of Selectize. In the coming weeks/days, I'll be moving it to an organization account so other people can take care of it. The reasons behind the move (+ some other thoughts):
- Selectize has been a personal project of mine – it's received no sponsorship and has been a "free time" project. I've been spread thin and it's been increasingly difficult to maintain as my available time has dwindled. I've been heads-down working Natural Atlas.
- jQuery plugins for UI components have always been a hack. I'm really stoked by what React is doing in this space. I highly recommend checking out @JedWatson's react-select project (even cooler given the fact Jed has contributed to Selectize in the past).
- Lastly: open-source burnout. I work on other OSS projects and jQuery plugins seem to be the most pain afflicting. The burnout stems from a few factors:
- Everyone has a different idea of how it should work. Different opinions and hard choices are great – but when the stream of people coming into Issues wanting you to drop everything else to make it their way is incessant, it gets old.
- Entitlement around new features, changes, and support. See bullet 1.
- Not enough ingenuity from users (i.e. the Stack Overflow effect). If a style is slightly off, change it for the project. If something minor is broken, fix it and make a pull request that makes obvious what the problem is, how it's solved, and ideally some tests to make sure it doesn't regress. This is an open source project, not a company's product.
- Front-end UI has a culture around un-tested code – after all, it's hard. Regardless, pull requests with tests are extremely rare, and most pull requests come in half-baked. By "half-baked" I mean they come with unintended consequences.
- The readme is ignored: updating the dist files in a PR has never been the right thing to do.
- Too many middle-of-the-night support requests.
What I'm mainly looking for in maintainer(s):
- Attention to detail. With the myriad of browser inconsistencies when it comes to focus handling combined with wide array of use patterns, it's easy to naively introduce new issues.
Where selectize needs some love:
- Bugfixes
- Finishing locking down the API.
- The "single" select mode that mimics a normal
<select>could use some UX improvement. react-select is a great example of how it can be improved.
That said, thanks to everyone who's brought selectize to where it is now. There's lots I've learned and certainly much I could have done better. I still want selectize to succeed and will try to work on it from time to time, but it'll be less than I currently do. If you're interested in maintaining, please email me: brian@thirdroute.com Thanks!
Activity
JedWatson commentedon Mar 28, 2015
@brianreavis I'm honoured. Thanks for all the work you've done on Selectize, you've created (imo) the best of the jQuery select controls and it was a huge inspiration for my work on react-select, especially with regards to the user interaction design.
I think many people (myself included, previously) underestimate how much work it is to get the design of a component like this right, and you nailed it.
Good luck finding maintainers, hopefully some great people will step up and help from here!
airwin commentedon Mar 31, 2015
Selectize.js is a great plugin, it helps me a lot, hope to have a good continuation! btw: I have turn to write react too and may also use @JedWatson 's react-select >.< . Thanks to all the open source contributors~!
tannerlinsley commentedon Apr 7, 2015
I would love to contribute. I'm run the entire front-end for Nozzle.io, and we exclusively use selectize.js for all of our needs (+ angular).
gregblass commentedon Apr 10, 2015
Just wanted to say thanks Brian. Using it for a responsive website and its working great! Chosen wouldn't work on mobile at all, and didn't have some of the other features I needed baked in like adding choices (I ended up hacking chosen to do that, but it was nice to just have it available). Yesterday I spent a LONG time looking through this code base and thinking about how I could just move the selected items outside of the box. It took me way longer than it should have to come up with a solution (so far down a few rabbit holes, when they were just the wrong ones). Anyway I really got a sense for this code base, and damn - there is a lot going on! I agree with you...I think in a general sense that this is kind of ridiculous, and can see how jQuery may not quite be the best way to go about things. And I also read through every issue trying to find an insight on mine. Man, people get SO entitled! Good luck with your project. Cheers.
gregblass commentedon Apr 10, 2015
Here's the responsive web app I finished up last night for a client using selectize magic! You can see I styled it a ton, and got the selected items to show up below - and working on mobile. Posting this to hopefully give you some sense of happiness to see your code being used. I wish I had the chops to contribute to the project. Thanks again!
barretts commentedon Apr 14, 2015
Thanks for all your work @brianreavis I've enjoyed using it these past few months. I'd love to contribute but I think you're right that the future is elsewhere. I've run into those focus issues in my own cross browser testing, nothing is ever simple is it? Though since I wasn't even able to get my own tests passing on Travis and haven't had the time to dig any deeper I don't think I could take the reins alone like you've been doing for so long. Anyhow best of luck on your future work, thanks again!
mikemaccana commentedon Apr 23, 2015
@brianreavis another way the burden could be reduced is by dropping support for older browsers completely. Google are IE10+ right now.
owais commentedon Apr 28, 2015
@brianreavis selectize is one of the most flexible and well designed frontend libs I've come across. You'd be surprised to see how I've used it in my projects. It never stops to be useful even for things it was not supposed to power. Thank you so much!
thstarshine commentedon Aug 28, 2015
So what's the status of this project now please?
Is there anyone gonna taking care of this?
Selectize is a really nice plugin.
tannerlinsley commentedon Aug 28, 2015
I'm thinking of putting together a rewrite of selectize. Removing the jQuery dependency, and cleaning up some of the code. Hopefully going to be more lightweight and have more opportunity for extensions. Another goal would be to separate the skinning and layout, and hopefully allow for some great framework extensions as well for angular, react, etc. Thoughts?
nathanboktae commentedon Aug 28, 2015
I'd love to help with a version that removes the jQuery dependency. Now with evergreen browsers working directly with the DOM is just fine. Then having a library of thin wrappers around popular MVC frameworks would be great and help it's long term success.
tomwjerry commentedon Oct 7, 2015
Any news about this rewrite stuff? Have you begun make a project yet? Selectize is like life and death for my project. If none are gonna make it, I will. I am not a coding expert and I know little about coding without jQuery. What I would to have is selection of multiple entries and creation of new entries on the fly.
Hope that the new selectize project can get started soon!
u01jmg3 commentedon Nov 3, 2015
I would be happy to help with maintaining this library to the high standard you have already put in place. I've used it extensively for a current project and have several bug fixes ready and tested but will wait to PR until the queue goes down -- hopefully I can help with that.
tomwjerry commentedon Nov 10, 2015
I still think we should need to make an library independent selectize thing. I do not think he will accept any fixes.
44 remaining items
scarroll32 commentedon Aug 31, 2020
Wow @oyejorge you have a serious amount of work in your fork. I think removing jQuery is a great idea, your fork should be accepted back here as a major version bump.
joallard commentedon Sep 2, 2020
Hey folks, thanks for your interest here. I thought I had asked in my previous post, but alas I did not: people interested in maintenance, would you send me an email at
atob("am9uYXRoYW4uYWxsYXJkQGhleS5jb20=")? I'm hoping we'll be able to talk it out from there. — cc @databyte @oyejorge and others interestedAlas, folks waiting for PRs will have to wait on this blocker to be resolved. Thanks for holding on tight, I'm sure it feels pretty ungrateful not to respond to PRs, but I'm hoping we'll be able to reuse your work soon enough when we're able to.
Pictor13 commentedon Nov 11, 2020
Ehm... any news?
Was there any meeting or decision with the mentioned volunteers?
I see there is @risadams that made several commits on the master branch and added himself for the lib's Copyright starting from 2020, so I assume somebody gave him write permissions or handed the repo to him, even though he never wrote in this thread to propose himself.
Who gave the permissions, @brianreavis or @joallard?
Was there some relevant decision that was not reported here yet?
It's good though, to see some refreshing work being done on Selectize. 👍
databyte commentedon Nov 11, 2020
Speaking of which, I was just talking to @risadams and @joallard over keybase about maintainers. Join the conversation - there's a general chat room on the open team
#selectize.We can move our conversation to the public channel there.
It's suggested we should get roughly 4-5 contributors then refresh the Project list, cleanup open Issues and work through the PRs. @joallard did some work already on getting CI cleaned up, merged a couple simple PRs and then added bootstrap 4 support. Lots more to get done.
We only just started chatting today so it's still early.
via app: keybase://team-page/selectize
via web: https://keybase.io/team/selectize
joallard commentedon Nov 11, 2020
@Pictor13 Confirming, I did. @risadams and @databyte responded to my previous comment, and I really didn't have the time to dedicate to this, so I took a bit of time to set up a maintenance team. I'm hoping this is some fresh new energy into this project!
Pictor13 commentedon Nov 11, 2020
Glad to hear that!
And sorry guys if I rushed things 😅
I'll follow and try to contribute as well when I can.
Thanks everybody for your past, present and future work 🙂
risadams commentedon Nov 11, 2020
@Pictor13 thanks for jumping in so quickly!
github-actions commentedon Jan 7, 2021
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
anandphulwani commentedon Jan 18, 2021
@joallard I would like to put my name in the list.