Becoming an AOSP contributor
summary
Shows the exact contribution flow: find or file an issue in Issue Tracker, run repo init and repo sync, use Android Studio and Gradle to build and run tests (full build can take ~60 minutes; 24 cores and ~192 GB recommended), make changes, sign the CLA, run pre-commit hooks and repo upload to Gerrit, or edit via cs.android.com web editor or GitHub PRs mirrored by copybara into Gerrit. Jetpack releases every two weeks; 66 external contributors so far.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:11What is AOSP
- 3:03Jetpack
- 4:22Bug Reporting
- 7:43Downloading Code
- 14:42Uploading Code
- 18:04Making Changes
- 20:11Garrett
- 23:25GitHub
- 29:36Questions
related talks
32mYour first AOSP contribution
31mContributing to AOSP
46mHow to contribute to the Android Open Source Project
44mAOSP Developers Birds of a Feather
32mAndroid Open Source: What more can we do with Android?
33mAndroid Open-source repositories 101: Everything you always wanted …
40mThe AOSP BOF Meeting
21mAndroid/AOSP Workflow