In this blog post, we are sharing our new open source licensing model, which aligns the licensing models previously used by each of Hortonworks and Cloudera and also introduces some new changes. Meanwhile over the past few years, we’ve seen many of our industry peers revise their open source licensing strategies and/or their relationship with the Apache Software Foundation, generating questions of if we’re planning to revise our approach as well. Aligning the two models was one of the last items on our merger to-do list. Prior to the merger, the two companies distributed their products under somewhat different open source licensing models. We’re also a very innovative open source company, having collectively launched more than a dozen new open source projects since the founding of the two companies. With more than 700 engineers in the new Cloudera, our company writes a prodigious amount of open source code each year that’s contributed to more than 30 different open source projects. However, perhaps that is also a flaw.Open source has been core to the missions of both Hortonworks and Cloudera and central to our values and culture. Something that fits into the development workflow will help flag any issues as soon as possible and, with GitHub being familiar to so many developers around the world, the chances of it being adopted should be quite high. Will it help?Ī tool like this certainly looks to be useful for organisations trying to get a handle on their Open Source usage and compliance. Licensed helps automate this process and can also be used to create a “Bill of Materials” that enables users to see all the Open Source components used within the application. Typically, the license terms of an Open Source dependency will require that a copy of the license is distributed with future applications that contain it. Whenever dependencies change, the license data must be updated which helps things remain compliant. Licensed will store the dependency data in a source control repository, which helps make checking this data part of the development workflow. X% similar to an existing license i.e.This will flag up if the license appears to be: Using a project called “Licensee”, it automates the reading of license files and attempts to determine the license type. It finds, caches and checks the license metadata of dependencies and works across multiple languages and package managers across multiple projects. This tool is aimed at helping developers work towards compliance with the license terms of Open Source dependencies (an external software package used in an application) within their programs.
GitHub, the online home of over 20 million developers, have open-sourced “Licensed” – their own, internal tool for managing Open Source licenses.
0 kommentar(er)
