From 55c3cbe9caadd1d244b027fe1279a552fe5d87e7 Mon Sep 17 00:00:00 2001 From: Sebastian Schildt Date: Tue, 15 Mar 2022 14:56:29 +0100 Subject: [PATCH 1/4] Add license information to docs Signed-off-by: Sebastian Schildt --- docs-gen/content/ecosystem/_index.md | 1 + docs-gen/content/introduction/_index.md | 2 +- docs-gen/content/license/_index.md | 30 +++++++++++++++++++++++++ docs-gen/content/rule_set/_index.md | 2 +- 4 files changed, 33 insertions(+), 2 deletions(-) create mode 100644 docs-gen/content/license/_index.md diff --git a/docs-gen/content/ecosystem/_index.md b/docs-gen/content/ecosystem/_index.md index 52b9dc439..c5c213627 100644 --- a/docs-gen/content/ecosystem/_index.md +++ b/docs-gen/content/ecosystem/_index.md @@ -2,6 +2,7 @@ title: "Ecosystem" date: 2021-07-05T15:12:25+02:00 chapter: true +weight: 40 --- # Tools diff --git a/docs-gen/content/introduction/_index.md b/docs-gen/content/introduction/_index.md index 7b6b35e06..01757c68e 100644 --- a/docs-gen/content/introduction/_index.md +++ b/docs-gen/content/introduction/_index.md @@ -1,6 +1,6 @@ --- title: Introduction -weight: 1 +weight: 10 chapter: true --- diff --git a/docs-gen/content/license/_index.md b/docs-gen/content/license/_index.md new file mode 100644 index 000000000..5f4455a90 --- /dev/null +++ b/docs-gen/content/license/_index.md @@ -0,0 +1,30 @@ +--- +title: License +weight: 30 +chapter: false +--- + + + +## 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, for (academic) research while providing a soli legal framework should 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 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). + +## 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-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 MPL2.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/))). + +In any case we _do_ recommend you to consider sharing generally useful improvements with the community. Not only will you win karma points with the community and gain visibility as an innovation leader in the automotive industry, you will most likely also get more robust software as you will have more users and testers. + +## I changed VSS or added custom signals to the standard catalogue. Do I need to give them away? +No. One important selling point of VSS is, that you can always extend the standard catalogue with your own use case specific signals. There is no obligation to release any added signals or proprietary information to third parties. + +From an MPL2.0 point of view the information of the previous question applies. To be extra sure, put any additions in extra files, and use the layering approach to modify the standard catalogue. This community does not consider deleting elements from the standard catalogue or adding VSS include statements "Modifications" in the sense of clause 1.10 of the MPL2.0. + +As with the tools, we _do_ recommend you to consider sharing generally useful standard catalogue improvements with the community. + + diff --git a/docs-gen/content/rule_set/_index.md b/docs-gen/content/rule_set/_index.md index 507afe804..f5b5243ed 100644 --- a/docs-gen/content/rule_set/_index.md +++ b/docs-gen/content/rule_set/_index.md @@ -1,6 +1,6 @@ --- title: Rule Set -weight: 2 +weight: 20 chapter: true --- From 4319378d4b07dd6a7d9a70cd6d60ec57b761fbdf Mon Sep 17 00:00:00 2001 From: Sebastian Schildt Date: Mon, 21 Mar 2022 15:36:54 +0100 Subject: [PATCH 2/4] Typos and style Signed-off-by: Sebastian Schildt --- docs-gen/content/license/_index.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs-gen/content/license/_index.md b/docs-gen/content/license/_index.md index 5f4455a90..568d689da 100644 --- a/docs-gen/content/license/_index.md +++ b/docs-gen/content/license/_index.md @@ -8,22 +8,22 @@ chapter: false ## 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, for (academic) research while providing a soli 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 while providing a solid legal framework should 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 itself. If in doubt, consult your friendly neighborhood lawyer or IP department. +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. ## 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[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-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 MPL2.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/))). +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/))). In any case we _do_ recommend you to consider sharing generally useful improvements with the community. Not only will you win karma points with the community and gain visibility as an innovation leader in the automotive industry, you will most likely also get more robust software as you will have more users and testers. ## I changed VSS or added custom signals to the standard catalogue. Do I need to give them away? No. One important selling point of VSS is, that you can always extend the standard catalogue with your own use case specific signals. There is no obligation to release any added signals or proprietary information to third parties. -From an MPL2.0 point of view the information of the previous question applies. To be extra sure, put any additions in extra files, and use the layering approach to modify the standard catalogue. This community does not consider deleting elements from the standard catalogue or adding VSS include statements "Modifications" in the sense of clause 1.10 of the MPL2.0. +From an MPL-2.0 point of view the information of the previous question applies. To be extra sure, put any additions in separate files, and use the layering approach to modify the standard catalogue. This community does not consider deleting elements from the standard catalogue or adding VSS `#include` statements "modifications" in the sense of clause 1.10 of the MPL-2.0. As with the tools, we _do_ recommend you to consider sharing generally useful standard catalogue improvements with the community. From cdf4f81a902b1d940be547f57b6e5421aaa60d9c Mon Sep 17 00:00:00 2001 From: Sebastian Schildt Date: Tue, 29 Mar 2022 12:14:44 +0200 Subject: [PATCH 3/4] Add disclaimer Signed-off-by: Sebastian Schildt --- docs-gen/content/license/_index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs-gen/content/license/_index.md b/docs-gen/content/license/_index.md index 568d689da..673200b50 100644 --- a/docs-gen/content/license/_index.md +++ b/docs-gen/content/license/_index.md @@ -5,7 +5,9 @@ chapter: false --- - +{{% notice warning %}} +**DISCLAIMER:** The following information about open source licensing shall not be considered legal advice. For advice on licensing, COVESA suggests that you contact your open source officer or legal counsel. +{{% /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. From 3cd66d1bd7119765c9b670af26f0f5c4ef60d478 Mon Sep 17 00:00:00 2001 From: Sebastian Schildt Date: Tue, 19 Apr 2022 10:26:13 +0200 Subject: [PATCH 4/4] 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/))).