Since then, there've been highs, lows, successes, failures, and just
about everything in between.
I'd like to use this milestone to ask you what you think about AOSP:
tell us what you've liked for the entire year, what you've disliked
for the entire year, what used to be bad but has improved, what used
to be good but has regressed, what you'd like to see continue, what
you'd like to see change, how AOSP compares to other open-source
projects, how AOSP compares to other phone platforms.
Also, feel free to tell us more about you. Are you working with AOSP
as a hobby or as part of your job? Are you mostly interested in the
system-level aspects (kernel, C library), dalvik, the core Android
framework, the applications? Are you working for an OEM or an ODM,
directly or as a contractor/partner? Are you mostly interested in AOSP
on phones, or on other hardware?
I understand that some people might want to keep their replies
private. In that case, feel free to send them to me directly, I won't
share them in public.
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
For me it's about getting back into programming. I had some basic programming experience but never really dove deep into a single language or discipline. Now I use any chance I get to tinker and learn at any level; apps, framework, Linux undersystem. I could care less about where the platform goes from here on or about legal issues, etc, because just a single branch clone is enough to put a lot of work into and we all know there's plenty of room for improvement.
As for the future, it's not really up to Android, but I'd like it if the platform eventually gave birth to an open device that's a multi-communication device with support for hardware upgrades (down to the processor) and powered by Android, ofcourse. Just imagine, community created and supported drivers for everything...
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to android-platfo...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en
* A thought occured to me as I typed that: if new features need to be secret, what about a public wishlist of things Google engineers want to see but haven't done yet and don't expect to have time for. Someone in the community might see an opportunity to contribute that they didn't know existed. Just a random thought.
Is it? Last time i checked you could still repo sync and the code you downloaded was still free. That the code Google has in their servers hasn't been released under a free licence (and that's up to them, since they really don't owe it to anybody to release their improvements), but that doesn't change that the code that currently constitutes aosp is still indeed free and open source.
On Nov 12, 2009 1:47 PM, "Disconnect" <dc.dis...@gmail.com> wrote:
..and a year later, its back to being closed source?
On Thu, Oct 22, 2009 at 10:00 AM, Jean-Baptiste Queru <j...@android.com> wrote: > > A year ago, AOSP...--
You received this message because you are subscribed to the Google Groups "android-platform" group....For more options, visit this group at http://groups.google.com/group/android-platform?hl=.
A year ago, AOSP turned to life with a set of initial contributions
from Google and its partners, with millions of line of previously
unreleased code suddenly becoming available for the world to use and