-
-
Notifications
You must be signed in to change notification settings - Fork 11
/
Copy pathlicensing.html
460 lines (457 loc) · 30.2 KB
/
licensing.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- PAGE settings -->
<link rel="icon" href="favicon.ico">
<title>Bliss OS</title>
<meta name="description" content="Open Source OS for PC's, based on AOSP">
<meta name="keywords" content="blissroms, bliss, os, x86, aosp, android, rom, teambliss">
<!-- CSS dependencies -->
<link rel="stylesheet" href="css/style.css">
<link rel="stylesheet" href="neon.css">
<link rel="stylesheet" href="css/animations.css">
<link rel="stylesheet" href="css/buttonstyle.css">
<link rel="stylesheet" href="css/table.css">
<link href="https://fonts.googleapis.com/css?family=VT323" rel="stylesheet" type="text/css">
<!-- Script: Make my navbar transparent when the document is scrolled to top -->
<script src="js/navbar-ontop.js"></script>
<!-- Script: Animated entrance -->
<script src="js/animate-in.js"></script>
<link rel="stylesheet" href="css/chat.css">
<!-- <script data-ad-client="ca-pub-7639560510014441" async="" src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script> -->
</head>
<body>
<access origin="mailto://*" launch-external="true">
<!-- Navbar -->
<div class="container">
<nav class="navbar navbar-expand-lg fixed-top bg-primary navbar-dark">
<div class="container">
<a class="navbar-brand" style="text-align: center" href="index.html"><img src="images/bliss_icon_light.png" class="d-inline-block align-top" style="width: 40%" alt="logo"></a>
<a class="navbar-brand" href="index.html">
<span style="font-weight: 500">Bliss OS</span>
</a>
<button class="navbar-toggler navbar-toggler-right" type="button" data-toggle="collapse" data-target="#navbar2SupportedContent" aria-controls="navbar2SupportedContent" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse text-center justify-content-end" id="navbar2SupportedContent">
<ul class="navbar-nav me-auto mb-2 mb-lg-0">
<li class="nav-item mx-2">
<a class="nav-link" href="index.html#features">Features</a>
</li>
<li class="nav-item mx-2">
<a class="nav-link" href="index.html#team">Team</a>
</li>
<li class="nav-item mx-2">
<a class="nav-link" href="https://blisslabs.org" target="_blank">Org</a>
</li>
<li class="nav-item mx-2">
<a class="nav-link" href="index.html#documentation">Docs</a>
</li>
<li class="nav-item mx-2">
<a class="nav-link" target="_blank" href="https://blog.blissos.org">Blog</a>
</li>
<li class="nav-item mx-2">
<a class="nav-link" href="licensing.html">Licensing</a>
</li>
</ul>
<a class="btn navbar-btn mx-2 btn-secondary shadow" href="index.html#download">Download</a>
</div>
</div>
</nav>
</div>
<!-- Cover -->
<section class="section-fade-out-white pt-5 text-light main_background">
<div class="container py-5 mt-5" style="top: 15vh; position: relative">
<div class="row">
<div class="col-md-6">
<h2 class="mb-4 display-5">Licensing Information</h2>
<p> Bliss OS brings the best of what Android has to offer to your projects. </p>
<p class="pb-3"> With a wide variety of compatibility for devices built in, we can help to bring the experience your customers demand, and the features they deserve. </p>
<a href="#oems" class="btn btn-lg btn-primary" contenteditable="true">Learn More</a>
</div>
<div class="col-md-5 align-self-center">
<img class="img-fluid mx-auto" style="
border: 1rem solid transparent;
border-radius: 1rem;
box-shadow: 0 25px 50px -12px rgb(0 0 0 / 0.4);
background: linear-gradient(to left, #191919, #292929)
border-box;
" src="images/bliss15_about.jpg">
</div>
</div>
</div>
</section>
<div class="py-5" style="" id="oems">
<div class="container">
<div class="row">
<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="mailto:social@blissos.org?subject=Bliss%20OS%20License%20Pricing">contact us</a> with your request.</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">
<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/<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">
<h3 class="display-4 text-center">FAQ</h3>
<div class="col-md-6 p-3">
<h4>Q: Is Bliss OS suitable for individuals?</h4>
<p> A: Yes, Bliss OS public releases are designed to be used as a daily replacement for Windows, ChromeOS, Mac OS or Linux and work is consistently being done to improve the User Experience.<br><br>We offer users multiple types of builds to help fit their needs:<br>- <b>Gapps Builds</b>: Comes with Google Play Store, Widevine and ARM compatibility layer options<br>- <b>FOSS Builds</b>: Comes with open-source alternatives for Google Play Store and media alternatives. <br>- <b>Vanilla Builds</b>: Comes with no added apps and services. Basic media support. </p>
</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 Services & Google Play Store.</p>
</div>
</div>
<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:social@blissos.org?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://bliss-bass.blisscolabs.dev" target="_BLANK">Bliss-Bass 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 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:social@blissos.org?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 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:social@blissos.org?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>
<p> A: This all depends on where the changes in the source were made, as many repos in the project retain a different OSS Licenses, there are different requirements per repo. If you are unsure if your company needs to release the source for any of the changes made, please feel free to contact us.<br><br>Another thing to pay attention to is if the tools being used require the end product or alterations to be released. Some Apache 2.0 licensed projects allow for that requirement to be made. Some versions of Android-Generic Project also have similar licensing requirements. We have put together a toolkit to help identify these types of licenses within the source. You can find that <a href="https://github.com/android-generic/agpm-auto-oss-license-documentation" target="_BLANK">here</a>.</p>
</div>
</div>
<div class="row">
<div class="col-md-12 pt-5 text-center">
<h1>Licensing Questions?</h1>
<h5>We try to offer a wide variety of licensing options that cater to organizations of all sizes.</h5>
<p class="mb-3">If you are not sure if you need a license, or just have some questions on our licensing options, please feel free to contact us. We love helping out others find the best way to contribute back to the source.</p>
<a class="btn btn-outline-primary mt-3" href="mailto:social@blissos.org?subject=Licensing Inquiry">Contact Us</a>
</div>
</div>
</div>
</div>
<section class="my-5" id="resources">
<div class="container main_grid" style="
display: grid;
grid-template-columns: 1fr 2fr 3fr 2fr;
grid-template-rows: 1fr;
gap: 0px 0px;
align-items: center;
">
<div class="">
<h4 class="display-5">Resources</h4>
<p> We offer OEM toolkits, custom options for automatic installation, as well as endless other customization options. </p>
</div>
<div class="w-75">
<img class="img-fluid position-relative" style="
border: 1rem solid transparent;
border-radius: 1rem;
box-shadow: 0 25px 50px -12px rgb(0 0 0 / 0.4);
background: linear-gradient(to left, #191919, #292929) border-box;
right: -70%;
z-index: -1;
" src="images/bliss15_multi_left.jpg">
</div>
<div class="">
<img class="img-fluid position-relative" style="
border: 1rem solid transparent;
border-radius: 1rem;
box-shadow: 0 25px 50px -12px rgb(0 0 0 / 0.4);
background: linear-gradient(to left, #191919, #292929) border-box;
z-index: 1000;
" src="images/bliss15_multi_menu.jpg">
</div>
<div class="w-75">
<img class="img-fluid position-relative" style="
border: 1rem solid transparent;
border-radius: 1rem;
box-shadow: 0 25px 50px -12px rgb(0 0 0 / 0.4);
background: linear-gradient(to left, #191919, #292929) border-box;
right: 50%;
z-index: -1;
" src="images/bliss15_about.jpg">
</div>
</div>
</section>
<div class="py-3" id="oems">
<div class="container">
<div class="row">
<div class="col-md-6 p-3">
<h4>System Settings</h4>
<p> We are available for contract work to help you with any specific device tuning and development in order to achieve the targets you require. </p>
</div>
<div class="col-md-6 p-3">
<h4>OTA Updates & LTS Contracts</h4>
<p> We offer OTA updates for a variety of hardware and offer Long Term Service contracts as well. </p>
</div>
</div>
</div>
</div>
<div class="py-3 mb-5">
<div class="container">
<div class="row">
<div class="col-md-6">
<a href="android-generic.github.io="><img class="w-75 rounded" src="images/ag_website.png"></a>
</div>
<div class="col-md-6 p-4">
<h4>Advanced Prototyping Tools</h4>
<p> We develop a few different tools and one of them is Android Generic Project (AG), a rapid prototyping toolkit for Android on PC (x86) hardware. <br>
<b>AG uses GNU General Public License v2.0 </b>
</p>
<a class="btn btn-primary text-right" href="https://android-generic.github.io" target="_blank">Learn More</a>
</div>
</div>
</div>
</div>
<div class="py-5 bg-secondary">
<div class="container">
<div class="row">
<div class="col-md-12">
<h1 class="text-center">Looking to use Bliss OS in a product?</h1>
<div class="row">
<div class="col-md-4 col-lg-3 order-2 order-md-1 p-0"> <img class="img-fluid d-block" src="images/np/android-business-mixed2.svg" height="240rem" width="240rem"> </div>
<div class="d-flex flex-column justify-content-center p-3 col-md-8 offset-lg-1 align-items-start order-1 order-md-2">
<h3 style="">We clean up nicely :)</h3>
<p class="mb-3">Navotpala Tech (our corporate sponsors), maintains a couple projecs based on Bliss OS and Android-Generic Project called <b>Bass OS </b>and<b> Bass Toolkit</b>, and they build off of what we have in order to add new features, remove any unlicensable assets/technologies, dial things in for enterprise/product use and simplify the product development process. </p>
<a class="btn btn-primary" href="https://navotpala.tech" target="_blank"><b><b>Checkout Their Projects Here</b></b></a>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="container my-5">
<div class="row">
<div class="col-md-12 text-center">
<h3 class="display-3">Branding</h3>
<p> If you decide to include our work in your project or product, we would appreciate you including a link to <a href="https://blissos.org" target="_blank">BlissLabs</a> as well as the projects you used. We have included a branding guide below for your convenience if you also choose to represent our branding in your project. </p>
</div>
</div>
<div class="py-3">
<div class="container">
<div class="row">
<div class="col-md-6 p-4">
<h4>Visual Branding Guide</h4>
<p> We offer a loose branding guide for our partners to follow. Feel free to contact us with any questions you may have </p>
<a class="btn btn-primary" href="images/Bliss_visual_system.pdf" target="_blank">Branding Guide</a>
</div>
<div class="col-md-6 p-4">
<h4>Our Logos</h4>
<p> We have a few assets for our partners to use in their designs. Please see below for a few options and feel free to contact us for more if you are in need. </p>
</div>
</div>
</div>
</div>
<div class="py-5">
<div class="container">
<div class="row">
<div class="col-6 p-3">
<img class="w-75" src="images/BlissIcon.png">
</div>
<div class="col-6 p-3">
<img class="w-75" src="images/Lotus_white.png">
</div>
</div>
</div>
</div>
<!-- Article style section -->
<!-- Features -->
<!-- Features -->
<!-- Carousel reviews -->
<!-- Call to action -->
<!-- START OF BLISSLABS -->
<div class="mt-5 text-center">
<div class="container">
<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 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>
</div>
</div>
<div class="mt-5">
<div class="container">
<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 class="mb-0 lead" > <a href="mailto:social@blissos.org,info@blisscolabs.dev">info@blisscolabs.dev</a> </p> -->
</div>
<div class="mx-auto p-4 col-md-6">
<h2 class="mb-4">Send us a message</h2>
<form action="mailto:social@blissos.org" method="post" enctype="text/plain">
<div class="form-group">
<input type="text" class="form-control" name="name" placeholder="Name" style="opacity: 100%" required="required">
</div>
<div class="form-group">
<input type="email" class="form-control" name="mail" placeholder="Email" style="opacity: 100%" required="required">
</div>
<div class="form-group">
<textarea class="form-control" rows="3" name="comment" placeholder="Your message"></textarea>
</div>
<button type="submit" class="btn btn-primary" value="Send"> Send </button>
</form>
</div>
</div>
</div>
</div>
<!-- END OF BLISSLABS -->
<!-- Footer -->
<div class="py-3 bg-dark">
<div class="container">
<div class="row">
<div class="col-lg-3 col-6 p-3">
<h5><b>Socials</b></h5>
<ul class="list-unstyled text-primary">
<li class="text-primary">
<a target="_blank" href="https://t.me/Team_Bliss_Community" class="text-info">BlissROMs Telegram</a>
</li>
<li class="text-primary">
<a target="_blank" href="https://matrix.to/#/#blissos:matrix.org" class="text-info">Bliss OS Matrix</a>
</li>
<li>
<a target="_blank" href="https://t.me/blissx86" class="text-info">Bliss OS Telegram</a>
</li>
<li>
<a target="_blank" href="https://www.facebook.com/BlissFamilyOfROMs/" class="text-info">Bliss Facebook</a>
</li>
<li>
<a target="_blank" href="https://twitter.com/blissos_org" class="text-info">Bliss OS Twitter</a>
</li>
<li>
<a target="_blank" href="https://www.linkedin.com/company/stayblissful" class="text-info">Bliss LinkedIn</a>
</li>
</ul>
</div>
<div class="col-lg-3 col-6 p-3">
<h5><b>Sources</b></h5>
<ul class="list-unstyled">
<li>
<a href="https://review.blissroms.com" class="text-info">BlissROMs Gerrit Review</a>
</li>
<li>
<a href="https://review-x86.blissroms.com">Bliss OS (x86) Gerrit Review</a>
</li>
<li>
<a href="https://github.com/BlissRoms" class="text-info">BlissROMs GitHub</a>
</li>
<li>
<a href="https://github.com/BlissRoms-Devices" style="" class="text-info">BlissROMs-Devices GitHub</a>
</li>
<li>
<a href="https://github.com/BlissRoms-x86" class="text-info">Bliss OS GitHub</a>
</li>
<li>
<a href="https://github.com/BlissRoms-pine64" class="text-info">BlissROMs-PINE64 GitHub</a>
</li>
<li>
<a href="https://gitlab.com/android-generic/vendor_android-generic" class="text-info">Android-Generic GitLab</a>
</li>
</ul>
</div>
<div class="col-lg-3 col-6 p-3">
<h5>Subreddits</h5>
<ul class="list-unstyled">
<li>
<a href="https://www.reddit.com/r/BlissRoms" class="text-info">BlissROMs</a>
</li>
<li>
<a href="https://www.reddit.com/r/BlissOS" class="text-info">Bliss OS</a>
</li>
<li>
<a href="https://www.reddit.com/r/TeamBliss" class="text-info">TeamBliss</a>
</li>
</ul>
</div>
<div class="col-lg-3 col-md-3 p-3">
<h5><b>Follow us</b></h5>
<div class="row">
<div class="col-md-12 d-flex align-items-center my-2 justify-content-center">
<a href="https://www.facebook.com/BlissFamilyOfROMs/" target="_blank">
<i class="mr-2 text-light fa-2x"><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-facebook"><path d="M18 2h-3a5 5 0 0 0-5 5v3H7v4h3v8h4v-8h3l1-4h-4V7a1 1 0 0 1 1-1h3z"/></svg></i>
</a>
<a href="https://instagram.com/blissos_org" target="_blank">
<i class="mx-2 text-light fa-2x"><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-instagram"><rect width="20" height="20" x="2" y="2" rx="5" ry="5"/><path d="M16 11.37A4 4 0 1 1 12.63 8 4 4 0 0 1 16 11.37z"/><line x1="17.5" x2="17.51" y1="6.5" y2="6.5"/></svg></i>
</a>
<a href="https://github.com/blissroms-x86" target="_blank">
<i class="mx-2 text-light fa-2x"><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-github"><path d="M15 22v-4a4.8 4.8 0 0 0-1-3.5c3 0 6-2 6-5.5.08-1.25-.27-2.48-1-3.5.28-1.15.28-2.35 0-3.5 0 0-1 0-3 1.5-2.64-.5-5.36-.5-8 0C6 2 5 2 5 2c-.3 1.15-.3 2.35 0 3.5A5.403 5.403 0 0 0 4 9c0 3.5 3 5.5 6 5.5-.39.49-.68 1.05-.85 1.65-.17.6-.22 1.23-.15 1.85v4"/><path d="M9 18c-4.51 2-5-2-7-2"/></svg></i>
</a>
<a href="https://twitter.com/blissos_org" target="_blank">
<i class="ml-2 text-light fa-2x"><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-twitter"><path d="M22 4s-.7 2.1-2 3.4c1.6 10-9.4 17.3-18 11.6 2.2.1 4.4-.6 6-2C3 15.5.5 9.6 3 5c2.2 2.6 5.6 4.1 9 4-.9-4.2 4-6.6 7-3.8 1.1 0 3-1.2 3-1.2z"/></svg></i>
</a>
<a href="https://discord.com/invite/F9n5gbdNy2" target="_blank">
<i class="ml-2 text-light fa-2x"><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-message-square-quote"><path d="M21 15a2 2 0 0 1-2 2H7l-4 4V5a2 2 0 0 1 2-2h14a2 2 0 0 1 2 2z"/><path d="M8 12a2 2 0 0 0 2-2V8H8"/><path d="M14 12a2 2 0 0 0 2-2V8h-2"/></svg></i>
</a>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="py-3 bg-dark">
<div class="container">
<div class="row">
<div class="col-md-12 text-center d-md-flex justify-content-between align-items-center">
<ul class="nav d-flex justify-content-center">
<li class="nav-item">
<a class="nav-link active" href="images/Bliss_visual_system.pdf" target="_blank">Brand</a>
</li>
<li class="nav-item">
<a class="nav-link" href="licensing.html">Licensing & Info</a>
</li>
<li class="nav-item">
<a class="nav-link" href="https://blisslabs.org">BlissLabs</a>
</li>
</ul>
<p class="mb-0 py-1">© 2024 BlissLabs. All rights reserved</p>
</div>
</div>
</div>
</div>
<!-- JavaScript dependencies -->
<!-- <script src="js/mainani.js" type="text/javascript"></script> -->
<script src="https://code.jquery.com/jquery-3.3.1.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.3/umd/popper.min.js" integrity="sha384-ZMP7rVo3mIykV+2+9J3UJ46jBk0WLaUAdn689aCwoqbBJiSnjAK/l8WvCWPIPm49" crossorigin="anonymous"></script>
<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/js/bootstrap.min.js" integrity="sha384-ChfqqxuZUCnJSK3+MXmPNIyE6ZbWh2IMqE241rYiqJxyMiZ6OW/JmZQ5stwEULTy" crossorigin="anonymous"></script>
<!-- Script: Smooth scrolling between anchors in the same page -->
<script src="js/smooth-scroll.js"></script>
<!-- <script src="https://bfintal.github.io/Counter-Up/jquery.counterup.min.js"></script> -->
<script src="js/counter.js"></script>
<script src="js/conditionize.js"></script>
<script src="js/adv.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/gsap/1.19.1/TweenMax.min.js"></script>
<!-- <script src="js/chat.js"></script> -->
</access>
</body>
</html>