You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Reacted by James Mills, Dmitri Shuralyov, zhoupeng, Petr, Nicolás, Ciaran Liedeman, chukui, Nathan Bass, Khanh Tran, Aymeric Beaumet and 58 more
Reacted by Dmitri Shuralyov, Equim, Petr, hbc, Nathan Youngman, Alexander Emelin, Nicolás, oli, Nathan Bass, Wilk and 53 more
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.
Reacted by Guo Xi, Jimmie Han, Raphael Randschau, James Mills, Chris, 文杰, antsBean, CyRto, Денис, OldCat and 19 more
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.
Reacted by QChen, sincof and Sarthak Bansal
Reacted by Phaneendra Chiruvella, Pierre Fenoll, Adam Quinn Snow, Nicolás, Ron, Warren, Alexey Palazhchenko, Mohamed Yousif, Florian Vogt, Paul Bernier and 73 more
Reacted by zhoupeng, Eliaz Bobadilla, yoxih and Rohit
Reacted by Matt Silverlock, Tom Thorogood, Matthew Radcliffe, Sami Koskimäki, César Hernández Monsrreal, Patrick Scheid and John C. Merfeld
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.
Reacted by Michael, Tom Thorogood, James Mills, Dmitri Shuralyov, Max Muth, Adam Quinn Snow, Matthew Radcliffe, Kien Pham, Dan Larsen, ssskip and 157 more
@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
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>
.
@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>
.
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
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.
Reacted by George, hbc, Kohei Misu, Tariq, gaborigloi and G2G2G2G
Reacted by Wilk, BennettJames, Nathan Youngman, Tariq, gaborigloi and G2G2G2G
@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.
No, we have not. The folks helping triage have not been interested in
taking over in full (nor do they owe us that).
PRs still get merged and this remains a mature library, so the need for
large scale changes is small.
@garyburd while I don't necessarily want to throw my hat in the ring for the role of maintainer of this project, we rely on it for both open source and commercial projects in the organization I work for. (https://github.com/sensu/sensu-go) As such I have a vested interest in seeing the project live on, and so does the company I work for.
I'd be interested in assisting with critical bug fixes, security issues, reviewing pull requests, and possibly funding (I have no direct control over funding, but could advocate for it if it would help the project stay alive).
I'm not interested in implementing new features, as I feel the feature set of websockets is good enough. I'm also not interested in triaging issues or trimming the issue backlog (and that's why I don't want to step up to be a maintainer, if that's an expected maintainer function). I also feel like the websocket library is in a pretty good place as things stand, so I wouldn't be surprised if my help isn't needed.
But if something needs doing to keep the lights on, you have my support. Feel free to reach out, or have Kamil feed me some tasks (I work with him in maintaining another legacy project already).
Cheers ✌️
Reacted by Adam Quinn Snow, Petar Petrov, John, Artur Carvalho, Kazuki Higashiguchi, Rohit Kalkur, Anh Tran Nhat, Irfan Ismail, lyp256, Dean Davidson and 7 more
@elithrar thanks for the link. It looks like there are new maintainers for the Gorilla projects. I'm very happy to see this! Wishing you all capable developers a happy continuation and collaboration.
Activity
HillbillyHero commentedon Apr 13, 2018
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 commentedon Apr 24, 2018
I'm also working on networking/sockets in Golang. Happy to help maintain/contribute ⚡️
binary132 commentedon Apr 30, 2018
Since people are constantly hammering on
x/net/websocketas "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 commentedon Apr 30, 2018
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 commentedon Apr 30, 2018
@garyburd have you considered the idea of merging into the official exp. stdlib? Thus probably replacing the current websocket implementation?
glerchundi commentedon Apr 30, 2018
Nevermjnd, i didnt read the previous comments. Still @garyburd opinion on this regard will be much appreciated!
prologic commentedon May 1, 2018
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 commentedon May 1, 2018
@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 commentedon May 1, 2018
elithrar commentedon May 1, 2018
prologic commentedon May 1, 2018
prologic commentedon May 2, 2018
So far so good (y) prologic/msgbus@4b954ba
niaow commentedon Jul 31, 2018
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 commentedon Aug 6, 2018
@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 togorilla/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.
24 remaining items
elithrar commentedon Feb 8, 2021
[-]New maintainers needed[/-][+]⚠️ New maintainers needed[/+]echlebek commentedon Dec 18, 2021
@garyburd while I don't necessarily want to throw my hat in the ring for the role of maintainer of this project, we rely on it for both open source and commercial projects in the organization I work for. (https://github.com/sensu/sensu-go) As such I have a vested interest in seeing the project live on, and so does the company I work for.
I'd be interested in assisting with critical bug fixes, security issues, reviewing pull requests, and possibly funding (I have no direct control over funding, but could advocate for it if it would help the project stay alive).
I'm not interested in implementing new features, as I feel the feature set of websockets is good enough. I'm also not interested in triaging issues or trimming the issue backlog (and that's why I don't want to step up to be a maintainer, if that's an expected maintainer function). I also feel like the websocket library is in a pretty good place as things stand, so I wouldn't be surprised if my help isn't needed.
But if something needs doing to keep the lights on, you have my support. Feel free to reach out, or have Kamil feed me some tasks (I work with him in maintaining another legacy project already).
Cheers ✌️
tomaswarynyca commentedon May 24, 2022
Any news? 🙁
XFrankly commentedon Oct 23, 2022
its a maintenance-only repo, no new development targets, i understand.
mrrobotisreal commentedon Oct 31, 2022
Hello, I am also willing to help maintain this.
grokify commentedon Nov 14, 2022
Seems like major versions can be considered given the following the following regarding "version 2.0s":
gorilla/mux#659
elithrar commentedon Dec 9, 2022
The Gorilla project has been archived, and is no longer under active maintainenance. You can read more here: https://github.com/gorilla#gorilla-toolkit
zrml commentedon Jul 27, 2023
@elithrar thanks for the link. It looks like there are new maintainers for the Gorilla projects. I'm very happy to see this! Wishing you all capable developers a happy continuation and collaboration.
bilinxing commentedon Aug 11, 2023
Has the Gorilla project found a new maintainer? 🎉This is exciting news, is there an announcement anywhere about the future direction of the project?