|
| 1 | +**NOTE:** If you are looking for Glodroid 1.0, please navigate to the |
| 2 | +[master branch](https://github.com/GloDroid/glodroid_manifest/tree/master) |
| 3 | + |
| 4 | +# GloDroid 2.0 |
| 5 | + |
| 6 | +## Ports |
| 7 | + |
| 8 | +At this moment we ported the following devices to GloDroid 2.0: |
| 9 | + |
| 10 | +[PinePhone](https://github.com/GloDroidCommunity/pine64-pinephone) |
| 11 | +[PinePhone-Pro](https://github.com/GloDroidCommunity/pine64-pinephonepro) |
| 12 | +[Raspberry PI 4](https://github.com/GloDroidCommunity/raspberry-pi) |
| 13 | + |
| 14 | +We are currently working on porting the remaining devices / adding new ones. |
| 15 | + |
| 16 | +## Introduction |
| 17 | + |
| 18 | +GloDroid is an Android port that aims to bring both user- and developer-friendly |
| 19 | +experience in using AOSP with a set of single-board computers (SBC), phones and |
| 20 | +other devices. |
| 21 | + |
| 22 | +Version 2.0 brings a mono-repository approach, which gives the following benefits |
| 23 | +compared to the classic manifest-based approach: |
| 24 | + |
| 25 | +1. No need to maintain forks. All necessary delta is stored in the form of patches. |
| 26 | + Benefits: Such patches are a lot easier to maintain. No need to merge/rebase |
| 27 | + fork repositories. Patches are much easier to review by external auditors to |
| 28 | + ensure high project trustworthiness. |
| 29 | + |
| 30 | +2. Atomic changes. |
| 31 | + Benefits: Classic approach may require synchronization of multiple changes in |
| 32 | + different repositories. Gerrit has a "Topic: " field for this purpose, but |
| 33 | + GitHub/GitLab doesn't support such flow. The mono-repository approach makes it possible. |
| 34 | + CI is much easier to integrate. |
| 35 | + |
| 36 | +3. Decouple devices or devices group from each other. |
| 37 | + As time has shown, maintaining all devices under the same manifest is impractical. |
| 38 | + It significantly increases the release cycle since all devices must be validated before |
| 39 | + publishing. Also, some devices may require custom patches on top of AOSP or vendor |
| 40 | + components, while others don't. |
| 41 | + It also allows different people to maintain different devices independently, |
| 42 | + benefiting from using a common code, without waiting for each other. |
0 commit comments