Between developers of reusable components and reusers there need to be, as with any other piece of software, a relation of trust. There is always a tendency to regard any piece of code which one has not written oneself (with one's owns standards) as a risk — the not invented here syndrome. To increase the trust reusable components must have a specified quality level, and to ease understandability it should follow development and documentation standards. If possible potential reusers should be able to get in personal contact with the developers or maintainers of larger components, preferably before they commit to reuse it.