Swashbuckle.aspnetcore: Last updated 6 months ago, hmmm...

Created on 10 Oct 2017  路  6Comments  路  Source: domaindrivendev/Swashbuckle.AspNetCore

I don't want to be the guy who's bugging the single owner of an after-hours, open-source project. But, is anyone looking at these pull requests? Is the project dead?

BTW: AppVeyor -> Project not found or access denied.

Most helpful comment

There are a lot of open issues and a number of useful PR's - it would be shame to see this project die because @domaindrivendev doesn't have the capacity to deal with them.
Perhaps he needs to put out a call for maintainers in the same way he has done for the original project?

This is an excellent project used by a growing number of people - it would be a shame for it to die because people have to fork it to get in the features they need.

@domaindrivendev You have done an excellent job so far as sole maintainer - do you need help to keep this going?

All 6 comments

Maybe we should fork this project? There are several very simple pull requests and yet they are stuck and not merged.

@domaindrivendev is actively looking for maintainers on his original Swashbuckle project. Maybe he should do the same thing for Swashbuckle.AspNetCore?

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,

Are there any "core" contributors / maintainers out there who can help @domaindrivendev bringing this project further?

I'm currently looking around in this project? is it still maintained after the above post? I've started a port on my own, just wondering if i should PR it into here?

Having lots of trouble with Kubernetes/Swagger UX behind nginx.

I managed to get a local build running under .net standard with swagger 3.5, excluding full blown verification it works fairly well. It fixed the stuff i needed for my purposes :)

There are a lot of open issues and a number of useful PR's - it would be shame to see this project die because @domaindrivendev doesn't have the capacity to deal with them.
Perhaps he needs to put out a call for maintainers in the same way he has done for the original project?

This is an excellent project used by a growing number of people - it would be a shame for it to die because people have to fork it to get in the features they need.

@domaindrivendev You have done an excellent job so far as sole maintainer - do you need help to keep this going?

If you take a look at the recent activity it should be clear that this project is still very much alive. But, please bear in mind that just because a PR is there and happens to solve an issue for you specifically, that DOES NOT mean it's high enough on the current list of priorities to be assessed, let alone accepted.

Rather than thumbing up a generic issue like this one, I would encourage folks on this thread to a) make sure their issue is being actively tracked in an open issue and b) continue adding comments to that issue. Typically, the issues with a lot of _constructive_ comments and feedback are most likely to make their way up the list of priorities.

Was this page helpful?
0 / 5 - 0 ratings