-
-
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.
- Loading branch information
1 parent
4eeb133
commit da2dd26
Showing
1 changed file
with
30 additions
and
5 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 |
|---|---|---|
|
|
@@ -90,11 +90,36 @@ <h2 class="mb-4 display-5">Licensing Information</h2> | |
| <div class="py-5" style="" id="oems"> | ||
| <div class="container"> | ||
| <div class="row"> | ||
| <div class="col-md-12 text-center"> | ||
| <div class="col-md-12 "> | ||
| <h2 class="display-3">Licensing</h2> | ||
| <p>Bliss OS is available under different licensing options designed to accommodate the needs of our various users: </p> | ||
| <ul> | ||
| <li>Bliss OS licensed under <b>commercial</b> licenses is appropriate for development of proprietary/commercial software where you do not want to share any source code with third parties or otherwise cannot comply with the terms of the GNU GPL version 3. </li> | ||
| <li>Bliss OS licensed under the <b>GNU General Public License (GPL) version 3</b> is appropriate for the development of Bliss OS applications provided you can comply with the terms and conditions of the GNU GPL version 3. </li> | ||
| </ul> | ||
| <br> | ||
| <p style="">Bliss OS also contains third-party code that is licensed under specific open-source licenses from the original authors (See <b>Third-Party Code in Bliss OS</b> below). </p> | ||
| <p style=""><b>Note</b>: For open-source licensed Bliss OS, some specific parts (Bass OS addons) are available under the GNU General Public License (GPL). For commercial licensees, all Bass OS addons are available under commercial Bliss OS licenses.</p> | ||
| <p style=""><b><i>Bliss OS documentation</i></b> is available under commercial licenses from Navotpala Tech (Bliss Co-Labs), and under the terms of the GNU Free Documentation License (FDL) version 1.3, as published by the Free Software Foundation.</p> | ||
| <p style="">Educational licenses are available for students and educators in qualified educational institutions or universities.</p><br> | ||
| </div> | ||
| </div> | ||
| <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> | ||
| <br> | ||
| <p>For further information and assistance about Bliss OS licensing, contact our sales; see https://navotpala.tech for contact details.</p><br> | ||
| </div> | ||
| </div> | ||
| <div class="row"> | ||
| <div class="col-md-12"> | ||
| <h2 contenteditable="true">Third-Party Code in Bliss OS</h2> | ||
| <p>The following documents the open-source licenses used in different parts of Bliss OS:</p> | ||
| <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 source, we do catalog all 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> | ||
| <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> | ||
| </div> | ||
| </div> | ||
| <div class="row"> | ||
|
|
@@ -111,17 +136,17 @@ <h4>Q: Does Bliss OS include proprietary software?</h4> | |
| <div class="row"> | ||
| <div class="col-md-6 p-3"> | ||
| <h4>Q: Is Bliss OS suitable for companies?</h4> | ||
| <p> A: Yes, but not all builds. We produce minimal vanilla and FOSS Bliss OS, and Bliss-Bass (bare-bones with added configurability options), and AOSP builds with basic x86/x86_64 PC hardware support. Both the AOSP and Bliss-Bass builds come with no proprietary software included, and those are available to test with. While those builds are very basic, they do include much of what would be needed to base a product off of. If your product requires no additional changes on top of what is released to the public, then you are free to use it at no cost.<br>If your product requires Google Apps, ARM/ARM64 Native-Bridge, or Widevine, due to licensing restrictions, we suggest that you <a href="mailto:[email protected]?subject=Development Contract Inquiry">reach out</a> and we can help you look into alternative options using open-source solutions. <br><br>You can find our production ready test builds:<br> <a href="https://sourceforge.net/projects/blissos-dev/files/Android-Generic/PC/aosp/" target="_BLANK">AOSP bare-bones test builds</a><br> <a href="https://sourceforge.net/projects/blissos-dev/files/BlissBass/" target="_BLANK">Bliss-Bass test builds</a></p> | ||
| <p> A: Yes, but not all builds. We produce minimal vanilla and FOSS Bliss OS, and Bliss-Bliss (bare-bones with added configurability options), and AOSP builds with basic x86/x86_64 PC hardware support. Both the AOSP and Bliss-Bliss builds come with no proprietary software included, and those are available to test with. While those builds are very basic, they do include much of what would be needed to base a product off of. If your product requires no additional changes on top of what is released to the public, then you are free to use it at no cost.<br>If your product requires Google Apps, ARM/ARM64 Native-Bridge, or Widevine, due to licensing restrictions, we suggest that you <a href="mailto:[email protected]?subject=Development Contract Inquiry">reach out</a> and we can help you look into alternative options using open-source solutions. <br><br>You can find our production ready test builds:<br> <a href="https://sourceforge.net/projects/blissos-dev/files/Android-Generic/PC/aosp/" target="_BLANK">AOSP bare-bones test builds</a><br> <a href="https://sourceforge.net/projects/blissos-dev/files/BlissBliss/" target="_BLANK">Bliss-Bliss test builds</a></p> | ||
| </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 or 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 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></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 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> | ||
| </div> | ||
| </div> | ||
| <div class="row"> | ||
| <div class="col-md-6 p-3"> | ||
| <h4>Q: Can my company use Bliss OS source-code in a product?</h4> | ||
| <p style=""> A: Yes, This applies to Android-PC (AOSP), Bliss OS, Bliss OS Go or Bliss Bass sources. <b>If you are an individual developer, a startup, or represent some other business enterprise and you are interested in using our sources, the open-source licenses we maintain allow you to use the source at no cost as long as you use it: A) as-is, B) you contribute any changes made back to the source, or C) produce the full source to the public independently.</b> If you would like to use our source and make changes to it that you do not plan on releasing as open-source, we request you contact us to work out a <b>per-device licensing agreement</b> and/or setup a <a href="mailto:[email protected]?subject=Development Contract Inquiry">development contract</a> for branding, optimizations and specific needs.</p> | ||
| <p style=""> A: Yes, This applies to Android-PC (AOSP), Bliss OS, Bliss OS Go or Bliss Bliss sources. <b>If you are an individual developer, a startup, or represent some other business enterprise and you are interested in using our sources, the open-source licenses we maintain allow you to use the source at no cost as long as you use it: A) as-is, B) you contribute any changes made back to the source, or C) produce the full source to the public independently.</b> If you would like to use our source and make changes to it that you do not plan on releasing as open-source, we request you contact us to work out a <b>per-device licensing agreement</b> and/or setup a <a href="mailto:[email protected]?subject=Development Contract Inquiry">development contract</a> for branding, optimizations and specific needs.</p> | ||
| </div> | ||
| <div class="col-md-6 p-3"> | ||
| <h4> Q: Does my company have to release any changes made to the collective source code of Bliss OS? </h4> | ||
|
|
||