From 1251669ef3048ea91588caa6b3cb9b45b0e74053 Mon Sep 17 00:00:00 2001 From: Sebastian Schildt Date: Tue, 19 Apr 2022 10:26:13 +0200 Subject: [PATCH] License info: Address editorial review comments Signed-off-by: Sebastian Schildt --- docs-gen/content/license/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs-gen/content/license/_index.md b/docs-gen/content/license/_index.md index 673200b50..ddeb3aad1 100644 --- a/docs-gen/content/license/_index.md +++ b/docs-gen/content/license/_index.md @@ -10,12 +10,12 @@ chapter: false {{% /notice %}} ## Which license applies -VSS as well as the VSS-tools are covered by the [Mozilla Public License 2.0 (MPL-2.0)](https://opensource.org/licenses/MPL-2.0). The MPL-2.0 is an OSI approved Open Source license that gives you a lot of freedom using VSS in your products, or for (academic) research while providing a solid legal framework should you choose to contribute to either the standards or the tools. +VSS as well as the VSS-tools are covered by the [Mozilla Public License 2.0 (MPL-2.0)](https://opensource.org/licenses/MPL-2.0). The MPL-2.0 is an OSI approved Open Source license that gives you a lot of freedom using VSS in your products, or for (academic) research. It also provides a solid legal framework if you choose to contribute to either the standards or the tools. -We will line out some answers to commonly asked question, but keep in mind this page is informational. The legally binding clauses can be found in the [license](https://opensource.org/licenses/MPL-2.0) itself. If in doubt, consult your friendly neighborhood lawyer or IP department. +We will line out some answers to commonly asked questions, but keep in mind this page is informational. The legally binding clauses can be found in the [license](https://opensource.org/licenses/MPL-2.0) itself. If in doubt, consult your friendly neighborhood lawyer or IP department. ## Can I use VSS / VSS-tools in my commercial products -Most definitely yes. You must inform your users that the product contains MPLed code and need to provide access to the source (e.g. by linking to this documentation or our[our Github repository](https://github.com/covesa/vehicle_signal_specification)). +Most definitely yes. You must inform your users that the product contains MPLed code and need to provide access to the source (e.g. by linking to this documentation or our [Github repository](https://github.com/covesa/vehicle_signal_specification)). ## I modified VSS-tools, do I need to give away my source? If you use the code internally within your organisation (company), you have no obligations to do so. (see also [Q5 here](https://www.mozilla.org/en-US/MPL/2.0/FAQ/)). If you distribute the modified vss-tools outside your organization (e.g. to your customers), you need to make the source code of the MPL-2.0 licensed parts available. However, the MPL has only a very weak copyleft effect. As a rule of thumb: You have no obligation to provide code in new files. You have the obligation to make code of changed existing MPLed files available under the clauses pof the MPL-2.0, _if_ you distribute them in source or compiled form outside your organisation ((see also [Q9,10,11 here](https://www.mozilla.org/en-US/MPL/2.0/FAQ/))).