-
Notifications
You must be signed in to change notification settings - Fork 25
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
Are you open to transferring ownership of this project? #37
Comments
I don't mind, but I'm also not at this org anymore so I can't give permissions. @koos42 do you know of anyone that can help out here? |
@bionicpill do you know of anyone that can chime in on the ask by @axelson ? |
Ping! FYI assuming that you all are open to it I've started a discussion about moving the maintenance of this library under the beam-community umbrella. See: https://github.com/orgs/beam-community/discussions/23 Although of course it could be done as a fork, but that's not my first preference. |
Unfortunately, the original maintainers of this library are no longer in the seomoz org and don't have permissions to change ownership of the repo. @younker might be able to help? |
Hi there! 👋
This library hasn't seen active maintenance in a while and I'm guessing that you're no longer actively using this project.
I have a semi-active fork of this that I just did some basic maintenance on: https://github.com/axelson/publicsuffix-elixir
Are you open to transferring ownership of this git repo and hex package over to me? I'd like to help maintain it (or help maintain with a few other maintainers as well).
I have fond memories of using this library and it would be nice if the library was able to stick around in it's original form rather than a hard fork 😄
The text was updated successfully, but these errors were encountered: