Policies

This guide covers the expectations and processes for Apertis developers wishing to make contributions to the Apertis project and the wider open source ecosystem. These policies should be followed by all developers, including core and third party contributors. A checklist is provided in conjunction with these policies to aid contributors. TL;DR Do you want to quickly submit some changes to an Apertis component? Have you tried to submit your changes upstream first? [Read More]

Apertis hosts its own package subset on the Apertis GitLab instance. On successful completion of the CI pipeline these are uploaded to Collabora’s Open Build Service (OBS) instance where the packages are formally built and hosted for Apertis. Packages Guidelines The package set is distributed in several groups: target, development, sdk, hmi, helper-libs. Those groups are merged in a single repository, and split in what distribution names repository components (target, development, sdk, hmi, helper-libs). [Read More]

Apertis and its direct downstreams are intended as baseline distributions for further product development, as such it’s important to have a clear definition of what downstreams further down the chain can expect in terms of releases and support cycles in order to understand how to best use them in their product development cycles. The release cycles of Apertis and its direct downstreams are split up in two big phases: a development phase, containing various development releases followed by a product phase which contains various stable point releases. [Read More]

Apertis aims to accomplish the following goals with it’s licensing: Ensure that all the software shipped in Apertis is open source or at least freely distributable, so that downstreams are entitled to use, modify and redistribute work derived from our deliverables. Ensure that Apertis images targeting devices (such as HMI and fixedfunction), are not subject to licensing constraints that may conflict with the regulatory requirements of some intended use cases. In order to reach these goals, the below assumptions are made: [Read More]

The Apertis Logo The Apertis logo consists of 2 elements: The Symbol The Wordmark In most situations the Symbol and the Workmark should remain connected and used as a whole. In isolated cases, where suitable, it is permitted that the Symbol can be separated from the Workmark, likewise the Wordmark can be removed from the Symbol. When using the Symbol and Wordmark togther, please ensure that you maintain the spacing /layout between them as below. [Read More]

This text documents what you can expect from the Apertis community online and at events and, in turn, what we expect from you. We believe that people generally mean well. Excepting strong evidence to the contrary, we ask that you do the same. We favour communication over confrontation. Most issues that arise during day-to-day contribution to any software project and at events can be resolved by communication between the affected parties. [Read More]

Who are we? “apertis.org” is managed and maintained by Collabora Limited. We are an IT global consultancy company, specialized in open source software. Our main office is in The Platinum Building, St John’s Innovation Park, Cambridge, United Kingdom. Our registered company number is 05513718 and our ICO registration number is ZA229843. If you have any queries in connection with how we use your data, you can contact us by emailing data@collabora. [Read More]

The text of the Apertis website is copyrighted (automatically, under the Berne Convention) by Apertis editors and contributors and is formally licensed under Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA) unless explicitly stated otherwise. The licenses that the Apertis website uses grant free access to our content in the same sense that free software is licensed freely. Apertis website content can be copied, modified, and redistributed if and only if the copied version is made available on the same terms to others and acknowledgment of the authors of the Apertis website article used is included (a link back to the article is generally thought to satisfy the attribution requirement; see below for more details). [Read More]