>I suggest that the vxl-users list be made member-post-only if it is not already. Then setup the welcome message to include a link to a "list policy" web page. The policy page could have text like:
>The vxl-users list is staffed by a purely voluntary group. The list is provided as support for users to get answers to questions that may involve vxl-specific knowledge and are best answered by a vxl developer. We are unlikely to take the time to answer general programming questions that can be answered by any experienced programmer. This includes trivial errors such as "include file not found" and "unresolved symbol" even if they appear when trying to use vxl code. If you are seeing such errors please consult with an experienced programmer in your group to confirm that it may be a real vxl problem before posting to the vxl-users list.
>If you have determined that your question is best answered by a vxl developer then it will be considered appropriate for the vxl-users list. However, when posting said question please include sufficient details. These include the versions of vxl and the compiler you are using....
You may also want to do what I do for the lists here at Kitware. If a non-member posts
to the list, it sends them a message that says basically this message will be ignored and
never approved, please join the list to post. The reason is to avoid SPAM on the list.
Then I just periodically, and indiscriminantly delete all the pending messages. It saves
a bunch of time, and avoids the problem of stupid questions being posted after the
person has already figured it out because it took two weeks to approve the post.
On the other hand, as the toolkit gets more popular it will be impossible to stop stupid posts,
and the best recourse is to either not answer them, or answer with a canned response.