-
Notifications
You must be signed in to change notification settings - Fork 137
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
Do you need maintainers? #366
Comments
@gjtorikian @tyler-wel Oof yeah, sorry I didn't see this before — I stepped away from this one quite a number of years ago and @ota42y de facto took over. @ota42y Do you have any thoughts on finding alternative maintainers? |
Sorry, I hadn't checked for a while and hadn't noticed (a kind friend told me about this Issue). However, there is a problem with the maintainer. I have not used Ruby recently and would like a maintainer who is actively using Ruby. |
I don't know how to prove it, but I still actively write and release Ruby gems, like:
I will say, though, that since I opened this issues, I found https://github.com/ahx/openapi_first, which also has a nice comparison of supported features: https://gist.github.com/ahx/1538c31f0652f459861713b5259e366a So while I can still volunteer to modernize/admin this gem I myself am no longer using it. 🤷♂️ I think probably much of this gem depends on https://github.com/ota42y/openapi_parser, which also has some open PRs associated with it. |
@gjtorikian
Yes, we have implemented the OpenAPI implementation as a separate gem for OpenAPI 3 support. Therefore, the committee itself is focused on exchanging requests and responses with rack. |
Ok, than I humbly accept! 😄 |
@brandur Can you give @gjtorikian write access to this repository? Any ideas on how to work with us? Currently I am going to release v5.0.0 in its current master code state, but I have no idea what features I will add next version. |
@ota42y @gjtorikian Added! |
I'm going to close this as it looks like everything was resolved at the time. |
There are a few open issues and PRs that solve issues; I'm volunteering to help merge/manage those. Ideally I would like to get this project updated to 5.x, and release support for OpenAPI 3.1.
Edit: @brandur @ota42y (pinging top contributors, sorry; I'm not sure who admins the repo) #349 is a good example of a PR where the work is done, but needs merging. I can always pin to a ref and move on with my day, but I would rather help get these released. ✌️
The text was updated successfully, but these errors were encountered: