Speakers Bureau/Technology Team/04-25-2007 Agenda and Notes

International Game Developers Association

Jump to: navigation, search

The first meeting of the Speakers Taskforce Technology team! The purpose of this meeting is introduce team members and discuss the high-level requirement and implementation issues and to establish some short-term tasks. Below is the meeting agenda outline with meeting notes interspersed; feel free to add, remove, or alter anything as needed.

Table of contents

[edit] Participants

  1. Nichol Bradford
  2. Jason Della Rocca
  3. Ramon Romero
  4. Dariius Kazemi
  5. Lucas Stapley
  6. Austin Krauss
  7. Brett Doerle
  8. Shane Liesegang

[edit] Project Overview

[edit] High Level Functionality Provided by Speakers' Website

  • provide login authentication mechanisms for developers and groups
  • data entry and storage for developers to register as speakers
  • speaker and group communication shall be facilitated through the web site
  • speaker course materials (PDFs) shall be stored and accessible through web site

[edit] Database Moderation

Requests for speakers shall be managed via the site and moderated by a taskforce member.

[edit] Initial Design Principles

[edit] Developer Profiles

Searchable by zip code, years experience in the industry, discipline, game credits, willingness to travel.

  • The policy team will determine the exact criteria that will be entered by developers and searchable by groups

[edit] Speaker Reviews

Can groups review speakers? Can speakers review groups? If so, the website shall provide interfaces for entering and querying this data.

[edit] Self Sustaining

Site should be self-sustaining as much as possible, this includes:

  • provide login information to developers and enter developer profile information into the speaker’s database
  • use existing IGDA database information to automatically update speakers information. For example, if a developer updates his/her employment information in the IGDA profile, this information should be automatically reflected on the speakers website.

[edit] Constraints/Resources

  • Speakers website should be it’s own domain and not exist within the IGDA website proper, although it will be hosted on IGDA servers
  • IGDA servers provide a LAMP web development environments (Linux, Apache, MySQL, PHP).

[edit] Some discussions about what the interface will look like

  • Wordpress / Blog interface ruled out because the goals of the site are mostly orthogonal to a daily blog page
  • Most likely a custom HTML interface will be developed, with additional Web 2.0 features given the resources (Flash, AJAX, etc)

[edit] What will be the link between the IGDA database and speakers database?

  • The speakers database shall use the IGDA database in “read only” fashion for data that is applicable.
    • Login / authentication
    • Employment / experience
    • Developer profiles
  • IGDA members registering as speakers can have some data populated from information in the IGDA database

[edit] Work Planning

  • Goal is to have speakers site running by the beginning of the school-year. The initial speakers shall also have be registered by this date
  • A separate email list will be established for the technology team

[edit] Short Term and Immediate Tasks

  1. Evaluate requirements from the policy committee
    • This may include documentation scoping the project and outlining an initial implementation plan.
  2. Paper design / prototyping phase
    • Jason Della Rocca will do the speaker’s database design and prototype
    • Shane Liesegang has volunteered to do some interface prototyping of the actual speaker’s web pages
  3. Version Control / Workflow
    • Shane Liesegang has volunteered to establish a Subversion repository to house the deliverables produced and shared by the technology team
  4. Recruiting
    • There may be a need for an additional recruiting phase to fulfill the role of a web-designer or person versed in HTML for page creation

[edit] Hub Team Representative

  • The technology team will need a representative to participate in bi-weekly one hour long meetings with the other teams of the taskforce. The goal of these meetings is to update other teams on the progress of the technology team and retrieve feedback as needed.
  • Shane Liesegang has volunteered to be the first Hub representative, with the understanding that he may pass this task to another team member if his schedule conflicts.

[edit] Additional Topics

Thanks to all participants. Future meeting times will be coordinated via email with the goal of lasting no more than one hour.

Retrieved from "http://www.igda.org/wiki/Speakers_Bureau/Technology_Team/04-25-2007_Agenda_and_Notes"
Personal tools
Toolbox