Sebastian Redl wrote:

...

I would like to suggest that Boost have separate NGs for each individual library. I also think, for each individual library, a separate user and developer NG should exist.

While this will lead to many more NGs, it will make it much easier for users/developers to have concerns addressed for a particular Boost library, and to have the implementor of that library address those concerns. Also of course it will make it easier for people interested, or working with, a particular Boost library, to go to the appropriate NG to read about any issues brought up regarding that library. A developer list per library might make sense. However, a user list per

Edward Diener wrote: library would, in my opinion (and experience from forums), mostly lead to misposted messages.

Boost users are better than you assume them to be. If there were individual user library NGs I believe the vast majority of users would follow that guideline to post to the appropriate NG.

On Mon, Jul 14, 2008 at 12:33 PM, David Abrahams <dave@boostpro.com> wrote:

...

Boost users are better than you assume them to be. If there were individual user library NGs I believe the vast majority of users would follow that guideline to post to the appropriate NG.

FWIW, we get get a lot of Boost.Python posts on the boost-users list even though there's a project-specific list.

I believe that would be less so if, as a policy, each and every lib had their own list, with maybe one general for those cases where the user does not know where to ask. I am a user of some libs all of which are handled in a common list. If I became a user of Boost.Python I don't think I would try to find if the specific list exists as I am used to a common shared NG. I guess it also depends on how clear it is in the docs where to ask... David