What is the future of pywagger ?

[manatlan]

Hi,

pyswagger is really robust, I've tested a lot of things like that, but pyswagger seems to be the better option for me. And I'd like to use it to my own needs. But I'm afraid that it's not the better solution, because it seems that it's not "alive", any more.

For my needs, I needed to patch some things, to be usable in my cases (ex: expose own proprietary variables from ours swaggers (private ones, doesn't seems to be readable currently) )... Should I make PR to this repo (will it be merged, and updated on pypi ?) ? or should I fork it, and maintains mine ?

Thanks in advance for any suggestions ...

[mission-liao]

Hi, manatlan,

I didn't use this repo anymore for years, and sadly its community doesn't grow large enough to survive without me. I think you have multiple options to push things forward:

• fork it and maintain by yourself.
• join this org as maintainer of this repo. But as I said, the community part is relatively small, so there is no difference from forking.

My suggestion is to fork this repo by yourself.

[manatlan]

Thanks a lot ...

[jsenecal]

Hi @mission-liao , @manatlan .

I strongly believe that this project has the potential to kick off due to many platforms (namely django-rest-framework and FastAPI) now using OpenAPI (fka Swagger) spec should it be maintained. I, myself have run into many issues trying to use this as is and would be willing to contribute back should my changes be merged and the project release new versions.

I see that @manatlan has a lot of changes in his fork, and I wouldn't mind using it as a "start" but I believe that no-one should have to dig through a project network of forks to find one that works properly and is maintained.

All that to say that if you are willing to accept new maintainers of this project, I could volunteer as potential maintainer😃

[manatlan]

Hi,

No, my version doesn't have many changes from the original. The only changes are here just to make it works for our needs. They are only quick patches, made in a pragmatic approach. The original version didn't work ootb, for our needs (mainly swagger v2). So needed to patch some little things, without understanding the big picture. My version, and it's pypi package, are only here, for our needs. (If it works for someone else, it's a hazard). I can't maintain the whole thing, for everyone. I am not a swagger expert (and don't want to be) ... Because it seems, that every organization adapt rules for their needs (without respecting the originals one, at least, for v2) ... It should be a big work, to make it work for everyone ootb. (If it's possible). Btw, the original was a good start for us, because 95% of things worked, compared to others libs. My version still continue to work for us, and we use it like that ...(hope it will continue, like that) ... But I won't accept patches that could broke the thing. I'm in a pragmatic approach, and don't have the pretention to make something as good as this old pyswagger ;-(

But like you, it didn't work ootb, so needed to patch ... And so, I forked the repo, and started my branches (for me needs only)

If one day, pyswagger goes in an active state (with lot of patches) ... I will try it ... And if it works ootb, my version will be discontinued ... For sure !

Regards

Le mer. 16 mars 2022 à 14:58, Jonathan Senecal @.***> a écrit :

Hi @mission-liao https://github.com/mission-liao , @manatlan https://github.com/manatlan .

I strongly believe that this project has the potential to kick off due to many platforms (namely django-rest-framework and FastAPI) now using OpenAPI (fka Swagger) spec should it be maintained. I, myself have run into many issues trying to use this as is and would be willing to contribute back should my changes be merged and the project release new versions.

I see that @manatlan https://github.com/manatlan has a lot of changes in his fork, and I wouldn't mind using it as a "start" but I believe that no-one should have to dig through a project network of forks to find one that works properly and is maintained.

All that to say that if you are willing to accept new maintainers of this project, I could volunteer as potential maintainer😃

— Reply to this email directly, view it on GitHub https://github.com/pyopenapi/pyswagger/issues/193#issuecomment-1069160150, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABEZQUUOJTJIE2KC7D25ETVAHSILANCNFSM4YJY5ATQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>