Showing content from https://github.com/selectize/selectize.js/issues/752 below:
Call for Maintainers · Issue #752 · selectize/selectize.js · GitHub
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!
alexweissman, sibinx7, mtangoo, anx-ckreuzberger, kstratis and 16 morebrunocassol, loicboset and eduardo-miorVerenaHeld, preeteshjain, stephanvierkant, maxcorbeau, mayankvadia and 6 more
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4