WANTED: Owner for Autofac.Extras.Moq

[tillig]

As folks may have noticed, the Autofac.Extras.Moq package largely goes unmonitored/untouched. There are a couple reasons for that:

• Limited bandwidth: There are currently only two active owners for core Autofac and all of the integrations/extension packages. That's two people with day jobs and families and other hobbies spread across all the packages. We do have occasional PR submitters, which is awesome, but reviewing PRs is not a zero-time investment, either.
• No clear vision: The Autofac.Extras.Moq package was a community-provided submission from many years ago (>12!) that had a sort of basic functionality but no real owner or clear vision for what it was supposed to do. When we see inconsistent behavior... which behavior is the right way for things to work? What do we make consistent? That wasn't documented, and it's not something the current active owners have time to figure out given neither of us use this package.

What we need is someone who can come in and provide ownership for the package. Unfortunately, ownership isn't a small task. It's not "throw in a couple of PRs and we're done." Ownership is...

• Answering support questions. That's stuff that comes in via issues and via Stack Overflow.
• Responding to issues. At the time of this writing, there are three issues hanging out. What are we (you?) going to do with them? Are they valid? Do they need more info? Do they still make sense?
• Keeping dependencies up to date. As new core Autofac or Moq releases go out, you need to determine if you should update the dependencies in this library and cut a new release.
• Ongoing code maintenance. We do get some PRs, but not very many. The vast majority of the time, you'll have to fix the code yourself.
• Ongoing documentation updates. As new features or FAQs come up, it's up to you to provide updated documentation and/or examples.

That's a big commitment. But that's also why movement here has stagnated - we don't get a lot of contributions, and with .NET Core in the last few years coming in and changing the landscape quite a bit for DI, the primary focus for current owners is core Autofac and ensuring the .NET Core integration is kept up to date.

Without an owner, issues in this repo will likely go untouched. PRs may hang out and not get reviewed or integrated. I'm sorry about that, it's just kinda how it is. If there's no one to provide that clear vision/direction on how the library should operate, any new feature or fix could be a benefit to some folks and a breaking change for others.

We haven't gone straight to maintenance mode with this library because it is reasonably popular on NuGet. We just don't have time to own all the things.

The alternative to all of this, of course, is that you can fork this library and do what you want - fix one tiny thing and call it good. But if you want to help the larger community... drop us a line on this issue and be an owner!