swagger-typescript-api
swagger-typescript-api copied to clipboard
acacode
Confused on how to contribute
The README states this.
P.S. If you are creating the PR, please check your changes with using command npm run prepare P.S. If you want to contribute please use the next branch. All PRs that has target master will be declined!
But prepare isn't a script in the package.json and the next branch is currently behind the master branch. 🤔
I'm a little concerned we haven't gotten a response to this yet. The last published update was almost 6 months ago now as well.
I really like this library and would like to see it stay relevant and continue to mature. @js2me are you open to sharing some responsibility to give others the ability to accept PRs and publish updates to NPM? There are quite a few PRs sitting ready to merge or get feedback. Right now it seems there is a bus count of one for this library :/
I would be interested in helping out where I can and potentially collecting more of your thoughts on the ideals and future you have in mind for this library in order to maintain the quality and focus.
@js2me if you're open to having a further discussion about this, it would be great to hear from you!
I think @js2me might be MIA... I sent him an email and tagged him in a Twitter post a few weeks ago and haven't heard anything from him. During my little investigation I noticed he is located in Russia and I worry with the situation over there that he may be temporarily unavailable or worse... :(
It's been 6 months since the last release. There are 188 issues and people regularly posting new issues. I think we are at the point that we need to find a new path forward.
I can't really commit the level of dedication for the project that @js2me has put into it. But I do feel passionate for keeping this project alive and believe I am capable of managing and leading the effort. For the purposes of moving forward, I am open to forking the repo and working to create a path to resolving issues and getting them upstream into a new NPM package on a regular basis.
I am not interested in splitting the community or making me the new single point of failure so I only want to do this with the support of others here and would require a few volunteers that are interested in keeping this repo alive and well to step forward. These people would become admins over the repo that have responsibility to manage issues, merge PRs and trigger new NPM deployments.
Anyone who is interested in helping out with this effort, whether through my proposed method or an alternative please comment below. I'm open to discussion and alternatives if others have a better solution.
(Pinging some past contributors for attention: @smorimoto @to-long @juliusBaranauskas @OutdatedVersion @pataiadam @azz @qboot @ApacheEx @hedgepigdaniel @cyclops23 @ajmnz @ivanovart @seivan @koolmonke @Soarc @Feargalicious)
@Jackman3005 He was active in february, so hopefully he is okay, just in a tough spot. Honestly, I like this package too and would love to help maintaining it, but it looks like people started using openapi-typescript as it quadrupled in weekly downloads over the last year. openapi-typescript-codegen looks like it has the same fate.
Hi @Jackman3005 support your concerns and ideas, sad to see that this project is dying
