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