build.md

@@ -9,6 +9,30 @@ ATTENTION : This process will only work on **case-sensitive** filesystems!
 * Linux: work on Ubuntu and CentOS
 >>>
 
+# Devices builds
+
+## Definitions: Custom vs Unofficial vs Official
+
+A **custom build** is a build that is using most of /e/ source code to generate a new ROM. This can be modified in any manner by the developer, for any purpose.
+
+An **unofficial /e/ build** is a build from /e/ source code to generate the /e/ ROM for a new, not yet supported, device. It’s not been approved and officially and included to the list of official /e/ ROMs
+
+An **official /e/ build** is an unofficial build from /e/ source code that has reached a sufficient level of quality and has been validated. It is published as an official build on /e/ websites.
+
+## Requirements for differents builds:
+
+* **Custom builds**: if the source code has been modified and if the ROM is redistributed, we have several requirements:
+    * any reference to /e/, including “/e/”, and our logo must be removed from the build
+    * the redistribution must not let people think that it is /e/. Must change name and possibly say it’s been fork from /e/
+    * calls to our OTA server infrastructure must be changed or removed
+    * Custom ROMs can be built on /e/ servers only for exceptional reasons (special development…).
+* **Unofficial /e/ builds**: source code can be modified only to reach full support on the target device. /e/ features, list of installed apps etc. shouldn’t be modified. Unofficial builds can be published on /e/ website at a specific place with warnings and a list of what works/what doesn’t work. It doesn’t have nightly builds nor OTA updates.
+* **Official /e/ builds** : the level of quality must have reached our conditions. It must have an official maintainer. Official builds have nightly builds and can be updated OTA. Source code have to be hosted on our GitLab instance, or on trusted sources (LineageOS GitHub group, AOSP).
+
+Any question about this? [contact us](https://e.foundation/contact/)
+
+## How to build?
+
 ## 1. Install docker
 
 If you have not already done so, [install docker](https://docs.docker.com/install/)