Hi Matthew, You can easily identify people with a specific level expertise on Stack Overflow by looking at their reputation or at previous questions they answered, and a good way to attract people on a question is to setup a bounty.
Members of the App Engine team and the community are already active on Stack Overflow, just take a look at the tag statistics and hopefully you will recognize a few people there :) http://stackoverflow.com/tags/google-app-engine/topusers In the top users you can see: http://stackoverflow.com/users/818274/guido-van-rossum (Python and NDB daddy, App Engine Software Engineer) http://stackoverflow.com/users/12030/nick-johnson (~59K reputation, App Engine Developer Relations) http://stackoverflow.com/users/453278/dan-sanderson (Author of Programming Google App Engine, and working for Google) http://stackoverflow.com/users/280474/robert-kluin (top group contributor) http://stackoverflow.com/users/125967/moraes (webapp2 author) http://stackoverflow.com/users/62288/dave-w-smith (App Engine Software Engineer, working on Map Reduce and testing) http://stackoverflow.com/users/23786/moishe (App Engine Software Engineer, working on XMPP, Mail and Channel API) http://stackoverflow.com/users/992563/amy-u (Author Google App Engine Java and GWT Application Development, App Engine Developer Relations) http://stackoverflow.com/users/656408/proppy (myself, App Engine Developer Relations) And many others I must have forgotten. Hope that answers your concerns. On Tue, Feb 7, 2012 at 11:24 AM, Matthew Jaggard <[email protected]>wrote: > @Ikai - I think this is a great idea, however like Ruslan I'm a bit > concerned about how much Google employees will be looking at the questions. > Would it be possible for us to have a mechanism for raising to a Googler > any questions that cannot be answered by the community. As a group we're > able to deal with most simple problems or confirm bugs but it would be > great to allow certain people - or people with a specific level of > expertise - to bring questions to your attention. > > > @Ruslan - This is a good idea, raise an enhancement request and I'll > happily star it. Or submit a patch? > > > Thanks, > Mat. > > > > > On 7 February 2012 02:31, Ruslan V <[email protected]> wrote: > >> Dear Ikai, >> >> >> Monday, February 6, 2012, 6:26:10 PM, you wrote: >> >> >> It looks like your question has already been answered: >> >> >> http://stackoverflow.com/questions/9124564/datastore-access-is-horribly-slow-on-dev-server-if-you-have-more-than-few-object >> >> The datastore stub is that: a stub. You cannot reliable depend on it for >> performance data. >> >> It would be great if you guys allow engineers to replace the stub with >> custom implementation as it was done in gae-sqlite for Python version of >> SDK. Is there a chance of this happening ? >> >> /Ruslan >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" 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/google-appengine-java?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" 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/google-appengine-java?hl=en. > -- Johan Euphrosine (proppy) Developer Programs Engineer Google Developer Relations -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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/google-appengine-java?hl=en.
