Debate on software reuse libraries

Does a single, general-purpose RSL or a domain-specific RSL provide the best method to leverage knowledge and assets across a large organization? My experience indicates the need for at least three fundamentally different types of libraries: local libraries; domain specific libraries; and reference libraries. Can RSLs can effectively interoperate across organizations? There are already come examples of the effective interoperation of reuse libraries. Does an RSL require a formal classification for components stored in the library? As collections grow, users will require more assistance in locating and selecting relevant candidates, but different classification mechanisms are relevant to different types of libraries. Must an RSL provide specialized reuse support, such as user registration, version control and problem notification? There will always be a role for libraries which are operated on a pro bone basis by members of the research community or other altruistic parties. On the other hand, as reuse transitions from a technological basis to an economic basis, there will be users willing to pay for additional services and there will be vendors willing to provide them.<
>