2013-01-16

First meeting
Per the schedule, our first team meeting to get ourselves organized and working will be during our class period this Thursday, January 16th. We may get some in-class time tomorrow (Tuesday the 14th) to meet, so please be prepared for that possibility as well. Meantime, please be thinking about your desired role versus needed project roles, ask questions about the project, post ideas, and get connected with the team. Then they built another hall [...] which also is a very beautiful mansion, and is called Vingolf. ''Thereupon they built a forge; made hammer, tongs, anvil, and with these all other tools. Afterward they worked in iron, stone, and wood, and especially in that metal which is called gold.'' -The Prose Edda, chapter 6, stave 14

Agenda:
Please feel free to add to this list if you feel there are other topics that need to be worked out!
 * Share contact information
 * Investigate project scope
 * Begin drafting requirements
 * Establish roles of each contributor (these are subject to change according to project needs)
 * Establish programming environment, target platform, project website and source control software.
 * Plug in to collaboration tools, including timesheet

Agenda for 1st team meeting, Thursday, January 16th: WHAT WE DO: Begin drafting requirements HOW MUCH: Investigate project scope - Required information for getting an art team, which we need asap - the design process is deep and lengthy. Everyone has asked I provide deadline/project scope information before they commit to the project- Bryce WHO: Establish roles of each contributor (these are subject to change according to project needs) BUILD A HOME: Establish programming environment, target platform, project website and source control software. Plug in to collaboration tools, including timesheet (Does everyone have time recording software? Report time spent and research areas, findings to group) WORK: Begin prototyping. Answer the question of whether you can fulfill your role with the given platform, environment, etc. ASK: What aren’t we thinking about? Next time: Refine requirements and feature set, very rough work estimates for features. (Gantt chart - this is how we track accountability for project roles and features) DELIVERABLES for next meeting:

Riley Monson and Mark Siebert absent.

Notes: -Introductions -Project Wiki - shoutwiki, create accounts -private repo - github.edu (Nathan)?

Assignments: -Riley Monson: migrating old wiki to new, invite Dr. K to the wiki -All team members: Acquaint yourself with at least one area of interest within the Project Requirements. Place your name next to the topic or subtopic you are researching. Significant research will be required, especially for the item creation process. Your task is to download and use at least two (preferably three) of the Game Development Platforms listed on the Programming Environment / Language Discussion page and to become acquainted with them and experiment with them, taking particular care to investigate the feasibility of implementing your feature/topic of the game using that particular game engine. If significant limitations exist for major parts of the game or if there are ways to facilitate a particular feature, it is best to know sooner rather than later. Take this also as an opportunity to prototype. For example, if you are trying out game engines for the game world, try to build a simple terrain or scenery or run through a tutorial on it as a proof-of-concept. We’ll compare notes to help us choose our final game engine when we meet next week.

=
=================