Calling for Maintainers

[domaindrivendev]

With the introduction of ASP.NET Core, I've now shifted my focus to the Core-specific project - Swashbuckle.AspNetCore. That project will be receiving most of my (already limited) personal time, and so I won't have the capacity to maintain this one at a sufficient rate. Still, I'd love to see it live on and am seeking one or two "core" contributors / maintainers to help out. Ideally, these would be people who have already contributed through PRs and understand the inner workings and overall design. Once signed-up, we can agree on an approach that works - ultimately, I want to remove myself as the bottleneck to merging PRs and getting fresh Nugets published. If you're interested, please let me know by adding a comment below:

[svrooij]

Sign me up.

I've been using this package for a long time, and think I could be a good help in maintaining all the pull-requests.

[lockewritesdocs]

I am interested in helping to support Swashbuckle documentation (I'm a tech writer). I implemented Swashbuckle for one of our C# APIs and think it's rather fantastic, so let me know where I can assist!

[domaindrivendev]

Awesome - I'm thrilled to see these responses. @heldersepu - I'm especially grateful for all your issue responses and PR's over the last few months.

For next steps, how do people feel about getting on a Google hangout and talking in person? There's some planning to be done!

[domaindrivendev]

Yeh - I'm fairly opinionated about what should be included with the core package and what should be left to application developers via the wide range of extensibility options.

So ... I want to triage and apply that lense. Of course on the flip side, I haven't had the bandwidth to provide feedback and I'm sure that's frustrating for contributors. Hence my desire to get us on the same page before opening the PR floodgates

[lockewritesdocs]

@heldersepu, I agree that the README can be broken out into separate pages. Additionally, I think that a short "Getting started" tutorial with more in-depth examples could be incredibly beneficial.

[lockewritesdocs]

@heldersepu, sounds good. However, the link that you provided is broken, and I could not find the Swagger_Test project in https://github.com/heldersepu/csharp-proj.

Also, I added code to modify Swashbuckle so that it generates a swagger.json file, which I then served up to DapperDox. It's a pretty cool integration, and I wonder if it's worth documenting. Thoughts?

[domaindrivendev]

@lockewritesdocs - regarding use of the wiki, I'm all for splitting up the docs for improved readability but I'm on the fence about wiki vs readme (or collection of) that are source controlled along with the code. I prefer the latter, because I like PR's (especially feature enhancements) to encapsulate a "complete package", including any required doc updates. Unless I'm mistaken, source control and the ability to incorporate into PR's isn't possible with a WIKI? On the flip side, I could be convinced if you have other compelling reasons :)

@heldersepu - thanks again for all you're continued work. I know I need to give you more support and at a minimum give you the ability to merge and release to Nuget. Like I said, I just wanted to align a little before doing so. What's next week like for you - Would you be free to chat for an hour Mon or Tues around 4:30 PST. @lockewritesdocs & @svrooij you're also both welcome to join too.

Regarding contact details, it would make most sense for you guys to connect with me over linkedin (https://www.linkedin.com/in/richard-morris-08479821/), then we can share emails for a Google hangout.

[lockewritesdocs]

I've been absent for quite some time; lots of things happening in my world right now.

Have either of you thought about using GitHub pages for the documentation? That implementation enables publishing docs from the source code, circumventing the problem that @domaindrivendev mentioned with a wiki. I think that the README has a lot of valuable information, but needs to be broken up into separate sections. Having that much content in a README is overwhelming IMO. A README is meant to provide a brief description of the tool, what it does, and how to get started, whereas the remaining information could be well organized in GitHub pages.

Thoughts?

[sachinjegaonkar]

I would like to contribute to this by any of the means that you see. I have used Swashbuckle in one of our projects. Enthusiastic to get a chance to work on this kind of project. Primarily, I use C++ and C# for my work. Let me know how can I help you.

[monemihir]

Would love to help out. Been using Swagger for a long time with Swashbuckle.

Would also be very interested in helping out with the AspNetCore package since we are moving to AspNetCore as well for the product which uses Swashbuckle. Currently we have it running happily through .Net Mono but have to maintain 2 code bases (not because of Swashbuckle) due to some idiosyncrasies of Mono.

[PaulDotNet]

I want to get my hands on AspNetCore. There are some basic things that have to be merged but they are stuck, Sign me up.

[mkondaveeti]

Richard , I have good experience in using swashbuckle. I had experience in overriding message hanndler and implementing filters for one of my clients for customtoken url and taking [] from generic types.
I have many times debugged entire swash buckle code for customization. Please sign me up.

[Alfetta159]

Let me know if I can help. I'm starting to use Swashbuckle for Core as I try to use .NET Core as much as possible.

[lonesomegeek]

I'm interested, needing help?

[gbaychev]

Hi everybody,
I just came by to ask what the current status is? Are there enough maintainers, is the project dead, what is happening? It seems that the last commit on master was a year ago.

Paging Mr. @domaindrivendev

Regards

P.S I don't mean any disrespect, I'm just curious what the situation is

[gbaychev]

Ok, dead it is then.

[domaindrivendev]

I'm devoting 100% of my spare dev cycles to the ASP.NET Core version of this tool and therefore am unable to continue maintaining this particular repo. So, I see two potential options:

1. Completely handover continued maintenance to one or more of the volunteers from this thread (@svrooij, @lockewritesdocs, @sachinjegaonkar @monemihir @mkondaveeti, @framebassman, @Alfetta159, @lonesomegeek). Please let me know if anyone from that group has the capacity to drive such an effort.

OR

2. Sunset this repo and redirect interest to an active fork such as Swagger-Net.

[lockewritesdocs]

I changed jobs about 1.5 years ago and have not used Swashbuckle since leaving the previous company. I definitely cannot maintain this project.

[jv42]

@domaindrivendev I think the second option would be best, as there is indeed an active fork.
Of course, that's only my opinion ;-)

[OskarKlintrot]

@heldersepu has already done a lot of work on Swagger-Net so that would indeed make sense. IMHO :)

[gbaychev]

Alright guys, thank you for the heads-up.

Also big thanks for @domaindrivendev . Just wanted to let you know that the swagger is one of the most beloved features in our REST APIs, especially among our QA and 3rd party and this is thanks to you.

[robinrodricks]

I am willing to maintain this project. I already took over FluentFTP from the original author three years ago and its now blossoming just fine, with tons of new features, PRs, issues fixed, nuget package, etc. @domaindrivendev Please contact me if you are willing to handover.

[Calebyang93]

Hi @domaindrivendev I will be interested to help to maintain the codebase if there are issues. Will read up on documentation and practice if you need help.

[TheMrAnderson]

@domaindrivendev I use this in my current job as we have some APIs that are too troublesome to move to .Net Core. I would be interested in helping to maintain this and even upgrade to Swagger 3.0.