- Telegram and GitLab account
- Account on our Discord server
- Familiarity and compliance with all our Telegram/Discord rules
- Familiarity with the contents of the OrangeFox wiki
- Experience of using GNU/Linux or macOS for some time
- Having the device in hand
- Having a fully working unofficial build
- Having your complete device tree on gitlab
- Be ready to support your own builds, community part, etc
- Not to be afraid of testing, much testing:
Testing new releases is the most important part of maintaining OrangeFox Recovery. Every new release should be fully tested and guaranteed to be working
- You shouldn't have a negative reputation in the Android community
- You shouldn't be rude
- You shouldn't maintain any other recovery and never do it for as long as you remain an official OrangeFox maintainer.
- Hands and brains
- Responsibility
For first you should properly test your unofficial build and fix all known bugs. Our test suite:
- Installing .zip files work
- Installing .img files work
- Backup works
- Backup encryption works (on supported devices - fox_10.0 and lower manifests only):
New backup > padlock icon. Works only if you have selected /data partition.
- Restore works
- The external SD card / OTG (if there is one) can be read
- Backup to external SD card / OTG works
- MIUI OTA works (on supported devices)
- Built-in features work normally
- Settings work and are kept after a reboot
- OrangeFox Recovery can decrypt encrypted data partition without asking for a password if no lockscreen password has been set in the ROM
- Recovery password protection works
- Flashlight works (on supported devices)
- Changing themes and splash work and are kept after reboot:
Changing splashes in some cases uses the mkbootimg binary, so if the splash is not retained after rebooting, it would usually be related to this.
You should fix as many issues as you find. But if you can't fix some issues it won't be a reason for refusing your request for maintainership - but every release you must clearly document all known bugs.
Some advanced functionality is not critical. You can easily disable features that are not working via special build vars.
-
All maintainers should follow the maintainers' guidelines. These include base rules about fstab and more. You should read the guidelines before proceeding.
-
If you meet the requirements listed above, you can message in #apply-for-maintainer on our Discord server to apply for official maintainership. Here is an invitation link - https://discord.com/invite/qbVMJdJbXF
-
You should provide a link to your device tree.
-
You should provide the OrangeFox recovery logs that show the success of your tests, as proof that your builds pass the test suite, and also the install.log and post-install.log files generated when you flashed the OrangeFox zip.
-
Your next step will be to ask for GitLab permissions in order to push your device trees to the OrangeFox gitlab repo. Then you will be allowed to push a Beta release. Only after positive and successful beta testing will you be able to make a Stable release.
We have our own maintainers panel website which will do all the hard work for you.