This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Call for Maintainers #752
Comments
|
@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! |
|
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~! |
|
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). |
|
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. |
|
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!
|
|
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! |
|
@brianreavis another way the burden could be reduced is by dropping support for older browsers completely. Google are IE10+ right now. |
|
@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! |
|
So what's the status of this project now please? |
|
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? |
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. |
|
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! |
|
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. |
|
I still think we should need to make an library independent selectize thing. I do not think he will accept any fixes. |
|
So... Project is dead? What are the best alternatives to it? |
|
This repo may not be maintained, but the project itself isn't dead and having recently researched alternatives, I still think this is the best codebase / project like it. |
|
If someone wants to port it over to the github.com/selectize organization, On Mon, Nov 30, 2015 at 9:54 AM Phil Freo notifications@github.com wrote:
|
|
The question is if the project should be rewritten from scratch or if just the code should be changed to remove the jQuery dependency. Should not be too hard to just change the code so that jQuery is not used. |
|
Rewriting from scratch essentially turns this into a new project. Perhaps a similar/compatible API, but it means possibly introducing some breaking bugs or impacting any custom plugins that a project may be using. If there were two forks of this, one rewritten from scratch and one maintaining/fixing bugs in the existing codebase, I know for sure that we'd choose the latter, as we couldn't risk the potential negative impacts of a brand new codebase. I think if it were rewritten from scratch, it'd be best to also rename the project in the process. Whoever does take this on, please ensure that if the jQuery dependency is dropped, custom plugins won't be negatively impacted, or at the very least, any breaking changes are well-documented. Same with the API in general. |
|
I've been thinking about breaking some things down into smaller modules/breaking up the API a bit (for instance to isolate the "fake input" functionality), pondering this over the past year but never making a move. I'd be down to pitch in with maintaining/refactoring/participating/triaging/whatever, with the possibility of removing jQuery for a Major bump. I for one am committed to a clean API and an extensible plugin. Have some people been selected or has there been any progress? I would've liked to make some PRs, but the queue is quite long. |
|
Hey @brianreavis, is there a way to check whether anyone is chosen as a new maintainer? Also I can't really see the github "Network" tab which shows how forks are progressing because there are too many forks. So basically I can't see whether anyone took over. |
|
None took over this so far. Best luck is on github.com/selectize |
|
@tomelssjo @tannerlinsley selectize/selectize doesn't contain any of the Git history, it's just a crude directory copy. If we do it right I'd be happy to pitch in and do some Git-fu with the PRs here, even better if we had @brianreavis' benediction. |
|
For sure. A transfer would be optimal with a rewrite of the contributors.md.
|
|
So @tannerlinsley and I have set up an organization fork at selectize/selectize to organize efforts to put this back on the rails. If you'd like to offer your help, chime in at selectize/selectize#4 or open an issue to talk about it. Or if there are PRs you'd like to resubmit/port over, go ahead. Hope to see you there! |
|
Can I restart the development? I still see a future for this framework. But expect no wonders I have also not so much time and it will be a spare time project. |
|
my name on npm is also devkral |
|
Ok, whoever is up and ready to maintain this repository, to like this comment, comment after with your DISCORD |
|
129 open pull requests ... did anyone finally agree to become a maintainer? |
|
We have not heard back from the Author yet |
|
Ping @joallard @brianreavis |
|
I switched meanwhile to choose.js and added support for select boxes (not merged yet, still some minor issues) |
|
Okay, looks like meanwhile I've gotten admin rights from Brian to be able to nominate maintainers. This is all a bit stale, so if you're up for it, please make your case. The ideal volunteer is someone who uses the library and knows it well, has participated in issues/PRs before, and who can help move this project forward with the input of the community. The job is pretty much to review stuff, help people write good code, and best case, scratch their own itches because they significantly use the project. (last point optional) If there's anything I've learned in open source: it takes a lot of patience, people can be from ungrateful to lovely — sometimes running into an annoying bug for hours can be really tiring too! — and it's real work. Like I said, ideally, this would look like a team of 2-3. I'm able to put a tiny bit of help with really meta things, but I can't give actual work time to this, I'm sorry. That said, if we're able to assemble something together so work is supported/funded, that'd be fantastic. Hopefully this is a new start for this old project ;) — and the people who appreciate it. |
|
Hey @joallard - I think at a minimum we should have a couple people help maintain repo health by managing travis, package.json and security vulnerabilities. Even if I'm not working on feature requests, I'd be great to maintain a healthy repo overall. As a contributor on a couple other packages, it's a lot of work to drum up support so lets use the recent activity around security vulnerabilities for library dependencies to pull in a few folks. If we could define a simple minor version update, then we can focus the next set of PRs and cleanup the Issues list. I recently used selectize on a project because they weren't using a client-side framework (e.g. React, Vue, etc) and it met the needs more so than other drop-down selectors. As an active and recent user, I don't see any reason why we couldn't pull together a small group of folks in Github discussions or Discord to cleanup and release a new version after a good 8-12 hours of work. We may want to call bankruptcy on Issues older than 2 years then triage the rest. I'm game if anyone else wants to sink a couple days into cleaning this up! |
|
I'd like to submit pull requests updating to the latest version of jQuery, with tests and all, but will it even get merged? |
|
To fork or not to fork? This project is awesome and it would be a shame to let it fade away. I personally think development should remove dependence on jQuery and aim for a framework agnostic design. I've completed removing jQuery, made sure tests pass, updated some documentation, etc over here and I'm wondering if I should continue independently or merge into selectize? @joallard @brianreavis |
|
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. |
|
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 Alas, 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. |
|
Ehm... any news? 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? It's good though, to see some refreshing work being done on Selectize. 👍 |
|
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 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 |
|
Glad to hear that! Thanks everybody for your past, present and future work 🙂 |
|
@Pictor13 thanks for jumping in so quickly! |
|
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 |
|
@joallard I would like to put my name in the list. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
and others
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):
What I'm mainly looking for in maintainer(s):
Where selectize needs some love:
<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!
The text was updated successfully, but these errors were encountered: