In our June 2012 event, East Bay GTUG welcomes back Ryan Boyd, who just published his first book with O'Reilly: Getting Started with OAuth 2.0. Ryan will introduce us the goals of OAuth, review the various OAuth 2.0 flows and discuss the use cases for each flows. Ryan's presentation was originally scheduled on May 2012
The May sessions were fantastic, many first time attendees and East Bay GTUG season passes holders attendees got to see two great technologies explained, and how we can create applications with the respective SDKs. We still have one Neurosky headset left, and we will lend it to the developer chosen by this event attendees. Please scroll to the bottom of this event information for the details.
East Bay GTUG appreciates the support from the city of Dublin, California. Regional Meeting Room is a first-class location for business and social events.
Google IO 2012 meeting is scheduled on June 27-29 at Moscone West Conference Center. See "Heads Up: Google IO Extended" details at:
6:00pm Check in, networking
6:10pm Getting Started with OAuth 2.0 (Ryan Boyd, Google)
7:10pm NeuroSky headset projects presentations/selection
7:45pm Raffles, clean up and networking
Getting Started with OAuth 2.0
OAuth 2.0 is the next generation version of OAuth which makes obtaining authorization to user data significantly easier than with OAuth 1.0. It also enables app developers to outsource their authentication challenges to OAuth 2.0 identity providers, such as Google, Microsoft and Facebook, while streamlining the login experience. In this talk, I will introduce the goals of OAuth, review the various OAuth 2.0 flows and discuss the use cases for each. I will also demonstrate some tools which will enable you to easily get started with OAuth 2.0.
Ryan Boyd is a Developer Advocate on the Google Developer Relations team, helping businesses build applications integrated into Google Apps. Ryan wears both engineering and business development hats, so you'll find him writing code and helping businesses get to market with integrated features. He also recently published his first book with O'Reilly: Getting Started with OAuth 2.0.
Rules for the NeuroSky headset projects presentations on Monday, June 4, 2012:
A. Eligible person:
A1. must attend the East Bay GTUG event on Tuesday, 5/29/2012.
A2. Arrive to the East Bay GTUG June meeting by 6:30pm to receive a presentation order number.
B. Project presentations:
B1. On your project, list one clearly objective that you want to achieve with the developer edition NeuroSky headset. This object will be used to be judged if you become the current project winner and you return to show your application (see session D)
B2. Please provide both hardcopy and softcopy about your ideas with your project name, your name, your email address, your meetup alias, and project info by 6:30pm at the East Bay GTUG meeting to the East Bay GTUG organizer(s). You will receive a presentation order number.
B3. At about 7:10pm, East Bay GTUG organizer will call number for you to pitch your project to the attendees. If your number is called, you have up to two minutes maximum to present and two minutes to answer (if any) questions.
C1. East Bay GTUG June meeting attendee will receive a ballot by about 7pm. They can turned in their ballot for vote and select up to the project(s) that completed pitch session.
C2. All ballots will be counted. In case of tie, a random pick will be used to select the winning projects. All the order of projects will be recorded.
D. Winning project:
D1. Winning project has one regular meeting period to complete the project as proposed, and return on the next meeting (currently Monday, July 2, 2012) to show the attendees how it works out (or not). During this loaning period, please keep the device in original condition. Project winner must agree, before taking the loaner device, that you will pay Easy Bat GTUG retail price for the headset should the headset is not in working condition prior to be confirmed as a working project (listed in D2) by signing a agreement paper.
D2. Should the project works as proposed (see objective on session B1) , the winning project person will keep the headset; otherwise, the headset shall be return to the East Bay GTUG.
D3. Should the project did not work out, the next runner up will be contacted and will have a chance to work on the project and continue the process listed in section D. The current winning project person can choose to withdraw from this process, and the next runner up will be contacted.
D4. Should every projects fail or no project is proposed, this headset will become an East Bay GTUG community equipment for testing.