[READ THIS FIRST] 🚨 Maintainer/Collaborator Needed #33
Description
Hi everyone,
When I first wrote Vex, it was to handle limited data validation problems in Phoenix controllers. It was a relatively simple, but fairly flexible package that met my needs, and I released it to help others. Since then it's grown quite a bit, driven largely by really good ideas from the community. Thank you.
For the last year or so @benwilson512 and I been working a lot on Absinthe, which addresses data validation problems in another, more comprehensive way for us. We recognize, though, that people still want more general-purpose validation, and while, eg, Ecto, has validation support for changesets, it may not meet their needs either.
We'd love Vex to continue to grow -- there are a lot of other ideas languishing here in the issue list that we'd love to address, but we simply don't have the time (either to build them or to assess the quality/direction of PRs submitted).
So, a request: If you would like to support Vex's development by becoming a collaborator and putting time into making these ideas reality, we'd love your assistance. We'd also have no problem giving up "ownership" of the package to someone who's committed to maintaining it.
We don't want to abandon Vex, but we don't have the time right now to keep developing it. Can you help?