Project status and future of stomp.js #121
Description
@jmesnil, I'm sure I speak for many in thanking you for this project! I completely respect your reasons for stepping away and as a father I understand your dilemma :) I do hope this project finds a home.
In the mean time I wonder if there isn't some relative hands-off way and a middle ground that would give this project some extra mileage? As you wrote the library is small, quite stable and documented but there will always be issues with browser compatibility. It seems rather feasible for the community to identify fixes in some cases but having a preferred place to contribute such fixes (vs having to fork) would make a big difference.
Could there be some process through which selected fixes from the community could be accepted? For example subjectively single out issues that clearly need fixing, come with reasonably straight-forward changes (pull request), and seem relatively low risk. This could further be coupled with additional specific requirements that such changes be tested and verified (vouched for) by at least 2 community members before they could be even considered. It gives the community a chance to step up.