--- Meeting begins --- People present: Hellfire[Coder], Tombe[Music], Jpl, Qton, eXinion, Zuu_Info, orudge (though not very talkative) People joined in later: oliver_ --- Agenda --- [21:01] Our topics for today: ## added topic · Short discussion of the minutes [21:01] · Idea processing progress [21:01] · Means of communication [21:01] · Core features, revisited [21:01] · Programmer recruitment, revisited [21:01] · Design documents [21:01] · Setting up mailing list --- Short discussion of the minutes --- - No comments on the minutes of the last meeting - eXinion volunteered to make the minutes of this meeting --- Idea processing progress --- - All ideas are processed - We decided to categorise all ideas, into the following categories: - User Interface - Multiplay - Artificial Intelligence - Gameplay - Because gameplay covers most of the ideas we subdivided that category in the following subcategories: - Vehicles - Stations - Tracks - Environment - Economy - Three volunteers for categorizing every idea in the database: - Qton will do ideas 1 - 61 - eXinion will do ideas 62 - 123 - Hellfire will do ideas 124 - 194 --- Means of communication --- - skipped, as 'Setting up mailing list' is mostly the same topic --- Core features, revisited --- [21:31] Last meeting we had a discussion and the following core features popped up: [21:32] - Multiplayer games: up to 8/16/32??? players. [21:32] - Extensibility/Flexibility: The database of vehicles/objects/graphics should be stored in [21:32] separate files in a directory structure (able to add vehicles and such to the game without [21:32] recompiling or having to remove other vehicles) [21:32] · A hierarchy in track types, where subclasses of a tracktype inherits properties of the [21:32] parent, but adds some of its own. [21:32] - Hard limits far exeeding practical limits. [21:32] - Cross-platform support: Windows, *nix and Mac support through SDL. [21:32] - 3D engine: to be determined (19/06/2004). - I added this to the list of core features: - Simplicity: keep it simple. Extending can be done at a later time. - We decided to build a 3D engine ourselves and agreed that details (like viewpoint) are just a matter of adjusting some variables, so they're not an issue yet! --- Programmer recruitment, revisited --- - We already welcomed eXinion and Mek - Zuu and Korenn offered help on coding --- Design documents --- - Uzurpator's document is a nice start for an appendix of our functional specifications - We'll discuss the Functional Requirements document at the next meeting when the ideas-database is fully categorized - At the next meeting we'll divide the task of converting the ideas to a well-structured document and discuss it the meeting after - We decided to add two flags to every idea in the database, a flag to express it's 'ease of implementing' and a flag for 'priority to implement' - The ease of implement flag will have the following values: - "not implementable" - "hard to implement" - "easy to implement" - "necessary feature" - The priority flag will have the following values: - "Must have" - "Should have" - "Nice to have" - "Questionable" - The questionable ideas will require votes. If the developers vote in favor with a majority of 66 %, the idea will be implemented. When the developers vote in favor with a minority of 33 %, the idea will not be implemented. If the developers vote in favor between 33 % and 66 %, the users get to vote. For the idea to get pushed through, the users require a 66 % majority as well. --- Setting up mailing list --- - We have two mailing lists on Sourceforge, (see http://sourceforge.net/projects/tt2), one for announcements and one for discussions. I think that all people who want to be involved in TE should subscribe to those mailing lists. - Minutes will be sent over the discussion mailinglist --- Meeting closure --- - [22:58] MEETING ADJOURNED! - [22:59] Next meeting, Saturday July 3rd @ 1900 GMT