At the moment, it's clear to me (being in the middle of it) that Google is a major bottleneck when it comes to Android as an Open-Source project.
As such, you can expect that we'll focus our energy primarily on things that only Google can do, and much less on things that can also be done by anyone in the community (assuming skills/time, of course), so that the desired end result can be reached as quickly as possible. Putting together nightly builds, opening and maintaining a wiki (... and helping direct traffic on the mailing lists, which you've been doing) are aspects where the community as a whole can get involved right now without help from Google. We're also looking for contributors to sanitize the behavior of the open-source tree on dream, or to decouple some unfortunate proprietary dependencies that still exist in the source tree. As time goes and more of the Google-only tasks get completed, more such options will open. Feel free to have the discussions about nightly builds on this group for now, as we don't currently have a more appropriate one to have build-related discussions on (we need one, I'm on it). JBQ PS: keep an eye on http://www.android.com/branding.html about the right way to use some of the brands. On Sun, Apr 5, 2009 at 10:49 AM, Mark Murphy <[email protected]> wrote: > > Jean-Baptiste Queru wrote: >> It might make sense for someone to start working on this right now, >> independently from Google or the core Android team, in a way that'd be >> decoupled from the Google infrastructure. >> >> This'd for sure relieve some resource pressure for the people who are >> working on the Android open-sourcing process at Google, as we're >> already overloaded and can't really take on additional tasks at the >> moment. > > I wasn't so much looking for the core Android team to do the work, > unless it wanted to. I am never quite clear what things Google wants > done where. > > If anyone is interested in putting together a federated build system, > for the purpose of generating nightly builds of key Android branches > (e.g., cupcake), either reply here or contact me off-list. If I can get > a team together, we'll work on getting a system up and running. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > Android App Developer Training: http://commonsware.com/training.html > > > > -- Jean-Baptiste M. "JBQ" Queru Android Engineer, 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 warning. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
