Are you open to transferring ownership of this project?

[axelson]

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 😄

[weiser]

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?

[weiser]

@bionicpill do you know of anyone that can chime in on the ask by @axelson ?

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

[bkirz]

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?

[reisub]

Thanks for the shout @bkirz!
@younker any chance you can help with this?

[reisub]

It's been a while but I'd still like this to happen and hopefully @axelson as well.
@bkirz @younker can you help us out with this?

[bkirz]

I looked into the hex side of things, and it looks like @myronmarston and I still have permissions to migrate the hex package to a new owner. Neither of us work at Moz anymore and aren't part of the seomoz org, so we don't have permissions to migrate the github repo. Given that the existing license rests with Moz, I'd want to get some form of approval from them to transfer the package and the repo before doing so. We've already tagged a few folks who still work there, but no luck so far. I think next step would be to reach out to the company directly.

[reisub]

@bkirz thanks for taking a look, let's see if we can get in touch with someone at Moz then.

@mutchco could you help us out with this?

[younker]

@funnylookinhat care to weigh in?

[reisub]

I've tried to be patient with this, but a recent change in how optional dependencies are resolved with hex forced my hand; I've published a fork of this library as public_sufx and plan to maintain it going forward.

The API surface is a bit smaller, and it downloads the fresh list on compile by default.

To the original authors/maintainers: thanks for all the effort you put into this library.

To anyone else needing this functionality: see above link.

Feel free to close this issue.

[axelson]

@reisub another option is to ask the hex.pm team to consider the public_suffix package to be abandoned (which it definitely seems to be). If they agree then they will release the package name and you could adopt the package instead of publishing a new one. A benefit of that is an easier upgrade path for existing users of public_suffix. The instructions to do so are at https://hex.pm/policies/dispute

Of course if you'd prefer to keep using public_sufx that is fine as well!

[reisub]

Thanks for the note @axelson. I've already diverged from the original interface (there's no registrable_domain function, though I might bring it back if people find it useful) so it's not a drop in replacement.

I'll keep the public_sufx name, but you make a good point and I'll keep it in mind for next time!

[axelson]

Yeah, that's totally fair 👍