Last active
April 28, 2017 16:14
-
-
Save bhush9/b58ecf0ea659cbf0b717377be07ab51c to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Technical points: | |
| - rootfs | |
| - initrd | |
| - android build | |
| - single libhybris v/s libhybris per device | |
| some legal points from StsKeeps | |
| > also one thing you guys might want to keep in mind is contribution agreements, not copyright assignment | |
| > but basically 'i own this work that i'm submitting' | |
| > as any possibly infringements due to some idiot using NDA'ed or other EULA'ed materials to do something might get applied to you as a unlimited partnership | |
| > and you'd be responsible due to distributing | |
| - license to use for docs | |
| organizational: | |
| - we need mailing list |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| - rootfs | |
| - We will use the ubuntu xenial rootfs generated by live-build configuration at https://github.com/halium/rootfs-builder | |
| - http://bshah.in/halium/halium-rootfs.tar.gz | |
| - Its minimal rootfs with systemd init and android-tools-adbd included | |
| - packages included : http://bshah.in/halium/halium-rootfs-packages | |
| - initrd | |
| - for stage0 bootstrap we will use ubuntu initrd and once we have android container running we will look into hybris-boot or other simpler initrd | |
| - We can't directly specify root=/dev/xxx as that is not how android bootloader would work | |
| - Once we have android source tree forked, we will build packages for | |
| - android-headers | |
| - libhybris | |
| - bshah to build and include the in the rootfs | |
| - We discussed if we shold use one libhybris for all devices or have one libhybris package per device | |
| - For reference/sandbox rootfs we want to go with "one libhybris to rule all" | |
| - If distribution wants the seperate libhybris and rootfs per device they can have it as distributions will not use reference packaging anyway | |
| - We might revisit this in future but for now that is it for simplicity | |
| - We discussed need for contribution agreements and also need to have code of conduct | |
| - We agreed upon license to use for the docs - CC-BY-SA 3.0 | |
| - We will need the general mailing list as communication channel and will look into how to set it up | |
| - We agree that we can reach stage 0 milestone of development outline in 2 week or so. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment