The provisions set forth in this document are non-negotiable and binding.
Non-compliance will result in the immediate revocation of maintainership rights, without the need for further discussion.
https://cdn.evolution-x.org.This Code of Conduct is established as a guiding legal framework to ensure the continuity, stability, and integrity of the ROM, and to regulate appropriate conduct among all associated individuals.
| Act 1: The usage of advertising-based link shorteners is strictly prohibited.
Act 1.1: Maintainers are permitted to solicit voluntary donations as recognition for their efforts.
| Act 2: Community builds must not be released for devices with an active official maintainer.
Act 2.1: This prohibition may be waived by the existing official maintainer.
Act 2.2: If a device is unofficially maintained, one may assume official maintainership.
Community maintainers may be temporarily appointed should the official maintainer fail to publish a build for a given time.
| Act 1: Maintainers shall uphold and maintain a reputable standing within the community.
| Act 2: Maintainers shall refrain from disrespectful behavior.
| Act 3: Maintainers shall sustain a positive rapport with fellow maintainers.
| Act 4: Maintainers shall protect the integrity of the ROM. Constructive criticism is welcomed, but malicious defamation is not permitted.
| Act 5: Maintainers are advised not to concurrently maintain more than two ROM projects.
Act 5.1: This restriction may be waived by decision of a Core Member.
| Act 1: Maintainers must not alter the ROM source code when compiling official builds. Any violation will result in immediate revocation.
Act 1.1: Source code modification is permissible only with explicit authorization, and only to ensure device compatibility—not for feature additions.
| Act 2: Device trees must not interfere with the ROM's core features.
| Act 3: Kernels must comply with their respective open-source licenses.
| Act 4: Maintainers may not intentionally block or disable any functionality in official builds.
| Act 5: Official builds must not include any form of privilege escalation (e.g., root solutions such as patched boot images or KernelSU).
Act 5.1: These may be provided separately, but never embedded within the official ROM.
| Act 6: Maintainers must possess the physical device they maintain.
Act 6.1: For device series sharing the same SoC, ownership of a single model is sufficient. In such cases, the maintainer must have the builds validated by testers prior to release.
| Act 1: Maintainers must upload builds and await CDN synchronization before submitting pull requests or public releases.
Act 1.1: RC/Beta/Alpha/Testing releases may be published via Google Drive or any other mean, but will be excluded from OTA updates.
Act 1.2: Only flashable ROM.zip packages are permitted on the Project's CDN.
| Act 2: Maintainers reserve the right to withdraw a published build at any time.
| Act 3: Maintainers must personally test each build before release. Untested builds will result in a warning; repeated offenses will lead to removal.
| Act 4: OTA pull requests must follow the naming convention: Device_Codename: MM/DD/YYYY Update, or OTA: Add Device_Codename as Official Device for new entries.
| Act 5: Changelogs must be appropriate and free from offensive or inappropriate content.
| Act 6: Official builds must be signed with the Project's designated keys.
Act 6.1: From EvolutionX 11.x - Android 16, Maintainer MUST use EvolutionX's CI/CD server to build. Maintainer MUST NOT release a self-built zip.
| Act 7: Builds must be released at minimum every two months unless justified. Prolonged inactivity without notification may lead to revocation.
| Act 1: Maintainers must host their device trees within the official device organization.
| Act 1.1: Maintainers should host their vendor trees within the official device organization. If not possible, other providers such as gitlab can be used.
| Act 2: All device, vendor and kernel trees must be publicly accessible. Private repositories are prohibited.
| Act 3: Commit authorship must be preserved. Force-pushes are permissible.
| Act 4: The following build environment declarations are mandatory for official builds:
export EVO_BUILD_TYPE=OFFICIAL # in build scripts
EVO_BUILD_TYPE := OFFICIAL # in the Makefile
| Act 5: Proprietary applications should not be included within device trees or as dependencies. Inclusion of binary files is acceptable.
Act 5.1: Exceptions such as Dolby may be permitted with prior approval.
Act 5.2: Act 5 may be overridden with consent from Project Members.
| Act 6: Device trees must not contain copyright-infringing blobs.
| Act 1: Maintainers must have an adequate command of the English language.
| Act 2: All user-facing communications must be conducted in English.
| Act 1: Forwarding of messages from the Maintainers Group is forbidden without explicit consent from the original sender.
| Act 2: Maintainers must safeguard project signing keys. Key leakage will result in immediate and irreversible expulsion.
| Act 3: Maintainers must possess an active Discord account and join the official Discord server.
| Act 4: Maintainers must be reachable via Discord.
Act 4.1: Immediate responses are not expected, but timely replies are appreciated.
| Act 1: Maintainers have the right to be treated with dignity and respect.
| Act 2: Maintainers have the right to vote and express opinions within the Project.
| Act 3: Maintainers may resign from the Project for personal reasons.
Act 3.1: While not mandatory, it is considered courteous to notify the team of one's departure.
| Act 1: Maintainers should moderate at least one thread in the official Discord device forum.
| Act 2: Promotion of other ROMs within device-specific channels is strictly forbidden.
| Act 3: Piracy, illegal content, and encouragement of unlawful behavior are prohibited.
| Act 4: Personal disputes must not result in user bans. Offenses will be subject to warnings.
| Act 5: Use of Telegram for personal groups is allowed, but the Project does not support Telegram officially.
| Act 1: Maintainers may create device groups using the format EvolutionX{codename} or any approved variation. Community maintainers are excluded from this right.
| Act 2: Device groups must use Haruka Aya Bot as the sole management bot.
| Act 3: Device groups must not host content related to other ROMs or serve personal projects.
| Act 4: Group administrators must not be listed among the Project’s blocklisted individuals.
| Act 5: Additional bots may be added, provided they do not violate any provisions of this Code.
| Act 6: Promotion of alternative ROMs is strictly forbidden.
| Act 7: Piracy or any encouragement of illegal behavior is prohibited.
| Act 1: Fedbans must be issued only with valid justification and supporting evidence.
| Act 2: Fedbans must not be issued due to personal disputes.
| Act 3: Abuse of fedban privileges will result in immediate revocation of such access.
| Act 1: CDN accesses must not be abused (e.g., deletion of files). Violations will result in instant revocation.
| Act 2: Only ROM.zip or images.img files may be uploaded to the Project's CDN.
| Act 3: Maintainers must await CDN synchronization prior to submitting a pull request.
| Act 1: Use of monetized services such as short ads or Pling links is strictly prohibited.
By accepting the role of maintainer, you hereby acknowledge and agree to comply with the above provisions in full.
For clarification or concerns regarding this Code, please contact the team on Discord.