:::tip This post is for developers and maintainers looking to join Team Bliss. Users can disregard this post. :::
We’re looking for potential maintainers for our next version of BlissRoms, Arcadia!
For this year, we are tightening up our maintainer application process and imposing certain requirements for new maintainers. All new maintainers must meet the following criteria to be accepted, barring any special circumstances. If you do not meet the requirements but believe you have a unique reason to be accepted, please reach out to the administrators at Team Bliss.
- You need to understand English. Many of our internal documentation and tools are written in English. In the past we’ve had some unfortunate instances where maintainers did not understand our directives and caused problems. Therefore, all maintainers must have a reasonable comprehension of English in order to be accepted.
- Your device must be buildable. Please do not apply in the hopes of getting your device maintained by us. That’s not what this program is for.
- Build artifacts must be flashable as-is, without any modification. Unzipping and swapping out the kernel image, editing system files to force certain features to work, etc., are not allowed. Build artifacts should retain their original file name.
- You should be able to use Linux,
git, and Gerrit. In addition, you may have to run Python scripts on machines you are building ROMs on to upload your builds. - You must have a commit history on GitHub for at least 6 months. Note that if you were to try and bypass this requirement by using a commit history alteration tool, we will reject your application and permanently ban you from applying. Please don’t try to cheat the system.
- All device trees (including kernel and vendor) must be public at the time of application, barring any legal problems like DMCA takedown requests. Particularly, if your vendor repository is prone to DMCA takedowns, please reach out to an admin before applying. There are no exceptions for device/kernel trees. Dependencies of the device tree (such as supporting libraries) must be public as well.
- You must release builds once a month, minimum. Please set aside enough time for maintaining your device.
- You must create and maintain an unofficial build for atleast span of 20 days with good stability before applying for official status.
- Should have all major hardware features working. VOLTE, NFC Payments are some of exceptions.
- Lack of activity or if 2 or more releases are skipped then such devices will be dropped from official status without notice.
Also, this year we are dropping the requirement for XDA threads. If you hate interacting with entitled users then you don’t have to! We are also dropping the requirement for support groups on Telegram.
All maintainers and developers of Team Bliss must abide by our ToC. These are really basic conditions, so don’t worry about signing away your soul or anything. These terms mainly deal with common decency to others and regulations like the above to agree to.
If you understand everything above, you may sign up for maintainership here: https://maintainers.blissroms.org/