{"id":3476,"date":"2019-10-18T16:58:26","date_gmt":"2019-10-18T23:58:26","guid":{"rendered":"http:\/\/blog.light42.com\/wordpress\/?p=3476"},"modified":"2022-02-09T13:16:27","modified_gmt":"2022-02-09T21:16:27","slug":"oss-license-strategy","status":"publish","type":"post","link":"http:\/\/blog.light42.com\/wordpress\/?p=3476","title":{"rendered":"OSS License Strategy"},"content":{"rendered":"

this post is an edited, public version of a DRAFT internal discussion<\/em><\/p>\n

Preamble<\/strong>
\n This blog post is intended to bring together topics, facts, considerations and other useful information pertaining to upcoming licensing decisions on full-stack software. It is assumed that all license decisions must be made prior to hand-off of the works to the contract originator. All license decisions must exist in writing.<\/p>\n

As noted below, some person or entity must have signature authority to enact these license decisions. Subsequently in the project life cycle, it is recommended that a project steering committee be formed with the authority to make or reject further changes. <\/p>\n

note<\/em>:
\n · not all components must have the same license
\n · dual licensing of GPL and non-GPL is possible (more on this later)
\n · this is a data-driven project – data (a lot) is the origin and outputs data sets require their own licenses in any event because GPL and other OSS licenses apply to source code, not data
\n · the means to transform data into a base load, into a DOCUMENT, and read the outputs are code, and must be licensed<\/p>\n

The deliverable to the contract originator is “—-” (confirm)<\/p>\n

The Open Source Movement<\/h4>\n

Major software initiatives using an Open Source model have flourished in an unprecedented success over the last 15 years, with names like GNU, Linux, BSD Unix, Apache and Mozilla. If the ability of software developers to contribute to common source code, and to form functional communities focused on continuous improvements to their projects is the engine, then the application of standardized licensing to source code (and therefore to new contributions) is what keeps that engine on track.<\/p>\n

\nOpen Source by Definition<\/strong><\/p>\n