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

Why not submit the work from this project back to the official Select2 project? #15

Open
klonos opened this issue Apr 30, 2018 · 2 comments

Comments

@klonos
Copy link

klonos commented Apr 30, 2018

This is more of a general question rather than an actual ticket. If these changes were accepted upstream, there would not be a need for this repo at all, and all current user base of Select2 would benefit from the improvements it brings?

Are the changes too WP-specific perhaps?

@iandunn
Copy link

iandunn commented May 29, 2018

It looks like this was originally created because the development of Select2 seemed to have stalled, and there wasn't a lot of confidence that a PR would be merged.

Select2 has seen some more activity, though, so it may be a good time to reconsider PRs upstream to merge all these important a11y fixes.

@alexweissman
Copy link

I've been busy with a couple other major projects recently (OSS and otherwise), but once finished I'd be willing to merge some carefully reviewed and tested PRs back into the main project repo.

The main issue is that we need a concerted and sustained effort to fix the various problems with Select2 without breaking something else.

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

3 participants