From: Mark Rodgers (mark.rodgers_at_[hidden])
Date: 2001-07-17 00:33:11
> While I think that there is some danger of people viewing "guidelines" as
> "requirements", can't that be dealt with?
> * Clearly identify the actual hard requirements in a separate document.
> * Make sure each link on the web site to the guidelines document
> that it is just that; a link to guidelines for developers who feel the
> need, and not a requirement that must be met by all Boost libraries.
> * Improve the caveat at the beginning of the guidelines document.
> * An edit of the guidelines document itself, rewording imperatives if
> If all those safeguards are in place, do you still think there is too much
> danger the guidelines will be seen as requirements?
Yes, unless you add
* Host them on another site with no Boost banner, etc so they are clearly
not Boost endorsed guidelines.
The danger is that Boost will be viewed as some authority (which is good)
so therefore any Boost-endorsed guidelines will be taken as holy writ no
matter what we say.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk