The other problem is that code comes out of Google to the main repository, so we need to know what's being done in Google to avoid duplicating effort, conflicting solutions, etc.
Al. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stoyan Damov Sent: 27 March 2009 19:23 To: [email protected] Subject: [android-discuss] Re: Andorid's marketing campaign ... JBQ, I and others have said it many times -- we speak to *you* (Android engineers) because there's no one else to speak to. It seems that Google does not want to speak to us, or hear us. I'm sick of this "in my role, as an Android engineer I can't ...". How do we get to someone who *can*? On Fri, Mar 27, 2009 at 9:18 PM, Jean-Baptiste Queru <[email protected]> wrote: > > I should have quoted the part that's relevant to my position as a > software engineer. > > "I want to hear WHAT is it that you're thinking, how do you THINK > should be implemented, etc." > > JBQ > > On Fri, Mar 27, 2009 at 12:10 PM, Disconnect <[email protected]> wrote: >> If you reread his message, you'll see he is looking for more planning >> information to come OUT of google. Not for info on how to push more info IN. >> >> And - as you are well aware - he's not the only one. >> >> On Fri, Mar 27, 2009 at 3:08 PM, Jean-Baptiste Queru >> <[email protected]> >> wrote: >>> >>> Pick a specific area in which you'd like to contribute (with 20+ >>> million lines of code, you've got to be precise), have a look at the >>> existing code, put together a high-level outline of the way you'd >>> "attack" your problem, and head over to android-platform or >>> android-kernel to discuss the details. >>> >>> JBQ >>> >>> On Fri, Mar 27, 2009 at 11:56 AM, Stoyan Damov >>> <[email protected]> >>> wrote: >>> > >>> > On Fri, Mar 27, 2009 at 8:38 PM, Incognito <[email protected]> >>> > wrote: >>> >> >>> >> >>> >> Wow the iPhone rocks. It is really our job to create great apps >>> >> for the g1. >>> > >>> > But you can't, and that's why we're having this discussion. >>> > On a side note, if Android is a community project, and we're part >>> > of the community I *don't* want to hear from Google "we're working >>> > on this". >>> > I want to hear WHAT is it that you're thinking, how do you THINK >>> > should be implemented, etc. >>> > We need a roadmap, we want to participate in SOME way in your decisions. >>> > Is Android (C) Google? If not, we should have *some* vote on what >>> > should be done, and how. >>> > >>> > Cheers >>> > >>> > > >>> > >>> >>> >>> >>> -- >>> 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. >>> >>> >> >> >> > >> > > > > -- > 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 -~----------~----~----~----~------~----~------~--~---
