So we have fairly strong support for the idea that recipe requests (AKA "recipe-swapping" questions) should be out of scope for the main site. I'd prefer not to rehash the rationale; for anyone who's not familiar with this subject, please see the following:
- Should “I need a recipe for X?” questions be off-topic?
- Restaurant mimicry questions allowed?
- What should our FAQ contain?
Thing is - there's also some pretty heavy resistance to the idea:
- Why is recipe swapping a bad thing?
- Something strange and is the scope of the site to narrow?
- ...and various answers and comments in the first set of links.
I think it's hard to argue that, in the big-picture view, a large number of recipe requests would be bad for the site. But I can see this argument dragging on for a long time (think SO and career advice), and major disagreements like that are also going to be bad for the site.
So I propose that we meet these people halfway: Create a dedicated recipe site that works like meta.
The way I see it, this makes sense on every level:
Migration is a more polite response to newbies than closing their questions;
It should satisfy the dissenters;
It eliminates any possibility of rep- or badge-farming (since rep is derived from the parent site, and badges don't carry over);
It eliminates front-page clutter;
The recipes would be indexed and searchable;
It supports voting and ranking, which is probably why some people are so dead-set on using the F&C SE for it.
People who use the "recipe meta" site would probably be more willing to help migrate recipe requests there instead of arguing or voting to reopen on the parent site. (In other words, we could all be on the same team here.)
At the very worst, it would stagnate and collect dust - doing no harm to the parent site, but proving that recipe swapping isn't necessary or helpful to the community's survival.
Maybe I'm missing something, but to me, this is win-win. Can we get this implemented ASAP? Or does anybody see any serious problems with it?