-
Notifications
You must be signed in to change notification settings - Fork 198
Call for maintainers! #48
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
Comments
Hi @mbuhot, me and @ThomasRueckert are willing to maintain this project. We would like to move the repo to our team @unifysell. |
I'm down to help with this project. I plan on fixing #47 sometime this month too. |
Thanks @cstaud, @ThomasRueckert @fenollp and @tapickell. I was originally thinking to create a new github org for the project, and invite a couple of admins who can then add additional members with commit access. Would that work for you? |
Sure. |
Yes, of course. :) |
I've moved the repo to a new org. |
We at github.com/GhostGroup (Weedmaps) are still very much interested in being maintainers or co-maintainers of this repo. We have 15 Elixir developers building JSON-API-complaint APIs, and we are just starting to ramp up adoption of open_api_spex. We have plans to make improvements to the casting and validation part of the package (you've seen the first two PRs so far). These improvements are very important to us, so any leverage you can provide in supporting their integration would be helpful. |
@moxley Great to hear, and thanks for the recent contributions. |
Ah so I'm the one with publishing rights. Anyone has a premade script that can publish to Hex on new tags? |
Haven’t tried it but looks like it would work: https://elixirforum.com/t/deployment-an-elixir-project-with-using-travisci/4875 |
I'm no longer using swagger in my day job, so I haven't had the need to make many improvements to this package.
If there are any users who are relying on open_api_spex in commercial / production settings that are willing to share in the maintenance of the project, please respond in the comments, or email me ([email protected]).
I'm happy to move this repo to a Github org and share ownership of the Hex package.
cc: @ThomasRueckert @fenollp @slavo2
The text was updated successfully, but these errors were encountered: