Why is this project so inactive from past year?

[nithinbandaru1]

I do not see any new commits on this repo for almost a year now.

Probably you guys should ask for new maintainers to come in ofcource if current maintainer is willing to take new maintainers.

I see some PRs that are ready to be merged but not sure why they are not being merged yet.

[soroshsabz]

ITNOA

@domaindrivendev Did you have any note about this issue?

Did you can add some collaborators?

[soroshsabz]

for example you can add https://github.com/mattfrear as collaborator

[ramondeklein]

@nithinbandaru1 Please note that @domaindrivendev created this awesome piece of software free of charge. Although a lot of companies rely on this (we do too), it's not fair to push a developer like this. Shouting (using capitals) doesn't prove your point. I have written some open-source software myself and I really hate that people think they're entitled to get support when they need it. Something like open-source doesn't exist in other branches. Let's be humble and appreciate the people that put in their time without needing anything in return...

I also hope that @domaindrivendev will pick up the project or will leave it to someone else to take over. To be honest, it's in the top 25 of projects and maybe Microsoft should step in and sponsor the project, fork it, ... But even if he complete abondons this project, then we still need to be thankful for it. Priorities may shift and maintaining a library like this takes a lot of time.

[nithinbandaru1]

@ramondeklein

• Firstly, I really appreciate the project and the value it brings in.
• I am really not looking for any immediate support, bug fix or feature request as I am not facing any breaking things at my end, I can still be happy with what this repo offers, but when I was going through recent reported issues, I came up with this.
• Capitals is used to stress it out to know what the status of this repo is as I beardly seen replies on the issues. I see this point is discussed in other issues too. So, wanted to know what's going on with this project by adding a separate one.
• I see 177 contributors for this repo and 0 commits on main branch. So, I am just showing my concern for this repo, that's it. I am not asking them to write code, but I see some ready to merge PRs.
• "People feel entitled" - Please don't take it to heart, I am just trying to see if this repo is still active or not. It also really helps people who are using it to know the future with this repo. I am not sure why you felt bad about this.
• I 100% agree that for sure Microsoft should take up this repo into their foundation and maintain it.

[ramondeklein]

@nithinbandaru1 It's pretty clear that this repo is very active, but it seems it's not maintained anymore for the past year. I'm concerned about it too, but submitting an issue with all capitals won't motivate any maintainer. That's why I downvoted it.

The reason why I think Microsoft should step in, is because they actively promote this package in the Learn ASP.NET Core documentation. That's one of the reasons why we started using it. We were not alone, because this module is in the top 25 list of most used .NET Core packages. If we knew it was a one-man project (at least the maintainer), then we might have choosen something else.

Being a developer of a highly popular project is probably hard. It requires a lot of dedication, with hardly any benefits. That's also one of the reasons why the developer's of Identity Server have gone commercial. There are not a lot of companies that sponsor open-source projects.

[nithinbandaru1]

Sure, Internet has a different story about this repo.

• https://www.reddit.com/r/dotnet/comments/188nfpp/should_we_be_concerned_about_swashbuckle/
• https://learn.microsoft.com/en-us/aspnet/core/tutorials/getting-started-with-swashbuckle?view=aspnetcore-7.0&viewFallbackFrom=aspnetcore-2.2&tabs=visual-studio
• Improvements to Swagger generation dotnet/aspnetcore#4854
• https://github.com/dotnet/AspNetCore.Docs/issues?q=is%3Aissue+is%3Aopen+NSwag
• NSwag.AspNetCore instead of Swashbuckle.AspNetCore dotnet/aspnetcore#50133
• It looks like Microsoft also did some contribution in past
  • Add support for Microsoft.AspNetCore.OpenApi strategy in NSwag RicoSuter/NSwag#4163 - In issue description I see 2 Swashbuckle PRs
• In past @domaindrivendev in this repo added a request for Maintainers https://github.com/domaindrivendev/Swashbuckle.WebApi, but he did not do that for this repo, so that make it more concerning as he is silent.

[mlapaglia]

"Swashbuckle is not supported in .NET 8 and later. For a supported alternative, see ASP.NET Core web API documentation with Swagger / OpenAPI." could be why?

https://learn.microsoft.com/en-us/aspnet/core/tutorials/getting-started-with-swashbuckle?view=aspnetcore-7.0&viewFallbackFrom=aspnetcore-8.0&tabs=visual-studio

dotnet/AspNetCore.Docs#31437

[schnerring]

Twitter or Reddit are better platforms for ranting.

@nithinbandaru1 If the "internet already has a different story", re-iterating the same point with an uppercase-titled issue has zero value. Everybody can see the concerned comments, as well as everybody can see that the maintainer is inactive.

You're always welcome to fork the repo and incorporate PRs or your own fixes into that fork. And if you do a good job and people start using your fork, congratulations, you're the new maintainer of Swashbuckle. 😅

EDIT: removed rant, sorry!

[nithinbandaru1]

@schnerring

Well, I really don't mind your opinions. All I care is about the status of this repo.

I think the maintainer is not going to be stressed with this 🤔🤔. If in-case he comes across this issue, he will announce for maintainers if he wants this lovely project to be alive or leave it to die. Both are good for community to have an answer, Because of this issue maintainer is not going to merge all PRs by taking stress on him.

Reaction for comments gives notifications. Interesting I did not get any of such. Something new 😁. Let me check.

NSwag repo is of multiple tools set, obviously it will have many issues compared to this repo. But in terms of swagger generation it almost similar.

Well, I don't need your suggestion to fork and become maintainer, if I had intentions to become maintainer I would have already asked. What I said is making an announcement like the maintainer did in his other repo will probably make this repo active again if someone comes in to take it up. I think that's how opensource can be alive, it's impossible for 1 person to keep it going. NSwag also have to do it at some point.

To be clear: I never have any intentions to insist, insult, stress maintainer to work on this repo. All I said is there is one last action that maintainer can take as he is too busy with other things in life. By the way I will have 0 benefits of this repo being alive in my life.

By the way the issue more about getting new maintainers if there is anyone willing. I think Capitals is getting more attention than the issues intention. Let me change that first 😁.

[Havunen]

I created a fork of this repository, because I couldn't wait for the maintainer of this repo.
The fork is called DotSwashbuckle https://github.com/Havunen/DotSwashbuckle it only supports .NET 8 for now.

Change the csproj nuget reference

-<PackageReference Include="Swashbuckle.AspNetCore" Version="6.5.0" />
+<PackageReference Include="DotSwashbuckle.AspNetCore" Version="1.0.2" />

Install the dotnet tool

dotnet tool uninstall --global Swashbuckle.AspNetCore.Cli
dotnet tool install --global --version 1.0.2 DotSwashbuckle.AspNetCore.Cli

1.0.2 is the first working version.

I am planning to maintain that repository at least until this repository picks up with the development, so if you are interested using it you can post issues or open PRs there.

Check the latest available version from Nuget

[martincostello]

FWIW, NSwag is actively maintained and supports the typical OpenAPI use cases.

If you haven't made a significant investment in Swashbuckle-specific features, migrating to NSwag isn't a massive change on a per-repository basis (example). Of course if you've used it in hundreds of repositories that's a different matter.

I've migrated all of the apps I personally maintain to NSwag as it at least has active development.

[domaindrivendev]

I appreciate this comment by @ramondeklein more than anyone could imagine. The journey I've take with Swashbuckle has been amazing but has also left me somewhat disillusioned with open-source, particularly from the perspective of maintainers/authors.

Not saying it's apparent in this thread but the "entitlement" I've witnessed over the years from users of this software has at times left me gobsmacked. Furthermore, I can't escape the sense that the biggest benefactors of OS tends to be companies driving profit. Sure it helps fellow devs and that's great but ultimately that just helps the companies those fellow devs work for. And, while there's some lip-service from some of those companies around sponsorship etc., in reality I've never seen it amount to anything more than a drop in the ocean vs the personal hours and value created - at least not in my experience.

Anyway, with all that said, I'm afraid I cannot justify giving any more of my time to this project. I'm chatting with one or two potential owners to transition it to - one in particular I feel would be an awesome fit. So hopefully will have an update on that soon. And, if that falls through, I'll renew the call for maintainers from the community and try be more responsive to get that squared away quickly so hopefully the project can start to thrive again.

[soroshsabz]

new version of DotSwashbuckle was released with merge many of PRs in this repo.

the address of DotSwashbuckle repo is https://github.com/Havunen/DotSwashbuckle

Thanks, and Congratulation to @Havunen

[soroshsabz]

@domaindrivendev very thanks for all of your works in many years :)

Surely you yourself know well, but from my point of view @Havunen and @mattfrear are very good options for collaborator of this repo

[mareek]

Anyway, with all that said, I'm afraid I cannot justify giving any more of my time to this project.

Thanks for your answer @domaindrivendev.
Can you update the README.md file to notice that this project is on hold while you're searching for a new maintainer ?
This would be helpful to people who expect some pull request fixing a bug will be merged in the near future

Thanks in advance.

[VictorioBerra]

Just want some clarification @Havunen should we be using https://github.com/Havunen/DotSwashbuckle or are you taking over this repo and we can stay on https://github.com/domaindrivendev/Swashbuckle.AspNetCore ?

[Havunen]

I don't have any access to this repository, appveyor or nuget.org, so I will continue developing my fork

[Herve-M]

FWIW, NSwag is actively maintained and supports the typical OpenAPI use cases.

If you haven't made a significant investment in Swashbuckle-specific features, migrating to NSwag isn't a massive change on a per-repository basis (example). Of course if you've used it in hundreds of repositories that's a different matter.

I've migrated all of the apps I personally maintain to NSwag as it at least has active development.

NSwag is nice but documentation is 50/50 contrary to Swashbuckle :/

[domaindrivendev]

I don't have any access to this repository, appveyor or nuget.org, so I will continue developing my fork

@Havunen fyi I messaged you on LinkedIn to discuss the possibility of contributing to this repo instead of forking. Let me know if you're interested?

[soroshsabz]

@Havunen Did you can see @domaindrivendev message?

thanks

[jonashendrickx]

I would be willing to step up as a maintainer if there is absolutely nobody else. I absolutely love the work that has been done here, and there's nothing like it that comes even remotely close.

[harvzor]

For those of you considering NSwag, I've done a high level comparison of the two projects: https://github.com/harvzor/swashbuckle-vs-nswag/

However, I'm looking forward to development on the forks of this project

[harvzor]

Also it looks like Microsoft plans on implementing their own Swagger implementation for dotnet 9: dotnet/aspnetcore#54599

[jonashendrickx]

They seem to have started the work. Seeing a couple open pull requests.

[domaindrivendev]

See #2778