Would be great if Jean (JBQ) or a head engineer at Android could be the technical spokesman for the product like spam engineer Matt Cutts does for SEO - attending conferences and blogging openly about updates, best practices, etc.
This would take the load off the engineers as a whole to focus on the work and complete the software while at the same time being inclusive by getting a face and the communication out there. My 2 cents. Michael Martin Google And Blog - GPhone Android News http://www.googleandblog.com/ On Jul 12, 8:41 pm, "Muthu Ramadoss" <[EMAIL PROTECTED]> wrote: > >> Furthermore I'd probably lose my job over it, and I'd like to think that > > I contribute enough to Android that losing my job wouldn't be beneficial to > Android as a whole (and it certainly wouldn't be beneficial to me, in more > than one way). > > Heard Google is pretty tight on employee blogs. You have done a great thing > of engaging the community again. We would like you to be with Android and > address our concerns as much as possible so it benefits Android as a whole. > So please tell us only what you can, and we'll understand. > > > > > > On Sun, Jul 13, 2008 at 5:09 AM, JBQ <[EMAIL PROTECTED]> wrote: > > > I'm really not allowed to say anything concrete about the possibility > > of an updated SDK at any point in the future. I'm left with two > > options: say nothing at all, or try to say as much as I think can get > > away with about other subjects, even if that doesn't answer the SDK > > question, and even if I sometimes have to answer in an oblique way. > > > Saying things I'm strictly not allowed to say wouldn't accomplish > > anything positive: saying isn't doing, and even if I said something > > there wouldn't be an SDK available. Furthermore I'd probably lose my > > job over it, and I'd like to think that I contribute enough to Android > > that losing my job wouldn't be beneficial to Android as a whole (and > > it certainly wouldn't be beneficial to me, in more than one way). > > > I'll try to answer a few of the questions that popped up, or to > > clarify some of my earlier comments... > > > About accelerating the untying or un-gagging: I don't know if there's > > much to be done. We've been struggling in those restraints for months, > > and no matter how much we try they don't seem to ever get any looser > > (but at least they don't seem to be getting any tighter either). I'm > > afraid that everyone (both engineers on the inside and developers on > > the outside) will have to be patient. > > > About the advocates: I have no reason to believe that at any point > > they got gagged more than they already were. Overwhelmed, certainly. > > Burnt out, possibly. I certainly don't envy their position, and my > > hat's off to them. > > > "We rant because we care" (slightly misquoted): very well said. I'll > > reply "we listen and reply because we care". And in the end we all end > > up within a heated discussion between people who care for exactly the > > same thing, which is truly bizarre and sad. > > > JBQ (Android Engineer) > > > On Jul 11, 9:23 am, Hong <[EMAIL PROTECTED]> wrote: > > > JBQ, we need an updated SDK. That's the original point of this post. > > > Why dodge the main concern us developers are having now? > > > > On Fri, Jul 11, 2008 at 12:16 PM, JBQ <[EMAIL PROTECTED]> wrote: > > > > > just-some-guy: is this a way of saying that we (Google Android team) > > > > should continue to focus on making sure that devices can be available > > > > as quickly as we possibly can? > > > > > JBQ (Android Engineer). > > -- > take care, > Muthu Ramadoss. > > http://cookingcapsules.com- nourish your droid.http://mobeegal.in- find stuff > closer.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
