Convio Drupal Module - Meeting Notes
July 12, 2010
Ashok Modi - firstname.lastname@example.org
Rain Breaw - email@example.com
Alan Doucette - firstname.lastname@example.org
Chris Luther - email@example.com
Kevin Suer - firstname.lastname@example.org
Michael Pih - email@example.com
Chris: Demonstrated his Drupa_API module - built on the assumption that Convio DB is master. Provides Autosync and Admin interface and Admin Accessible Connection/Response Testing tools. Explained that is provides a set of programmer accessible apis, but nothing Drupal Admin User available. Suggests that many Convio features can be exposed and provided as separate related modules.
Ashok: Discussed his Convio API module. Split raw API module content from user management. Assumes that user site is on convio owned domain... site-id
The separate Convio_User_Module handles client login. If they are attempting to login, first check to see if they exist in Convio db, if they don't create a new user, if they weren't a convio user but drupal user, allow. Future registrations were pushed to the convio site, handled there, and then back to Drupal.
Alan: Discussed his Convio API module - flexible to support custom domain names - thinks that there should be core API module and multiple smaller modules providing deployment options.
Mike Pih (Kevin Suer): discussed the Convio sponsored Convio module. Single module with classes API (generic calls), UI for configuring keys, Convio user module authentication and SSO (bi-directional) hooks within user module to automatically insert correct libraries in to pages, personalization of user, handles both server and client-side (http:get) - security built around private key. Personalized tokens for admin end-users.
Things that Kevin's module don't have:
Don't have pushing user registration to Convio.
Editing the profile.
**Good things already in one or the other of the modules and could be blended together:**
All Convio Core Server APIs (chris)
Select Convio Client Side APIs (Ashok, Mike)
Admin interface enabling entry of convio site, user and api keys (all).
Admin test interface (chris)
User registration workflow - Ashok
User personalization tokens - Chris/Mike
UI for configurable integration mapping - Chris/Mike
Bi-directional single-signon (Mike)
Pushing user registration to convio ( Ashok )
Auto syncing between Convio and Drupal - Chris
Extra security to verify that data is coming from Convio and not elsewhere (mike)
Choice of domain name (so that the site doesn't need to have a Convio URL) (Alan)
**Things yet to build out or include in final:**
Server-side and client-side should be both possible.
Having test users drupal side is important.
Other Convio features executed as related modules.
Rain will create new issue on the project page for standing meeting time.
Ashok is official maintainer for Convio_API - will direct integration of all modules features
Chris will create Convio_User project and invite others, and will act as the official maintainer.
Mike and Kevin will create new issue on the project/convio_api page and add their module and documentation
Chris is presenting at the Convio conference in late October (Oct. 25-27). He would like others to present with him, so if anyone is available, let Chris know.
We also need to think long term about both D6 and D7 support.