gorilla/websocket - Looking for a New Maintainer

[Matt Silverlock]

I think I've posted about this before (or Gary has!), but we're looking for a new maintainer to take over the gorilla/websocket project. We've tried for a while (over a year) to find a new maintainer and haven't had any real bites.

Some context:

• It's heavily used - 9k+ stars, 4600+ importers, and used in some fairly large projects - and so a maintainer with previous experience in this space would be appreciated
• We care a lot about backwards API compatibility, and this should be a guiding principle of any new maintainer(s)
• You'll have help: there are a couple of us maintaining other Gorilla packages, handling CI, etc - and there have been a couple of regular commenters/reviewers on the websocket package.
• Ideally, we'd give you some limited rights to the repo for issue triage for a while + merge on your behalf, before handing you the keys to the kingdom (so to speak).

If you're interested, please reach out on the issue - https://github.com/gorilla/websocket/issues/370 🦍