AOSPにパッチを送ってみた

Google I/O Extended LT

Transcript

1. AOSPにパッチを送ってみた Kazuki Nara @ AWA Co., Ltd.
2. 自己紹介 Kazuki Nara Android Developer @ AWA Co., Ltd. http://github.com/kazukinr http://www.facebook.com/kazuki.nara
3. How to send Patch Set to AOSP
4. Android Open Source Project https://android.googlesource.com/ https://source.android.com/source/submit-patches 不具合があったら自分で修正できるということ
5. Establishing a Build Environment **For Mac** Disk image must be case-sensitive. # hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size 40g ~/android.dmg
6. Using Repo Initialize $ repo init -u <MANIFEST_URL> -b <BRANCH_NAME> Sync $ repo sync -j8 -c
7. Authentication and CLA Establish a password. https://android.googlesource.com/new-password Contributor License Agreement. https://cla.developers.google.com/about/google-individual
8. Apply your change set Start repo branch. $ repo start <YOUR_BRANCH_NAME> . Make your change and upload $ git add -A $ git commit -a $ repo upload --current-branch .
9. Comment guidelines - Start with a one-line summary (50 characters maximum), followed by a blank line. - Starting on the third line, enter a longer description, which must hard-wrap at 72 characters maximum. - Include a brief note of any assumptions or background information that may be important when another contributor works on this feature next year. - The line starting with “Test” is required.
10. Getting reviewed After you run repo upload, open https://android-review.googlesource.com/ . Add an appropriate reviewer by yourself.
11. Noticed - Test code is important (required in many case). - Presubmit Verify task may be failed. But you don’t have to care. - There are no googlers on weekends. - Using repo is つらい - All English is つらい
12. Incentives - You can fix issues by yourself. - Your name will be displayed as a contributor.
13. Thank you.