Speakers Bureau/Technology Team/05-25-2007 Agenda and Notes
International Game Developers Association
The purpose of our second meeting is to review and give feedback to the policy committee regarding their proposed web site interaction flow and general guidelines.
Table of contents |
[edit] Participants
- Jason Della Rocca
- Ramon Romero
- Darius Kazemi
- Lucas Stapley
- Austin Krauss
- Brett Doerle
- Shane Liesegang
[edit] Flowcharts
Throughout the meeting the technology team focused on the flowcharts provided by the policies team. The first flowchart presents an over view of common features relating to speaker registration while the second flowchart goes into detail regarding the requester search mechanism.
[edit] Speaker Sign-Up Flow
The technology team first reviewed the IGDA Sign-Up Flow and Speaker Sign-Up Flow sections of the first flowchart.
[edit] IGDA Sign-Up Flow
- Speaker signs into IGDA website, signs Honor Code before being directed to enter profile data.
- Some of this profile data can be prepopulated from data existing in the IGDA profile database.
- There was some concern brought up that because the Speaker's website would be on a different domain than the main IGDA site, that the database information would be difficult to access across domains.
- We determined that this wouldn't be a serious issue since both sites would be hosted on the same server.
[edit] Speaker's Forum
There was some discussion regarding the Speaker's Forum concept that was referenced on the Speaker's Information Flow section. The concept being that speakers would have a forum to exchange and discuss best practices, speaking experiences, etc.
- We didn't think this was necessary for this initial phase of site creation and could possibly moved to a "phase 2" of development.
- Another idea was to utilize the existing IGDA forums for the implementation of this feature.
[edit] Requester Search Flow
The majority of the meeting focused on the Requester Search Flow details outlined on the second flowchart.
- Separate domain, hosted on the IGDA server
- Goal is to be a bit more “user friendly” in website design than the main IGDA site
[edit] Search Options
- If no game developers are found using search criteria, a link to the speaker resources should be provided so that instructor may review and present the material on his/her own
- Some discussion about job search granularity
- Job titles may be confusing to requesters (e.g. Level Scripter vs. Designer)
- One idea proposed is to have a FAQ or Glossary of job titles and responsibilities
- Another idea which the policy team will evaluate is to present search choices based on a broad discipline instead of job title (e.g. art, programming, design, music, etc)
- Simple search upfront, detailed information to be presented later after requester registration (similar to match.com or other matchmaking sites)
[edit] Accounts
- Requester has to sign up for a free account
- The account should be fairly low-profile, some examples of data we may want to store are: name, email address, institution
- We'd like to display a list of simple search results (perhaps just job titles) before requiring the requester to create an account or sign-in.
- We weren't sure why the policy team decided upon "no names" when displaying a list of potential speakers (perhaps privacy was a concern)
- Once the requester has registered and read the "Community Honor Pledge" detailed search results would be displayed
[edit] Registering the Event Info
- Should a time frame be included in the email request to the potential speaker?
- Throttle requests to speakers
- Have database track the one week timeout and take appropriate action if the speaker fails to respond to the requester
- Discussion about requiring speakers a one month in advanced time
- Decided on a solution that would just be a text disclaimer for one month, thought it would be too easy to game the system otherwise
- Burden is on speaker to contact community member
[edit] Multiple Speakers
- We decided this could be an item for "phase 2" of the site; for now we want to focus on the flow for a single speaker
- No need to queue requests, take them back to search results and grey-out the speaker search result that either didn't respond in one week or responded with a 'No' answer
[edit] Short-Term Tasks & Updates
- Shane Liesegang has established a Subversion repository will post wiki page of info.
- Jason Della Rocca will do an overview of the database from the policy team flow charts.
- Shane Liesegang will mock up some static HTML pages demonstrating the overall web site flow from page to page.
