The use of open source in website development has become mainstream - I dare say ubiquitous. Many developers utilize open source projects to build and scale dynamic websites. WordPress, Joomla, and Drupal are some of the more popular (you’ve probably heard of all three). LAMP stacks are used to run web servers. MySQL databases are used for website databases. Firefox is used to test and trouble shoot coding and rendering issues, as well as to browse; you may, in fact, be reading this post in it right now… I could go on and on. In the world of website application development you’d be hard pressed to find a site that doesn’t leverage open source code to some extent. Irrespective of size, organizations are running their websites using open source technology.
A critical consideration of a corporate open source software provisioning strategy revolves around the maturity of the community and longevity of that community continuing to develop their project.
Without an effective internal OSS governance strategy, enterprises both large and small are susceptible to problems and risks that can surface quickly when there is a lack of understanding and acceptance of open source software issues.
When scanning your software for open source software, it is important to set and understand your objectives. Your objectives may effect how you approach the task of finding the various open source software components and licenses, what the final reports will look like, and what you ultimately do with the information.
If you read a post on The Enterprise OSS Blog, please leave a comment. Let us know what you think, even if it's just a few words. Comments do not require approval, but they are moderated.OpenLogic reserves the right to remove any comments it deems inappropriate.