Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this still being maintained? #114

Open
BrendanBall opened this issue Jul 12, 2022 · 4 comments
Open

Is this still being maintained? #114

BrendanBall opened this issue Jul 12, 2022 · 4 comments

Comments

@BrendanBall
Copy link

Hi @Azolo . I would like to find out if you're still planning on maintaining this library?
I'm very glad that you decided to make this library and open source it.
I think that many people have gotten lots of use from it, based on the number of forks and downloads on hex.
Certainly I have enjoyed working with it as a native Elixir library.
However there are still a few issues that prevent me from considering it to be truly "production ready".
The biggest one for me currently is explained in this PR #112.
Other people have also had things that they wanted fixed and have started maintaining a fork at https://github.com/XiaoTeTech/gunpowder (although it hasn't been published to hex).

I think it's a big ask for one person to maintain such a library, especially if you're no longer using it, or just busy with other things, personally or professionally. If I were to make a hard fork of WebSockex, the same thing would most likely happen for me.
IMO unless you really want to keep complete control of your library, it's better to get multiple maintainers involved.

So I propose 2 options:

  1. Make a WebSockex organisation and get multiple maintainers involved (I could also do this if you want to give access to publish to hex).

  2. I make a hard fork and create an organisation with the new name and get multiple maintainers involved so that it doesn't end up unmaintained the same way

Let me know what you think.

@Azolo
Copy link
Owner

Azolo commented Jul 19, 2022

Thanks for understanding! These last three months have been particularly hellish for me.

I do what I can when I can, and I understand that people use this library a lot more than I do.

I would be happy to make an organization and such, but I would want to get some repository contribution and management rules in place before I do.

I think whoever wants to submit some contribution and management guidelines first then we can discuss them with any parties that want to be involved.

@BrendanBall
Copy link
Author

Sorry to hear that :( , hopefully it's getting better now :) .

Great.
I haven't set something like this up before, but I'll do some research and put something together.
I'm sure there's some good examples in other libraries like phoenix etc.

@bradleyd
Copy link

@Azolo per your request above #117
It is a start, not everything flushed out.

@mustela
Copy link

mustela commented Feb 13, 2024

@Azolo, I'm wondering if you are still interested in maintaining this library. I think there are a lot of people using it, and it would be awesome to move some existing PRs (Pull Requests) and contributions forward. If you can't or don't want to maintain it (totally fine, life is hard), would you be open to enabling other contributors to help with it?

I've seen several comments like this one where people are trying to contribute.

On this topic, related to another PR that was opened, I would be very happy to work more actively on this repo and I imagine I am not alone in this case, to keep up the pace if @Azolo is understandably busy with other things. But of course we'd need your greenlight for that, and closure on the contribution guidelines PR. I am using Websocket and Elixir quite often these days so I'd really like that repo to be well maintained, along with the help of the community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants