Comment 1 for bug 1234738

Blueprints have been spammed for something like the last seven or eight years, sadly, not just the past year. It's a very long time since looking through the blueprint list was a remotely helpful indicator of developer activity; and most of the blueprints filed by casual users never get any attention, since they have been misled into thinking that filing a blueprint is a useful way to make a feature request, rather than a mechanism for developers to plan, coordinate, and record non-trivial feature development work.

I think it'd be reasonable to use the members slot for this. Really, blueprints are a tool for developer coordination, but it's quite common for them to be registered by people in management positions and I think the developer slots would be a bit too restrictive in practice. The bar for membership should be low enough that anyone who's really involved shouldn't have a problem, while it would steer casual users to more constructive avenues for feature requests.