1 page.title=Android Community 2 @jd:body 3 4 <!-- 5 Copyright 2015 The Android Open Source Project 6 7 Licensed under the Apache License, Version 2.0 (the "License"); 8 you may not use this file except in compliance with the License. 9 You may obtain a copy of the License at 10 11 http://www.apache.org/licenses/LICENSE-2.0 12 13 Unless required by applicable law or agreed to in writing, software 14 distributed under the License is distributed on an "AS IS" BASIS, 15 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 16 See the License for the specific language governing permissions and 17 limitations under the License. 18 --> 19 20 <div id="qv-wrapper"> 21 <div id="qv"> 22 <h2>In this document</h2> 23 <ol id="auto-toc"> 24 </ol> 25 </div> 26 </div> 27 28 <p>Welcome to the Android community!</p> 29 30 <p>The key to any community is communication. Like most projects, Android 31 communicates via mailing lists. Because Android is an extremely large 32 project with many components, we have many discussion forums, each focusing on 33 a different topic. View the available <a href="#open-source-project-discussions">groups</a> 34 and join any that seem interesting to you. You can also discuss Android on 35 <a href="#android-on-irc">IRC</a>.</p> 36 37 <p>If you are a user looking for help with the Android UI or an Android device, 38 details on Android updates or security issues, or how to build applications for 39 Android, see the list of <a href="#resources">resources</a> below.</p> 40 41 <h2 id="resources">Resources</h2> 42 43 <p>This site covers creating custom Android stacks, porting devices and 44 accessories, and meeting compatibility requirements. The Android OS is a Git 45 repository of files and not a single file (.zip/tar/exe/etc.) to download. You 46 can get started with the Android source code by following the instructions on 47 the <a href="downloading.html">Downloading the Source</a> 48 page. For other information about Android, refer to the following resources.</p> 49 50 <div class="wrap"> 51 <div class="col-4"> 52 53 <h4>Using Android</h4> 54 55 <h5>Help centers</h5> 56 <a href="https://support.google.com/android/">General</a><br> 57 <a href="https://support.google.com/pixelphone/">Pixel phones</a><br> 58 <a href="https://support.google.com/nexus/">Nexus phones/tablets</a><br> 59 <a href="https://support.google.com/playedition">Google Play Edition</a><br> 60 <a href="https://support.google.com/androidauto/">Auto</a><br> 61 <a href="https://support.google.com/androidtv/">TV</a><br> 62 <a href="https://support.google.com/androidwear/">Wear</a><br> 63 <a href="https://support.google.com/android/answer/3123680">Apps</a> 64 <p></p> 65 66 <h5>Communities</h5> 67 <a href="#open-source-project-discussions">AOSP communities</a><br> 68 <a href="http://developer.android.com/support.html">Developer communities</a> 69 <p></p> 70 71 <h5>Send feedback</h5> 72 <a href="{@docRoot}source/report-bugs.html">Report AOSP bug</a><br> 73 <a href="https://code.google.com/p/android/issues/entry?template=Feature%20request">Suggest 74 a feature</a> 75 <p></p> 76 77 </div> 78 <div class="col-4"> 79 80 81 <h4>Updates & security</h4> 82 83 <h5>Android releases</h5> 84 <a href="https://www.android.com/history/#/marshmallow">Android history</a><br> 85 <a href="https://www.android.com/versions/nougat-7-0/">Current release</a> 86 <p></p> 87 88 <h5>Device images</h5> 89 <a href="https://developers.google.com/android/images">Nexus and Pixel devices</a><br> 90 <a href="https://support.google.com/android/answer/3094742">Other devices</a> 91 <p></p> 92 93 <h5>Security assistance</h5> 94 <a href="https://www.google.com/safetycenter/everyone/start/">Google Safety Center</a><br> 95 <a href="https://support.google.com/android/answer/6215472">Tips for users</a><br> 96 <a href="http://developer.android.com/training/articles/security-tips.html">Tips 97 for developers</a><br> 98 <a href="{@docRoot}security/index.html">Platform security</a> 99 <p></p> 100 101 <h5>Security announcements</h5> 102 <a href="{@docRoot}security/enhancements/index.html">Release 103 enhancements</a><br> 104 <a href="{@docRoot}security/bulletin/index.html">Bulletins</a> 105 <p></p> 106 107 </div> 108 <div class="col-4"> 109 110 <h4>Getting involved</h4> 111 112 <h5>Developer resources</h5> 113 <a href="http://developer.android.com/">Developer.android.com</a><br> 114 <a href="http://developer.android.com/support.html">Developer support</a><br> 115 <a href="http://android-developers.blogspot.com/">Android developers blog</a><br> 116 <a href="https://developers.google.com/groups/">Google Developer Groups (GDGs)</a> 117 <a href="https://www.android.com/gms/">Google Mobile Services (GMS)</a> 118 <p></p> 119 120 <h5>Training</h5> 121 <a href="https://developer.android.com/training/index.html">Google</a><br> 122 <a href="https://www.udacity.com/google">Udacity</a> 123 124 </div> 125 </div> 126 <div style="clear: both;"></div> 127 128 129 <h2 id="open-source-project-discussions">Open Source Project discussions</h2> 130 <ul> 131 <li> 132 <p><em>android-platform</em>: 133 This list is for general discussion about the Android Open Source Project or 134 the platform technologies.</p> 135 <ul> 136 <li>Subscribe using Google Groups: 137 <a href="https://groups.google.com/forum/?fromgroups#!forum/android-platform"> 138 android-platform</a></li> 139 <li>Subscribe via email: 140 <a href="mailto:android-platform+subscribe (a] googlegroups.com">android-platform 141 </a></li> 142 </ul> 143 </li> 144 <li> 145 <p><em>android-building</em>: 146 Subscribe to this list for discussion and help on building the Android source 147 code, and on the build system. If you've just checked out the source code and 148 have questions about how to turn it into binaries, start here.</p> 149 <ul> 150 <li>Subscribe using Google Groups: 151 <a href="https://groups.google.com/forum/?fromgroups#!forum/android-building"> 152 android-building</a></li> 153 <li>Subscribe via email: 154 <a href="mailto:android-building+subscribe (a] googlegroups.com">android-building 155 </a></li> 156 </ul> 157 </li> 158 <li> 159 <p><em>android-porting</em>: 160 This list is for developers who want to port Android to a new device. If 161 you're wondering how to combine the Android source code with your hardware, 162 this is the right group for you. Discuss here the specifics of porting Android 163 to individual devices, from obtaining toolchains and merging kernel drivers 164 all the way to configuring or modifying applications for your specific 165 configuration.</p> 166 <ul> 167 <li>Subscribe using Google Groups: 168 <a href="https://groups.google.com/forum/?fromgroups#!forum/android-porting"> 169 android-porting</a></li> 170 <li>Subscribe via email: 171 <a href="mailto:android-porting+subscribe (a] googlegroups.com">android-porting</a> 172 </li> 173 </ul> 174 </li> 175 <li> 176 <p><em>android-contrib</em>: 177 This list is for developers who want to contribute code to Android. This is a 178 working list, and is not appropriate for general discussion. We ask that 179 general discussion go to android-platform (and contributors to the Android 180 kernel should go to android-kernel).</p> 181 <ul> 182 <li>Subscribe using Google Groups: 183 <a href="https://groups.google.com/forum/?fromgroups#!forum/android-contrib"> 184 android-contrib</a></li> 185 <li>Subscribe via email: 186 <a href="mailto:android-contrib+subscribe (a] googlegroups.com">android-contrib</a> 187 </li> 188 </ul> 189 </li> 190 <li> 191 <p><em>android-kernel</em>: 192 This list is for developers who want to contribute to the Linux kernel used by 193 Android devices. If you've downloaded the kernel code, know how to compile it, 194 and want to write kernel code to support Android, this is your place. This 195 group is <em>not</em> for user-space topics (see android-platform); people 196 will shake their fingers at you and call you naughty if you ask user-space 197 questions here.</p> 198 <ul> 199 <li>Subscribe using Google Groups: 200 <a href="https://groups.google.com/forum/?fromgroups#!forum/android-kernel"> 201 android-kernel</a></li> 202 <li>Subscribe via email: 203 <a href="mailto:android-kernel+subscribe (a] googlegroups.com">android-kernel</a> 204 </li> 205 </ul> 206 <li> 207 <p><em>android-ota</em>: 208 This list is for developers working on the Android OTA system (the recovery 209 image and the scripts that generate OTAs).</p> 210 <ul> 211 <li>Subscribe using Google Groups: 212 <a href="https://groups.google.com/forum/?fromgroups#!forum/android-ota"> 213 android-ota</a></li> 214 <li>Subscribe via email: 215 <a href="mailto:android-ota+subscribe (a] googlegroups.com">android-ota</a></li> 216 </ul> 217 </li> 218 </ul> 219 220 <h3 id="audience">Audience</h3> 221 <p>These discussion groups are intended for developers working with the Android 222 platform. Everyone is welcome to join in, provided you follow the community 223 policies described below. Our users help each other, and many experts post to 224 these groups, including members of the Open Handset Alliance.</p> 225 <p>No topic is off-limits, provided it relates to Android in some way. However, 226 since these are very busy lists, search the archives before posting your 227 question; you may find your question has already been answered.</p> 228 229 230 <h3 id="getting-the-most-from-our-lists">Getting the Most from Our Lists</h3> 231 <p>Please consider the following before you post to our lists.</p> 232 <ul> 233 <li> 234 <p><em>Read the <a href="#mailing">Charter for our forums.</a></em> This 235 explains the (few) rules and guidelines for our community.</p> 236 </li> 237 <li> 238 <p><em>Search the group archives to see whether your questions have already 239 been discussed.</em> This avoids time-wasting redundant discussions.</p> 240 </li> 241 <li> 242 <p><em>Use a clear, relevant message subject.</em> This helps everyone, both 243 those trying to answer your question as well as those who may be looking for 244 information in the future.</p> 245 </li> 246 <li> 247 <p><em>Give plenty of details in your post.</em> Code or log snippets, 248 pointers to screenshots, and similar details will get better results and make 249 for better discussions. For a great guide to phrasing your questions, read 250 <a href="http://www.catb.org/%7Eesr/faqs/smart-questions.html">How to Ask 251 Questions the Smart Way</a>.</p> 252 </li> 253 </ul> 254 255 <h3 id="mailing">Mailing list rules</h3> 256 <p>We love simplicity and hate restrictions, so we keep our policies minimal. 257 The rules below describe what's expected of subscribers to the Android mailing 258 lists.</h2> 259 260 <ul> 261 <li><em>Please be friendly</em>: Showing courtesy and respect to others is a 262 vital part of the Android culture, and we expect everyone participating in the 263 Android community to join us in accepting nothing less. Being courteous does 264 not mean we can't constructively disagree with each other, but it does mean 265 that we must be polite when we do so. There's never a reason to be 266 antagonistic or dismissive toward anyone; if you think there is, think again 267 before you post. Mobile development is serious business, but it's also a lot 268 of fun. Let's keep it that way. Let's strive to be one of the friendliest 269 communities in all of open source. 270 </li> 271 <li><em>Allowed discussion topics</em>: Most of our groups are for technical 272 discussions of Android or users helping each other. Generally we don't put 273 hard restrictions on the topics discussed in the group: as long as the topic 274 is relevant to Android in some way, it's welcome on our groups. We welcome 275 announcements and discussion of products, libraries, publications, and other 276 interesting Android-related news, but please do not cross-post. Post only to 277 the most relevant group for your message. We even welcome (polite!) discussion 278 of articles and ideas critical of Android—after all, we can't improve if 279 we don't listen. 280 </li> 281 <li><em>Working Lists</em>: Some of our groups are considered "working lists", 282 by which we mean that the list is intended to be used in support of the 283 completion of specific tasks. On these groups, we don't welcome off-topic 284 conversations, and will generally ask you to take general discussions to a 285 different list. Since these are lists where people are trying to get work 286 done, we will be pretty aggressive about keeping the noise level low. We ask 287 that you respect our contributors' time and keep general discussions to 288 appropriate lists. 289 </li> 290 <li><em>Spam</em>: We hate spam almost as passionately as we love courtesy and 291 respect, so we reserve the right to limit discussions that amount to spam. 292 Outright spam will result in the spammer being immediately and permanently 293 banned from the list. 294 </li> 295 </ul> 296 <p>The most important rule is friendliness. Remember: disrespect and rudeness 297 are not welcome in our community under any circumstances. We don't have a 298 formal policy on dealing with troublemakers, and we hope we never need one. 299 That said, we do pledge to do our best to be fair, and we will always try to 300 warn someone before banning him or her.</p> 301 302 <h3 id="contacting">Contacting the moderators</h3> 303 <p>If you see anyone being rude, call them out on it. This is your group too, 304 and you don't have to accept someone else being disrespectful just because it 305 wasn't directed at you. Just remember to be polite and courteous yourself! 306 Don't add fuel to the fire.</p> 307 <p>But if you see an outrageous violation, want to report spam, feel strongly 308 about something, or just want to chat, then contact the mailing list owners. 309 It's what we're here for!</p> 310 311 <h3 id="using-email-with-google-groups">Using email with Google Groups</h3> 312 <p>Instead of using the <a href="https://groups.google.com/">Google groups</a> 313 site, you can use your email client of choice to participate in the mailing 314 lists. To subscribe to a group without using the Google Groups site, use the link 315 under "subscribe via email" in the lists above.</p> 316 <p>To set up how you receive mailing list postings by email:</p> 317 <ol> 318 <li> 319 <p>Sign into the group via the Google Groups site. For example, for the 320 android-platform group you would use 321 <a href="https://groups.google.com/forum/?fromgroups#!forum/android-platform"> 322 https://groups.google.com/forum/?fromgroups#!forum/android-platform</a>.</p> 323 </li> 324 <li> 325 <p>Click "My membership" on the right side.</p> 326 </li> 327 <li> 328 <p>Under "How do you want to read this group?" select one of the email options.</p> 329 </li> 330 </ol> 331 <h2 id="android-on-irc">Android on IRC</h2> 332 <p>Android has a presence on IRC via 333 <a href="http://freenode.net/">freenode</a>. We maintain two official IRC 334 channels on <a href="irc://irc.freenode.net/">irc.freenode.net</a> (access via 335 the web at <a href="http://webchat.freenode.net/">freenode webchat</a>)</p> 336 <ul> 337 <li> 338 <p><a href="irc://irc.freenode.net/android">#android</a> - dedicated to 339 general Android discussion and porting concerns</p> 340 </li> 341 <li> 342 <p><a href="irc://irc.freenode.net/android-dev">#android-dev</a> - dedicated to discussion about writing Android applications</p> 343 </li> 344 </ul> 345 <p>The community also uses several <em>unofficial</em> channels that are not not officially moderated or managed. The Open Handset Alliance does not endorse unofficial channels and there's no warranty express or implied, so use them at your own risk. Here's a list of a few unofficial channels (many more may exist):</p> 346 347 <ul> 348 <li> 349 <p><a href="irc://irc.freenode.net/android-firehose">#android-firehose</a> - 350 displays in real-time the commits to the Android Open Source Project</p> 351 </li> 352 <li> 353 <p><a href="irc://irc.freenode.net/android-fr">#android-fr</a> - pour discuter 354 d'Android en franais</p> 355 </li> 356 <li> 357 <p><a href="irc://irc.freenode.net/android-offtopic">#android-offtopic</a> - 358 for, well, off-topic discussions</p> 359 </li> 360 <li> 361 <p><a href="irc://irc.freenode.net/android-root">#android-root</a> - for 362 discussion related to off-label uses of hardware</p> 363 </li> 364 </ul> 365