Skip to content

⚠️ New maintainers needed #370

Closed

Description

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.

Activity

  1. HillbillyHero commented on Apr 13, 2018

    @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.

  2. nynhex commented on Apr 24, 2018

    @nynhex

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

  3. binary132 commented on Apr 30, 2018

    @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.

  4. elithrar commented on Apr 30, 2018

    @elithrar
    Contributor

    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.

  5. glerchundi commented on Apr 30, 2018

    @glerchundi

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

  6. glerchundi commented on Apr 30, 2018

    @glerchundi

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

  7. prologic commented on May 1, 2018

    @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.

  8. HillbillyHero commented on May 1, 2018

    @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

  9. prologic commented on May 1, 2018

    @prologic
  10. elithrar commented on May 1, 2018

    @elithrar
    Contributor
  11. prologic commented on May 1, 2018

    @prologic
  12. prologic commented on May 2, 2018

    @prologic

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

  13. niaow commented on Jul 31, 2018

    @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.

  14. theckman commented on Aug 6, 2018

    @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.

  15. 24 remaining items

  16. elithrar commented on Feb 8, 2021

    @elithrar
    Contributor
  17. ghost changed the title [-]New maintainers needed[/-] [+]⚠️ New maintainers needed[/+] on Dec 13, 2021
  18. echlebek commented on Dec 18, 2021

    @echlebek

    @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 ✌️

  19. ghost deleted a comment from on Jan 8, 2022
  20. tomaswarynyca commented on May 24, 2022

    @tomaswarynyca

    Any news? 🙁

  21. deleted a comment from amustaque97 on Jun 26, 2022
  22. XFrankly commented on Oct 23, 2022

    @XFrankly

    任何新闻?🙁

    its a maintenance-only repo, no new development targets, i understand.

  23. mrrobotisreal commented on Oct 31, 2022

    @mrrobotisreal

    Hello, I am also willing to help maintain this.

  24. grokify commented on Nov 14, 2022

    @grokify

    @XFrankly wrote:
    its a maintenance-only repo, no new development targets, i understand.

    Seems like major versions can be considered given the following the following regarding "version 2.0s":

    gorilla/mux#659

    The major libraries — mux (https://github.com/gorilla/mux), schema (https://github.com/gorilla/schema), handlers (https://github.com/gorilla/handlers), and sessions (https://github.com/gorilla/sessions) — are all reasonably mature libraries, but ongoing stewardship around bug triage, feature enhancements, and potential "version 2.0s" are all possibilities.

  25. elithrar commented on Dec 9, 2022

    @elithrar
    Contributor

    The Gorilla project has been archived, and is no longer under active maintainenance. You can read more here: https://github.com/gorilla#gorilla-toolkit

  26. unpinned this issue on Jul 10, 2023
  27. zrml commented on Jul 27, 2023

    @zrml

    @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.

  28. bilinxing commented on Aug 11, 2023

    @bilinxing

    Has the Gorilla project found a new maintainer? 🎉This is exciting news, is there an announcement anywhere about the future direction of the project?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    ⌂ 换网址