Looking for additional maintainers
lukeautry opened this issue · comments
Hey all!
I'm pretty busy and can't keep up with the influx of great feedback and pull requests.
Please post in this issue if you're willing to help as a maintainer. Maintainers preferably should have submitted pull requests before and have some (if superficial) knowledge of the codebase.
I'm not sure how much I'll be able to contribute, but I'd be up for helping out as much as I can.
I can help as well. I've got two open pull requests at the moment. There's a lot about TSOA that I'm not familiar with, but I'm willing to learn!
I was just about to come ask here if tsoa will support the oneOf Swagger keyword in the near future, and perhaps I can contribute in that way, missing features, etc? Likewise, I also do not know the codebase very well, but am also willing to learn.
One quick suggestion: Add a "help wanted" label to issues that you know can't be addressed in the near future.
As for me, I'm using tsoa for a huge personal project and I learned the codebase by fixing some bugs I found during development process. I'm willing to contribute as much as I can, this is a super cool project!
I'd be happy to help out, as well. I'm currently building out a middleware for lambda-api
Hi all. Great project, would love to help contribute. Even though this is my first foray into"code-first" api doc gen, I love the fact that tsoa is very straightforward to use and your documentation is succinct. I was able to generate API docs from my Google Cloud Functions very easily. Other tools like this were too bloated or documentation was not very clear (irony) so I couldn't even tell if any of them handle typescript-to-swagger generating.
By any chance do you have a page setup for your project goals? In particular, I have been trying to find out how to generate subroutes in my controllers (much like C# RoutePrefix decorators)...looking through the code I didn't see anything. If this doesn't exist yet, please let me know if you have any recommendations on how I can contribute towards this. Would love to see tsoa grow into the standard toolset for typescript-to-swagger formatting!
Anyone willing to contribute, please feel free to comment on issues or voice opinions on PRs. I think the biggest part of the work is evaluating both of those.
Count me in. :) Also, I think an easy way to get help is to start adding labels to the issues like "Easy first issue." That's helped me to get involved with more open source projects.
Hey!
I would like to help to,
After merging 2 PR and had part in another I'm starting to get to know most of the base code.
Hi, I want to help. I sent a pull request of a implementation of:
#180
Im using tsoa at work and we need this feature.
@CristianoVotre how were you able to submit a PR without using the pull request template?
@WoH, your help has been invaluable recently. Would you be interested in being an additional maintainer?
If so, reply and Luke can hook you up. :)
Even if the answer is “no,” I’d like to take a moment to express gratitude for your contributions. :)
Even if the answer is “no,” I’d like to take a moment to express gratitude for your contributions. :)
Thanks for your kind words and your immediate feedback that kept motivated 🍻
I'm not sure about being a maintainer because I don't see myself being able to handle community interaction even nearly as patiently and friendly (compared to you). Maybe if you are looking for someone to tackle features and reviews, but if you're looking for someone to provide comprehensible documentation and responses to issues, you'll most likely be able to find someone significantly more valuable.
@dgreene1 @lukeautry Would you be comfortable with me being an additional collaborator to coordinate a 3.0 release and manage issues related to that?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
Somewhat related but I want to say @WoH has been doing amazing work on 3.x release -- I am saying that based on reading the doc changes as I actually haven't tried it out yet but will try to migrate to it soon.
Thanks everyone for your contributions to the 3.x release!
Thank you so much
Wouldn't have been possible without all the PRs from @Eywek @jfrconley @fantapop @dgreene1 @aldenquimby @dimitor115 @michaelbeaumont @itamarco @AlexChambers @edbrannin @jreusch @jtfell @simllll @rgripper @marius-usvat @0v3rst33r @ryankeener and yourself! (Sorry if I forgot anyone)
I hope your upgrade goes smoothly, if there are any issues, please post them!
I am unsure on whether this issue is still relevant but just wanted to also say I'd love to help as much as I can to contribute.
If you're still looking for more maintainers I'd love to help on that front too, although I've never been a maintainer so I am inexperienced.
Hello everyone!
Apart from looking for maintainers this way, have you considered using a reward system to incentivize collaboration from external devs? I think people will be more eager to collaborate on this project if there would be some way of financial compensation. It will also make it easier for individuals/businesses to financially support the project
I created a platform for this type of situation, opire.dev, and the code owners will receive a % of the rewards when created by someone outside the organization.
TSOA it's a solid product that I've been using, and I'd love to be able to put money into solving issues that may be causing people to decide to go with alternatives.