All right, there seems to be a bit of confusion around the mailing
lists for the Android Open-Source Project, so I'll try to clarify
things a little bit. Hopefully this'll help people better understand
which list(s) to read, and which list to post to.
Fundamentally, besides the maintainers and administrators, there are 2
kinds of actors in the ecosystem of the Android Open-Source Project:
-the readers: those are people who download the source code from the
Android Open-Source Project and use it for their own purposes. One of
the things that can be done is to port the entire Android platform to
new devices and ship those devices to consumers, but there are plenty
of other uses cases (from studying the security model to try to adapt
bits of Android to run in other environments).
-the writers: those are people who intend to contribute patches to the
Android Open-Source Project, so that those patches can benefit
everyone who uses the source code from the Android Open-Source
Project. With the way the Android Open-Source Project is set up, those
patches are considered for inclusion into Google's internal code
repository (so they need to comply to Google's and other relevant
coding practices and be accepted by Google engineers), and only become
part of official releases if they make it through Google's scrutiny.
At the moment, there are 3 mailing lists set up to publicly discuss
the various aspects of the Android Open-Source Project:
-If you're a reader, you should be posting to the android-porting mailing list.
-If you're a writer, you should be posting to the android-kernel
mailing list (if you intend to contribute to the kernel) or to the
android-platform mailing list (f you intend to contribute to
As a side note, if you're not sure which mailing list to post to,
please don't cross-post. If you happen to post to the wrong mailing
list, people there will direct you to the best mailing list.
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further