Actions
Issue #2110
openMinimal Replicant branding, was: Rebrand as Replicant
Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
08/25/2020
Due date:
% Done:
0%
Estimated time:
Resolution:
Device:
Unknown
Grant:
Porting Replicant to Android 9 (NLnet Foundation)
Type of work:
Build system integration, Unknown
Updated by Denis 'GNUtoo' Carikli over 3 years ago
While I started to do that and rename vendor/lineage to Replicant, Putti had very valid concerns with the fact that this created way too much side effects.
So the idea is to keep vendor/lineage, symlinks users facing scripts from it in vendor/replicant and brand the rest as usual (add the Replicant name, logo, etc), but do it in a way that is easiest to rebase for future Replicant versions .
Updated by Denis 'GNUtoo' Carikli over 3 years ago
- Grant set to Porting Replicant to Android 9 (NLnet Foundation)
Updated by Denis 'GNUtoo' Carikli over 3 years ago
- Subject changed from Rebrand as Replicant to Minimal Replicant branding, was: Rebrand as Replicant
Updated by _I3^ RELATIVISM about 3 years ago
- Type of work System administration, Unknown added
Updated by Denis 'GNUtoo' Carikli about 3 years ago
- Type of work Build system integration added
- Type of work deleted (
System administration)
The images needs to visually look like Replicant images (with Replicant being the name of the distribution, they probably need a splash screen with the Replicant logo, and so on).
It also needs to be done in a way that makes it easy for other people to fork Replicant if needed (like to support devices we might not want to support in Replicant)
Updated by Denis 'GNUtoo' Carikli over 2 years ago
Status:
| Feature | Status |
| Replicant default wallpapers | DONE |
| Replicant wallpaper chooser | |
| Replicant boot animation | WIP |
| Replicant version in settings |
Actions