| bigbiff bigbiff | 5be3b23 | 2016-07-19 21:02:25 -0400 | [diff] [blame] | 1 | --- |
| 2 | layout: post |
| bigbiff bigbiff | 597e2a4 | 2018-10-16 15:52:07 -0400 | [diff] [blame^] | 3 | title: "How Do I Become a TWRP Maintainer?" |
| bigbiff bigbiff | 5be3b23 | 2016-07-19 21:02:25 -0400 | [diff] [blame] | 4 | --- |
| 5 | |
| 6 | <div class='page-heading'>How Do I Become a TWRP Maintainer?</div> |
| 7 | <hr /> |
| 8 | <ol> |
| 9 | <li>Device Tree</li> |
| 10 | You need to have a device tree. You need to figure this out on your own. You can review other trees for help and modify it as necessary. You can use <a href="https://github.com/Tasssadar/libbootimg">libbootimg</a> to get the needed values from stock recovery to populate BoardConfig.mk. |
| lj50036 | 3dbddac | 2016-12-28 08:55:39 -0600 | [diff] [blame] | 11 | <li>Push your tree to Github.com.</li> |
| bigbiff bigbiff | 5be3b23 | 2016-07-19 21:02:25 -0400 | [diff] [blame] | 12 | We need to be able to fork your tree to our TeamWin repository. We can then add it to our Gerrit.twrp.me and Jenkins.twrp.me instance for building. If you want to be an active maintainer, we can give you +2 rights to merge new updates directly to our repository at Github. |
| 13 | <li>Verify your device tree works</li> |
| bigbiff bigbiff | 6d815b2 | 2017-10-15 20:23:57 -0400 | [diff] [blame] | 14 | Make sure your image works as intended. You can use <a href="http://tinyw.in/XCN3">this</a> for a functional list to test your device. |
| bigbiff bigbiff | 5be3b23 | 2016-07-19 21:02:25 -0400 | [diff] [blame] | 15 | <li>Use our <a href="https://twrp.me/contactus/">Contact Us</a> page to send your repository to use for official inclusion at twrp.me.</li> |