⚠️ New maintainers needed

I am stepping down as the maintainer of the gorilla/WebSocket project.

I am looking for a new maintainer for the project. The new maintainer should have a track record of successfully maintaining an open-source project and implementing RFCs.

Potential maintainers can gain the required experience by contributing to this project. I need help triaging issues, reviewing PRs, and fixing issues labeled "help wanted." If you are interested, jump in and start contributing.

If you rely on the quality and ongoing maintenance of this package, please get involved by helping to maintain this package or finding people to help maintain the project.

[HillbillyHero]

Hey guys,

I am very interested in helping maintain gorilla/websocket. I currently deal with a lot of networking in Golang and believe I could be of service to the project and team.

[nynhex]

I'm also working on networking/sockets in Golang. Happy to help maintain/contribute ⚡️

[binary132]

Since people are constantly hammering on x/net/websocket as "unmaintained" and "everyone uses gorilla/websocket", please consider putting in more than a month's worth of half-baked effort to make sure you have found a suitable maintainer for this, since many production systems rely on its quality.

[elithrar]

There’s no need for combative language here @binary132. This is an OSS project, primarily maintained by an individual.

If (commercial) production systems rely on this package, having those engineers dedicate time to contributing back or helping with triage would be a far more reasonable request vs. suggesting Gary put in more than a “half baked” effort here.

Finding maintainers & contributors is really hard. Most requests fall on deaf ears. I don’t blame Gary for putting a clear timeline around this.

[glerchundi]

@garyburd have you considered the idea of merging into the official exp. stdlib? Thus probably replacing the current websocket implementation?

[glerchundi]

Nevermjnd, i didnt read the previous comments. Still @garyburd opinion on this regard will be much appreciated!

[prologic]

What's the status of this project? I'm looking to switch to gorilla/websocket for the control message pin/pong support in my project.

[HillbillyHero]

@prologic I'm thinking best course of action is to just contribute. If we need to make any updates/changes fork gorilla/websocket, do whatever is needed, then make a PR. The more people we have helping out the better :D

[prologic]

This all works fine as long as there's enough folks that have "Contributor" access to the repo? i.e: Can approve/merge PRs etc? Can I be added to the repo? In lieu of an "official" maintainer; just expanding the list of who can "maintain" the repo is "good enough" IHMO. James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

…

On Tue, May 1, 2018 at 9:45 AM, Gary Burd ***@***.***> wrote: I stepped down as regular maintainer of this project. I will fix critical bugs during the search for a new maintainer. If you rely on the quality and ongoing maintenance of this package, then please get involved by volunteering to maintain the package or by helping to find a maintainer. If you support any of the people who volunteered to maintain the project, then comment here or send email to the address on my GitHub profile. @MiikeWilliams <https://github.com/MiikeWilliams> and @nynhex <https://github.com/nynhex>: Thank you for volunteering to help maintain the project. As noted in the issue, I want to see some consensus on the new maintainer. That has not happened yet. @elithrar <https://github.com/elithrar> Thank you for your help with this project and your comment above. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#370 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABOv-kRN5QKBJaRMcJl7bJdtfLVieCrlks5tuJE4gaJpZM4TC8KQ> .

[elithrar]

@garyburd, @kisielk and myself can merge any critical bugs/patches (as Gary addressed, above), and myself & @kisielk can triage in the meantime. We're both pretty strapped for time (+ maintain the other Gorilla repos), so it'll likely be "critical bugs" only. I don't know where Gary stands on this, but if you start contributing fixes, documentation & triaging issues for some period to establish capability & trust, it will help us understand when to dole out write privileges to the repo.

…

On Tue, May 1, 2018 at 9:54 AM James Mills ***@***.***> wrote: This all works fine as long as there's enough folks that have "Contributor" access to the repo? i.e: Can approve/merge PRs etc? Can I be added to the repo? In lieu of an "official" maintainer; just expanding the list of who can "maintain" the repo is "good enough" IHMO. James Mills / prologic E: ***@***.*** W: prologic.shortcircuit.net.au On Tue, May 1, 2018 at 9:45 AM, Gary Burd ***@***.***> wrote: > I stepped down as regular maintainer of this project. I will fix critical > bugs during the search for a new maintainer. > > If you rely on the quality and ongoing maintenance of this package, then > please get involved by volunteering to maintain the package or by helping > to find a maintainer. If you support any of the people who volunteered to > maintain the project, then comment here or send email to the address on my > GitHub profile. > > @MiikeWilliams <https://github.com/MiikeWilliams> and @nynhex > <https://github.com/nynhex>: Thank you for volunteering to help maintain > the project. As noted in the issue, I want to see some consensus on the new > maintainer. That has not happened yet. > > @elithrar <https://github.com/elithrar> Thank you for your help with this > project and your comment above. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#370 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/ABOv-kRN5QKBJaRMcJl7bJdtfLVieCrlks5tuJE4gaJpZM4TC8KQ > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#370 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABIcOzOwnYM1mqFslZVlGWOmdU7-_F-ks5tuJNNgaJpZM4TC8KQ> .

[prologic]

Sounds reasonable On Tue, May 1, 2018 at 10:02 Matt Silverlock <notifications@github.com> wrote:

@garyburd, @kisielk and myself can merge any critical bugs/patches (as Gary addressed, above), and myself & @kisielk can triage in the meantime. We're both pretty strapped for time (+ maintain the other Gorilla repos), so it'll likely be "critical bugs" only. I don't know where Gary stands on this, but if you start contributing fixes, documentation & triaging issues for some period to establish capability & trust, it will help us understand when to dole out write privileges to the repo. On Tue, May 1, 2018 at 9:54 AM James Mills ***@***.***> wrote: > This all works fine as long as there's enough folks that have "Contributor" > access to the repo? i.e: Can approve/merge PRs etc? > > Can I be added to the repo? > > In lieu of an "official" maintainer; just expanding the list of who can > "maintain" the repo is "good enough" IHMO. > > > James Mills / prologic > > E: ***@***.*** > W: prologic.shortcircuit.net.au > > On Tue, May 1, 2018 at 9:45 AM, Gary Burd ***@***.***> > wrote: > > > I stepped down as regular maintainer of this project. I will fix critical > > bugs during the search for a new maintainer. > > > > If you rely on the quality and ongoing maintenance of this package, then > > please get involved by volunteering to maintain the package or by helping > > to find a maintainer. If you support any of the people who volunteered to > > maintain the project, then comment here or send email to the address on > my > > GitHub profile. > > > > @MiikeWilliams <https://github.com/MiikeWilliams> and @nynhex > > <https://github.com/nynhex>: Thank you for volunteering to help maintain > > the project. As noted in the issue, I want to see some consensus on the > new > > maintainer. That has not happened yet. > > > > @elithrar <https://github.com/elithrar> Thank you for your help with > this > > project and your comment above. > > > > — > > You are receiving this because you were mentioned. > > Reply to this email directly, view it on GitHub > > < #370 (comment) > >, > > or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/ABOv-kRN5QKBJaRMcJl7bJdtfLVieCrlks5tuJE4gaJpZM4TC8KQ > > > > . > > > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#370 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AABIcOzOwnYM1mqFslZVlGWOmdU7-_F-ks5tuJNNgaJpZM4TC8KQ > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#370 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABOv-kFg85-WN3J-sixaRdZB1Vehif5Kks5tuJUWgaJpZM4TC8KQ> .

-- James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

[prologic]

So far so good (y) prologic/msgbus@4b954ba

[niaow]

The Gofrs organization would like to help maintain this project. We have filed a help request issue to discuss ways to possibly maintain this. You can also contact us on the Gophers Slack in the #gofrs channel.

[theckman]

@garyburd @elithrar @kisielk I think we in the Gofrs would like to help look after gorilla/websocket. Right now our GitHub org is at about 20 people, and I assume most of them likely won't contribute to every project we work on. So I'm only expecting a handful to want to contribute to gorilla/websocket, but it could be more.

How would y'all like to start down the path of having us look after this repo? My initial thought was to become an administrator on the organization, and to then manage an org team for The Gofrs based on who wants to contribute to the repo. This would allow us to manage membership without needing to take more of your time away from the other projects.