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