I am asked two very reasonable questions, on a very regular basis, by some very interesting people.
If this hasn't already happened, eventually one or more of your customers are going to influence your open source software policy. Today’s blog article is a continuation of some themes established in my last post about when and how your open source software policy might need to be updated with new policy rules. In a variety of scenarios, your customer's interactions with or requirements of your products may directly or indirectly impact your open source policy. Traditionally, we often think of the end goal of an open source policy as dealing with license compliance. Because most open source licenses are triggered by "distribution," this leaves the potential for other open source use cases to go un-addressed in your open source policy. License compliance is not the only reason for an open source policy; technical support should also be addressed.
In today’s article I will discuss some internal and external events that may cause you to update your open source policy rules. For this discussion it is important to differentiate between the open source software (OSS) policy and the rules that flow from the policy.
Companies can increase the usage of some of the most innovative technology in the world, open source software, and manage the risk that comes along with it by creating policies that effectively build awareness, provide control mechanisms and promote low overhead compliance.
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.