# Code Of Conduct

## Important rules

Posted by Immanuel Raj on March 29, 2021

## Exceptions **SHOULD** be made only by contacting the administration team.

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119. The maintainers:

• MUST NOT get involved in arguments or resort to insults, or use hateful words, personal attacks or any other verbal or nonverbal action that is considered detrimental towards the creation of a positive environment for the team.

• All theirs device sources on LegionOS-Devices organization. It goes without saying that these SHOULD be fully buildable. Using external repos for build releases aren’t allowed. Exceptions may be open if only it’s absolutely necessary.

• Changelogs for each build. These MUST be user-friendly, simplifying the changes for the average user who aren’t aware of things like Safetynet or color calibration, but would like to know what has changed since the last update.

• MUST test every build before sending an OTA update to users. Each build MUST be thoroughly vetted by the maintainer before it is released, and all hardware and software functionalities MUST be tested before a build is released. Releasing untested builds can (and will) lead to your maintainership being revoked.
• MUST ship the builds monthly . If this is not possible, the reason(s) MUST be sent to the Legion Administration. In the absence of any explanation, a maintainer will be contacted thrice. If there is no satisfactory answer or the administration does not receive a reply, the maintainer will be kicked without any prior warning.

• MUST maintain authorship of git commits that are pushed, this is a mandatory requirement for ALL repositories. Force-pushes are acceptable, but try to keep them to a minimum.

• In the event of any disagreements between maintainers, sort them out via direct messages on Telegram or XDA. Do not take your fights to our chats, approach the administration if you want something sorted out quickly. The same is valid for our public chat. “We don’t do this here”.

• Any features in their device specific packages, eg. configpanel, XiaomiParts, etc., like KCAL, force Camera API2, etc.

Features that are device specific and are available in stock firmware, eg. Alert Slider and Offscreen gestures for some OnePlus Devices, Fingerprint Gestures and MotoActions for Motorola Devices, are allowed.

Dirac Sound or any audio enhancer is allowed, but it MUST be a device’s ROM stock feature, or else it’s not allowed. The same MUST be working fine; otherwise, it can’t be shipped.

• Playground or anything else related to getting Pixel-like features that aren’t available from the ROM sources - only GoogleCamera and ARCore are acceptable.

• Any Google applications that aren’t available from ROM sources - again, only GoogleCamera is acceptable, but please ensure that you use a reliable source and that the device has proper support for them.

• Any stock firmware app. Once again GoogleCamera is acceptable per se, so is the camera app from the stock firmware itself, only, if fully functional.

• MUST NOT enable the Always On Display in case the device has a LCD panel.
• MUST, for kernels, follow our Kernel Guidelines.

• About Magisk, the maintainers MUST NOT:

• Do any heavy software modification that may lead to Magisk working properly. If possible, recommend to users to stop using Magisk if it’s not working properly.

• Do any modifications that may lead to Magisk not work, as per the Kernel Guidelines.

• If you’re a maintainer of an A/B partition or a dynamic partition device, you MUST NOT ship TWRP prebuilt. Instead, the maintainer MUST ship the AOSP Recovery.