Hi James, This is similar in spirit to my earlier suggestion<https://mail.google.com/mail/u/0/?ui=2&shva=1#starred/142ffd90000b639b>for the committee members to (eventually) address the Moderator questions asked at GWT.Create<https://www.google.com/moderator/#16/e=21396f>. There are some good questions there. Perhaps, should your idea catch on, for the first Q&A we could add more questions to that Moderator instead of setting up a new one?
Boris BORIS BRUDNOY Java/GWT Web Software Developer (LinkedIn<http://ca.linkedin.com/in/borisbrudnoy> , Careers 2.0 <http://careers.stackoverflow.com/brudnoy>) On Sun, Jan 26, 2014 at 3:41 PM, James Nelson <[email protected]> wrote: > Hi all, > > I am just wondering if it would be possible to setup a quarterly Q&A > hangout-on-air with steering committee members taking questions from the > public, and presenting on ideas that are in the works for GWT. > > It would be similar to the panel held at GWT.create, except we could > collect up the questions via Google Moderator over the coming months, to > give panel members time to discuss and decide on answers. > > If possible, I would like to get a few RSVPs before mentioning it at the > community hangout; > we could schedule the first Q&A panel for the end of March, and post the > moderator tomorrow to get people started on the questions. > > Thanks, > James > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > --- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
