Replies: 1 comment
-
Hey @axelson this is a great thread and we probably should formalize a document for public consumption. To date the process has been pretty ad-hoc. The biggest concern I have with taking on new projects is going to be maintainers. There's 27 people in the org but I'd say less than 5 are currently active in these repos and I don't want to put more on the plates of a few. If yourself and @reisub are open to helping maintain and the current maintainer is willing to transfer the repo and the Hex package permissions, I'm open to supporting this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi! Is there a process to add a new library to this organization?
I looked at https://github.com/beam-community and https://beam-community.org/ but I didn't see anything.
I'd like to recommend moving public_suffix under this umbrella. The library hasn't seen an update since 2018 and it only needs a small amount of maintenance. I started a discussion about transferring ownership at: seomoz/publicsuffix-elixir#37
If the library is moved under beam-community I'd be interested in helping maintain it, and @reisub has expressed interest as well: axelson/publicsuffix-elixir#2
What do you all think?
Beta Was this translation helpful? Give feedback.
All reactions