a. General Compliance ObligationsThese are things like: you can use the software as long as you meet the following requirements...b. Location of Notice RequirementsI love it when the author tells me specifically where I have to include attributions, like in my documentation, or in a Notice file accompanying the software. If the license says you must provide attribution but doesn't say how, then I suggest you create a convention for your organization than enforce it. For example, always include a 3rd-party attribution file somewhere users can easily access and read.c. Copyright NoticesThese are generally terms about not modifying or removing copyright notices. Sometimes they may ask you to add specific copyrights to your documentations.d. Warranty Disclaimer NoticeMost open source licenses disclaim warranty and offer their software to you "as-is." Make sure you review these so you are not caught off guard by unusual disclaimers in case of a dispute.e. AttributionsLike the "location of requirements" obligation, this section tells you who (author, organization, etc.) you need to mention or give attribution to in order to comply.f. ModificationsThese requirements tell you what you have to do if you make modification to the original code.g. Specific ObligationsWhile these might be covered under the more general categories they may contain special conditions, like if you advertise the use of this product you have to place specific attribution text in your advertising materials.Look for specific obligations that fall out of the normal categories.
Under what conditions is termination allowed or invoked? Familiarize yourself with these to make sure you don’t find yourself in a situation in the future that could trigger termination. Such a violation could cause you to lose your right to continue to distribute your product.
Some licenses contain sections to help you with compliance by providing sample attribution text or instructions on how to comply. Look for these types of terms usually listed near the end of the actual license text or in a separate README, COPYING or LICENSE file distributed with the open source software.
Many open source license are not written by lawyers and consequently do not always define key terms used in the license. If the open source licenses you encounter happen to have a terms definition section take time to understand how the various terms are used in the context of the license.
Cloud solutions and the term flexible seem to be joined at the hip with each new article, offering, and solution we see. Despite the repetition of the term, the inference of flexibility is not always clear nor is it well defined.When evaluating the flexibility of a PaaS solution, and how that fits with your current environment, be sure to look past "now" and examine what the horizon might hold for you and your organization. Being locked into the wrong cloud solution can limit the options you will have to choose from in the future, if the flexibility of the solution you pick doesn't match those eventual needs.
Examine the 5 C's of flexibility before choosing a flexible cloud solution:Customizable PaaS:PaaS offerings can enable you to quickly and easily deploy applications into the cloud by leveraging a standard, pre-built technology stack. However, most PaaS solutions don’t give you the ability to pick and choose your own technology components and versions to fit your specific requirements.Look for a PaaS platform that is completely customizable to your needs. Flexibility here will allow you to start with a pre-built platform, and then tailor the technology stack to your needs by adding or removing components and changing versions. Be sure that you have the flexibility to add your own code, blend proprietary software with open source, or create your own stack from scratch.Compatibility:Ensure that the cloud-based platforms you are evaluating fulfill the technical requirements of your applications and conform to your corporate architecture standards. You need to be able to pick and choose the components, versions, and patches that have been vetted by your technical experts, ensuring that your applications are supportable and secure. Once you’ve customized your technology components look for a fully flexible cloud solution that allows your team to share them with others on your team or in your company, giving your developers instant access to approved technology stacks that meet your enterprise needs.If you are migrating existing applications from your data center into the cloud, you'll need to be able to match the specific components that are already being used and avoid porting efforts that can be associated with a fixed PaaS option.Cost Management:
Cloud based solutions promise lower cost infrastructure options, but you can’t manage your costs unless you can measure your costs. A fully flexible PaaS cloud solution will provide the cost management capabilities that let you see your spend across multiple clouds and multiple accounts. With developers and business units often using credit cards to procure cloud resources, it’s difficult to track costs and meet budgets. Ideally you should look for a solution where you can register all of your accounts across all of your cloud providers, and then have real-time visibility into your spend.
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.