Prusa Connect Created by Prusa Research a.s. (https://www.prusa3d.com) This project is licensed under OCL v1.1 + Micro v1 + NoSaaS v1 + SWAtt v1 (Open Community License v1.1 + Micro Business v1 + Software Specific Use v1 + Software Attribution v1). The full texts follow: the Open Community License v1.1 and the three add-on conditions it is distributed with. The license, its add-ons and examples of how they apply are published at https://github.com/OpenCommunityLicence/OpenCommunityLicence ================================================================================ Open Community License (OCL v1.1) OCL pertains to intellectual property applied in licensor‘s product (licensed item - hardware and/or software) and/or its components which is distributed as is under OCL, including copyright, registered design or design patent, and (utility) patent. All licensor‘s copyrights, designs, and patents as far as relevant to products and/or its components under OCL are COMMUNITY-OPEN, as the aim of OCL is to allow open access to relevant community including the essential right, the right-to-repair, by giving users complete freedom of use, copy, modification, and hack, while promoting a fair competition by securing intellectual property rights to prevent vendor lock-in and patent trolling. NOTE that any component provided under a license incompatible with OCL and as such included in or distributed alongside the product and/or its component remains unaffected by OCL. Also NOTE that OCL does not override imperative exceptions and limitations under applicable law. As a non-commercial END USER YOU MAY use, copy, modify, hack the product and/or its components as you wish! YOU SHOULD support the community by sharing your creations and modifications. If you distribute your creations, modifications, or any such derivatives YOU MUST do so under OCL allowing other community members to do everything that YOU MAY. This does not concern your creations and modifications that are not derived from the product and/or its components. As a commercial BUSINESS USER YOU MAY use the product and modify it to your use case solely for your internal business use (including internal production). YOU MUST NOT copy or in any way replicate the product and/or its components and/or its derivatives for any commercial purpose excluding your internal right-to-repair without obtaining a separate business license or repair license. Licensor‘s products and/or its components under OCL MUST NOT BE subject to any systematic or automated text and/or data mining or other text and/or data collection activity in relation to the product without explicit permission. Licensor may expand conditions of OCL distribution only by including add-on conditions (one or more) defined and provided in OCL repository. Any distribution under OCL requires clear reference to an OCL version and applicable add-on conditions and their version. Any allowed distribution of derivatives must retain applicable add-on conditions. To promote ease of understanding of OCL licensor may keep and update a database of products and/or its components licensed under OCL and good practice. For practical examples of how this license applies, see the examples/ directory. For available add-on conditions, see the addons/ directory. ================================================================================ Open Community License - Micro Business (Micro v1) Micro serves solely as an add-on condition for OCL distribution and is effective only if specifically referenced in said OCL distribution (OCL v* + Micro v1 or Open Community License v* + Micro Business v1). Such add-on only adds further binding license condition without any change or invalidation of any part of OCL. As a commercial BUSINESS USER YOU MUST NOT use the product and/or its components and/or its derivatives in any way if your annual gross revenue for the last twelve months exceeds the value of one-million EURO without obtaining a separate business license. The revenue includes licensee as well as any affiliates that, directly or indirectly, control licensee or are controlled by licensee or are under common control with licensee. ================================================================================ Open Community License - Software Specific Use (NoSaaS v1) NoSaaS serves solely as an add-on condition for OCL distribution and is effective only if specifically referenced in said OCL distribution (OCL v* + NoSaaS v1 or Open Community License v* + Software Specific Use v1). Such add-on only adds further binding license condition without any change or invalidation of any part of OCL. As a commercial BUSINESS USER YOU MUST NOT use the product and/or its components and/or its derivatives for providing and/or offering its functionality, features, execution and/or APIs to any third party or as a part of any service offering to any third party, which includes especially but not exclusively hosting, deployment or running the product and/or its components and/or its derivatives as a Software-as-a-Service, Platform-as-a-Service, Infrastructure-as-a-Service, and/or Managed Service where any third party interacts directly or indirectly with a functionality of the product and/or its components and/or its derivatives, as well as exposing the product and/or its components and/or its derivatives via network-accessible APIs or endpoints to any third party. ================================================================================ Open Community License - Software Attribution (SWAtt v1) SWAtt serves solely as an add-on condition for OCL distribution and is effective only if specifically referenced in said OCL distribution (OCL v* + SWAtt v1 or Open Community License v* + Software Attribution v1). Such add-on only adds further binding license condition without any change or invalidation of any part of OCL. As a non-commercial END USER If you distribute your creations, modifications, or any such derivatives YOU MUST reasonably and in a common manner retain and represent in your distribution the identification of the creator/s of the product and/or its components and its derivatives on which your derivative is based. YOU MUST represent said identification of the creator/s visibly for the user in the user interface of your derivative and in the source code of your derivative. User interface representation may be omitted ONLY if your derivative lacks user interface, and therefore does not provide software means for data input and/or output readout by a user. Representation SHOULD include "built on [identification of creator/s]". In respect to practical representation limitations YOU MUST retain and represent AT LEAST the identification of the creator/s of the product and/or its components, and if applicable the identification of the creator/s of the last derivative, on which your derivative is based.