-
-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update licensing page to allow for Bliss OS team to have initial cont…
…act requests
- Loading branch information
1 parent
1c05cfc
commit 955605c
Showing
1 changed file
with
7 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -107,9 +107,9 @@ <h2 class="display-3">Licensing</h2> | |
| <div class="row"> | ||
| <div class="col-md-12"> | ||
| <h2>Purchasing and Sales Information</h2> | ||
| <p>To purchase a Bliss OS license, <a href="index.html#contact">contact us</a> with your request.</p> | ||
| <p>To purchase a Bliss OS license, <a href="mailto:[email protected]?subject=Bliss%20OS%20License%20Pricing">contact us</a> with your request.</p> | ||
| <br> | ||
| <p>For further information and assistance about Bliss OS licensing, contact our sales; see https://navotpala.tech for contact details.</p><br> | ||
| <p>For further information and assistance about Bliss OS licensing, contact us or see our website for further details.</p><br> | ||
| </div> | ||
| </div> | ||
| <div class="row"> | ||
|
|
@@ -119,7 +119,7 @@ <h2 contenteditable="true">Third-Party Code in Bliss OS</h2> | |
| <p> Bliss OS inherits the same Apache v2 licensing that AOSP uses for most of the components, while many of the other components like Android-Generic Project use GPL-2.0 license. <br>For product use, we do not include proprietary components like Google Apps, Native-Bridge, and widevine. Some features and toolkits like our rebranding toolkit would require additional licensing to be obtained by the customer. <br></p> | ||
| <br> | ||
| <p> - <a href="https://source.android.com/docs/setup/about/licenses" target="_BLANK">AOSP Licenses</a> - <a href="https://github.com/BlissRoms-x86/manifest/blob/arcadia-x86/License" target="_BLANK">Bliss OS License</a> - <a href="https://github.com/BlissRoms/platform_manifest/blob/typhoon/LICENSE" target="_BLANK">Bliss ROM License</a> - <a href="https://github.com/android-generic/vendor_ag/blob/unified/LICENSE.md" target="_BLANK">Android-Generic Project License</a> - <a href="https://github.com/boringdroid/boringdroid/blob/master/LICENSE" target="_BLANK">Boringdroid License</a> - <br> | ||
| <br> For Bliss OS/<a href="https://bliss-bass.blisscolabs.dev" target="_BLANK">Bass OS</a> source, we do catalog the repos used and their licenses. You can view that <a href="https://github.com/BlissRoms-x86/oss-licenses" target="_BLANK"> here</a>.</p><br> | ||
| <br> For Bliss OS/<a href="https://bliss-bass.github.io" target="_BLANK">Bass OS</a> source, we do catalog the repos used and their licenses. You can view that <a href="https://github.com/BlissRoms-x86/oss-licenses" target="_BLANK"> here</a>.</p><br> | ||
| </div> | ||
| </div> | ||
| <div class="row"> | ||
|
|
@@ -130,7 +130,7 @@ <h4>Q: Is Bliss OS suitable for individuals?</h4> | |
| </div> | ||
| <div class="col-md-6 p-3"> | ||
| <h4>Q: Does Bliss OS include proprietary software?</h4> | ||
| <p> A: Yes. Our GMS/Gapps releases include proprietary software, and are intended for individuals only, while our FOSS and Vanilla builds might include some proprietary parts as well. <br><br>Proprietary redistributables in all Bliss OS public builds: <br>- linux-firmware blobs <br>- Proprietary linux drivers (broadcom-wl for example) <br>- some media codecs (for decoding H.264/HEVC) <br>- ARM Translation Library (Houdini or libndk-translation) <br>- Widevine L3 <br><br>Extra proprietary redistributables in BlissOS Gapps builds include Google Play Serivces & Google Play Store.</p> | ||
| <p> A: Yes. Our GMS/Gapps releases include proprietary software, and are intended for individuals only, while our FOSS and Vanilla builds might include some proprietary parts as well. <br><br>Proprietary redistributables in all Bliss OS public builds: <br>- linux-firmware blobs <br>- Proprietary linux drivers (broadcom-wl for example) <br>- some media codecs (for decoding H.264/HEVC) <br>- ARM Translation Library (Houdini or libndk-translation) <br>- Widevine L3 <br><br>Extra proprietary redistributables in BlissOS Gapps builds include Google Play Services & Google Play Store.</p> | ||
| </div> | ||
| </div> | ||
| <div class="row"> | ||
|
|
@@ -140,7 +140,7 @@ <h4>Q: Is Bliss OS suitable for companies?</h4> | |
| </div> | ||
| <div class="col-md-6 p-3"> | ||
| <h4>Q: Can my company use Bliss OS with Gapps as-is?</h4> | ||
| <p> A: No. The Bliss OS versions that include Google Play Store, native-bridge, or widevine are not fit for commercial use and are not meant to be included in products as they contain proprietary features and services that typically require per-product licensing through Google, Intel, or others. We do however release public Vanilla and FOSS (bare-bones) builds that are suitable for company use and do not contain any proprietary resources.<br><br>Most of those proprietary licenses are not eligible for use in generic operating-system setups. Some require the device to pass certification programs that is only meant for single device certifications. <br>If you have a product and you would like to explore what the CTS certification process includes, please feel free to <a href="mailto:[email protected]?subject=Development Contract Inquiry">contact us</a></p> | ||
| <p> A: No. The Bliss OS versions that include Google Play Store, native-bridge, or widevine are not fit for commercial use and are not meant to be included in products as they contain proprietary features and services that typically require per-product licensing through Google, Intel, or others. We do however release public Vanilla and FOSS (bare-bones) builds that are suitable for company use and do not contain any proprietary resources.<br><br>Most of those proprietary licenses are not eligible for use in generic operating-system setups. Some require the device to pass certification programs that are only meant for single device certifications. <br>If you have a product and you would like to explore what the CTS certification process includes, please feel free to <a href="mailto:[email protected]?subject=Development Contract Inquiry">contact us</a></p> | ||
| </div> | ||
| </div> | ||
| <div class="row"> | ||
|
|
@@ -281,7 +281,7 @@ <h4>Our Logos</h4> | |
| <div class="row"> | ||
| <div class="col-md-12"> | ||
| <h4 class="mb-3 display-5"> Third-Party Repositories & Packages </h4> | ||
| <p> We recommend all software included in Bliss OS releases be inspected and agreed upon through official involvement with <a target="_blank" href="https://blisslabs.org">BlissLabs</a> in order to ensure user privacy and security guidelnes. All third-party software must also agree to present source code for us to inspect as well. Failure to do this may void any support contracts or retail contracts. </p> | ||
| <p> We recommend all software included in Bliss OS releases be inspected and agreed upon through official involvement with <a target="_blank" href="https://blisslabs.org">BlissLabs</a> in order to ensure user privacy and security guidelines. All third-party software must also agree to present source code for us to inspect as well. Failure to do this may void any support contracts or retail contracts. </p> | ||
| </div> | ||
| </div> | ||
| </div> | ||
|
|
@@ -292,7 +292,7 @@ <h4 class="mb-3 display-5"> Third-Party Repositories & Packages </h4> | |
| <div class="row"> | ||
| <div class="mx-auto p-4 col-md-6"> | ||
| <h2 class="mb-4">Get in touch</h2> | ||
| <p> We love to hear from potential partners and offer a way for you to talk directly with the team by emailing us Whether you’re an existing partner or want to explore offering BlissOS, we look forward to hearing from you. </p> | ||
| <p> We love to hear from potential partners and offer a way for you to talk directly with the team by emailing us. Whether you’re an existing partner or want to explore offering BlissOS, we look forward to hearing from you. </p> | ||
| <!-- <p class="mb-0 lead" > <a href="mailto:[email protected],[email protected]">[email protected]</a> </p> --> | ||
| </div> | ||
| <div class="mx-auto p-4 col-md-6"> | ||
|
|
||