Consider to allow using forks of chosen

I am a new Chosen-module Maintainer and currently going over the whole Issue list.
Some of the problems are related to the plugin we are implementing, chosen from harvest.

I have postet already some comments over there, or redirected users to post their issues over there, because we are doing just the plugin implementation for Drupal.

Issues like the

• The search string isn't visible on the blue backgrounded items (mouse hover or first item when searching)
• The div has overflow "problems" when used in overlays (when chosen should go over the overlay's border) (#1670658)

The Problem seems to be a bit that a lot of things would be fixed, but the pull request are not getting accepted, and a lot of issues are still open.

Now I have found select2 which is a fork of the chosen module and seems to be more active in bugfixing etc. And I am thinking about to make it possible to load such forks also into the libraries folder and activate them.

I think because they are forks, that would be pretty simply and they should not get an completely own module. This should really just change the plugin we are using.

What do you think? Should this be fine, or should a fork have its completely own module in Drupal?

Here are the details of the fork I have found:

• https://github.com/ivaynberg/select2
• http://ivaynberg.github.com/select2/