Final product warranty vs MIT licensed FreeRTOS warranty disclaimer
Clash Royale CLAN TAG#URR8PPP
I want to base my embedded project on FreeRTOS, modify the original source code of FreeRTOS (strip some functionality, remove some unused code, increase reliability), write my application specific code and then I want to sell the whole product and give warranty for it.
MIT license for FreeRTOS have disclaimers like: "THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND...". As far as I know I am required to include the MIT license text in my product even when I do not disclose the source code (e.x. in documentation or somewhere like the "About" tab).
So what is the impact of the MIT license terms of FreeRTOS on my final product warranty? Am I allowed to give warranty for my product? (I will modify the original FreeRTOS source code, improve reliability, test and verify it in my application)
There is something like OpenRTOS or even pre-certified SafeRTOS that are targeted specifically for commercial use, but I am not sure if this is the only way for me to be able to provide warranty for my product to my customers and/or apply for some industrial certification in the future.
licensing mit warranty
asked Feb 15 at 13:00
RitchieRitchie
261
add a comment |
I want to base my embedded project on FreeRTOS, modify the original source code of FreeRTOS (strip some functionality, remove some unused code, increase reliability), write my application specific code and then I want to sell the whole product and give warranty for it.
MIT license for FreeRTOS have disclaimers like: "THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND...". As far as I know I am required to include the MIT license text in my product even when I do not disclose the source code (e.x. in documentation or somewhere like the "About" tab).
So what is the impact of the MIT license terms of FreeRTOS on my final product warranty? Am I allowed to give warranty for my product? (I will modify the original FreeRTOS source code, improve reliability, test and verify it in my application)
There is something like OpenRTOS or even pre-certified SafeRTOS that are targeted specifically for commercial use, but I am not sure if this is the only way for me to be able to provide warranty for my product to my customers and/or apply for some industrial certification in the future.
licensing mit warranty
asked Feb 15 at 13:00
RitchieRitchie
261
add a comment |
I want to base my embedded project on FreeRTOS, modify the original source code of FreeRTOS (strip some functionality, remove some unused code, increase reliability), write my application specific code and then I want to sell the whole product and give warranty for it.
MIT license for FreeRTOS have disclaimers like: "THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND...". As far as I know I am required to include the MIT license text in my product even when I do not disclose the source code (e.x. in documentation or somewhere like the "About" tab).
So what is the impact of the MIT license terms of FreeRTOS on my final product warranty? Am I allowed to give warranty for my product? (I will modify the original FreeRTOS source code, improve reliability, test and verify it in my application)
There is something like OpenRTOS or even pre-certified SafeRTOS that are targeted specifically for commercial use, but I am not sure if this is the only way for me to be able to provide warranty for my product to my customers and/or apply for some industrial certification in the future.
licensing mit warranty
asked Feb 15 at 13:00
RitchieRitchie
261
I want to base my embedded project on FreeRTOS, modify the original source code of FreeRTOS (strip some functionality, remove some unused code, increase reliability), write my application specific code and then I want to sell the whole product and give warranty for it.
MIT license for FreeRTOS have disclaimers like: "THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND...". As far as I know I am required to include the MIT license text in my product even when I do not disclose the source code (e.x. in documentation or somewhere like the "About" tab).
So what is the impact of the MIT license terms of FreeRTOS on my final product warranty? Am I allowed to give warranty for my product? (I will modify the original FreeRTOS source code, improve reliability, test and verify it in my application)
There is something like OpenRTOS or even pre-certified SafeRTOS that are targeted specifically for commercial use, but I am not sure if this is the only way for me to be able to provide warranty for my product to my customers and/or apply for some industrial certification in the future.
licensing mit warranty
licensing mit warranty
asked Feb 15 at 13:00
RitchieRitchie
261
asked Feb 15 at 13:00
RitchieRitchie
261
asked Feb 15 at 13:00
RitchieRitchie
261
asked Feb 15 at 13:00
RitchieRitchie
261
asked Feb 15 at 13:00
RitchieRitchie
261
261
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The MIT license requires that you keep all notices intact, and explains that you have not received any warranty from the software's authors.
But this does not prevent you from offering warranties yourself. This is similar to how a car dealership can sell you an extended warranty package that goes beyond the car manufacturer's warranty.
To avoid misunderstandings, it may be best to make it clear that your software is based on FreeRTOS, and show the MIT license incl. warranty disclaimer in that context.
answered Feb 15 at 14:13
amonamon
12.4k11533
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "619"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f7950%2ffinal-product-warranty-vs-mit-licensed-freertos-warranty-disclaimer%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The MIT license requires that you keep all notices intact, and explains that you have not received any warranty from the software's authors.
But this does not prevent you from offering warranties yourself. This is similar to how a car dealership can sell you an extended warranty package that goes beyond the car manufacturer's warranty.
To avoid misunderstandings, it may be best to make it clear that your software is based on FreeRTOS, and show the MIT license incl. warranty disclaimer in that context.
answered Feb 15 at 14:13
amonamon
12.4k11533
add a comment |
The MIT license requires that you keep all notices intact, and explains that you have not received any warranty from the software's authors.
But this does not prevent you from offering warranties yourself. This is similar to how a car dealership can sell you an extended warranty package that goes beyond the car manufacturer's warranty.
To avoid misunderstandings, it may be best to make it clear that your software is based on FreeRTOS, and show the MIT license incl. warranty disclaimer in that context.
answered Feb 15 at 14:13
amonamon
12.4k11533
add a comment |
The MIT license requires that you keep all notices intact, and explains that you have not received any warranty from the software's authors.
But this does not prevent you from offering warranties yourself. This is similar to how a car dealership can sell you an extended warranty package that goes beyond the car manufacturer's warranty.
To avoid misunderstandings, it may be best to make it clear that your software is based on FreeRTOS, and show the MIT license incl. warranty disclaimer in that context.
answered Feb 15 at 14:13
amonamon
12.4k11533
The MIT license requires that you keep all notices intact, and explains that you have not received any warranty from the software's authors.
But this does not prevent you from offering warranties yourself. This is similar to how a car dealership can sell you an extended warranty package that goes beyond the car manufacturer's warranty.
To avoid misunderstandings, it may be best to make it clear that your software is based on FreeRTOS, and show the MIT license incl. warranty disclaimer in that context.
answered Feb 15 at 14:13
amonamon
12.4k11533
answered Feb 15 at 14:13
amonamon
12.4k11533
answered Feb 15 at 14:13
amonamon
12.4k11533
answered Feb 15 at 14:13
amonamon
12.4k11533
12.4k11533
add a comment |
add a comment |
Thanks for contributing an answer to Open Source Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f7950%2ffinal-product-warranty-vs-mit-licensed-freertos-warranty-disclaimer%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown