title: Building a code asset library
body: <p>I have been thinking about setting up some sort of library for all our internally developed software at my organisation. I would like collect any ideas the good SO folk may have on this topic. </p>
  
  <p>I figure, what is the point in instilling into developers the benefits of writing reusable code, if on the next project the first thing developers do is file -> new due to a lack of knowledge of what code is already out there to be reused. </p>
  
  <p>As an added benefit, I think that just by having a library like this would encourage developers to think more in terms of reusability when writing code</p>
  
  <p>I would like to keep this library as simple as possible, perhaps my only two requirements being:</p>
  
  <ul>
  <li>Search facility</li>
  <li>Usable for many types of components: assemblies, web services, etc</li>
  </ul>
  
  <p>I see the basic information required on each asset/component to be:</p>
  
  <ul>
  <li>Name &amp; version</li>
  <li>Description / purpose</li>
  <li>Dependencies</li>
  </ul>
  
  <p>Would you record any more information?</p>
  
  <p>What would be the best platform for this i.e., wiki, forum, etc? </p>
  
  <p>What would make a software library like this successful vs unsuccessful?</p>
  
  <p>All ideas are greatly appreciated. </p>
  
  <p>Thanks</p>
  
  <p>Edit:</p>
  
  <p>Found these similar questions after posting:</p>
  
  <p><a href="https://stackoverflow.com/questions/1475316/how-do-you-ensure-code-is-reused-correctly">How do you ensure code is reused correctly?</a></p>
  
  <p><a href="https://stackoverflow.com/questions/529739/how-do-you-foster-the-use-of-shared-components-in-your-organization">How do you foster the use of shared components in your organization?</a></p>