Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project continuation #2773

Closed
kant2002 opened this issue Mar 19, 2024 · 3 comments
Closed

Project continuation #2773

kant2002 opened this issue Mar 19, 2024 · 3 comments

Comments

@kant2002
Copy link
Contributor

Thank you for your work on this project.

Given recent announcements is there a way that you start cooperate with community (at least me) on the project transition.

I understand that you maybe cautious give project to strangers or have other concerns.

If you have process in your mind which is best suited to you, please tell us.

if you want speak privately I think I have my email/Twitter/Mastodon in my profile.

@pinkfloydx33
Copy link

As someone who has spent an inordinate amount of time customizing swashbuckle for work and personal projects, I would be devasted to see this project go unmaintained. I too would be willing to help keep it alive as a maintainer

@skellyapi
Copy link

skellyapi commented Mar 21, 2024

The developer, @domaindrivendev , is actively searching for someone to take over ownership and if that falls through, he'll actively seek maintainers from the community; reference . @Havunen has created a fork which has included many commits related to issues reported on this repo.

The time saved by this project is major and I sincerely hope the dev understands how much we all appreciate his efforts over the years. Ideally Microsoft steps up to sponsor or even fork it to maintain as their own; in my eyes it has saved us hundreds of hours and switching to a solution like NSwag will take time and investment given we've standardized usage within our APIs.

Unfortunately, it looks like Microsoft will be pulling Swashbuckle from it's WebAPI template moving forward with .NET 9. I hope it means that they will offer mechanisms further extending OpenAPI and Swagger such that if swashbuckle ceases maintenance completely, we have easy mechanisms to replace with what is support by Microsoft.

@domaindrivendev
Copy link
Owner

See #2778

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants