What you and others are suggesting is a Linux-like approach which shifts product maintenance and support from a vendor to the user community, at least to an extent. Regardless of whether that's a good idea or not, it is clear from Ken's replies that it is not something Microsoft is interested in doing. They like the bug tracking process they already have in place. To continue to belabor the point is really just tilting at windmills. Microsoft owns the product and they get to make the rules.


>I can see how, if it were implemented as a simple list, things could get out of hand.
>
>It'd have to have verification and voting features for each item, with an ability for the community to 'strike' a report if it were collectively deemed to be frivolous. Discussion threads and code samples would have to be enabled for each item.