Chairman: Hyronymus & Steve
Minutes: Steve
Other: pjaytycy, uzurpator, Mek, Purno, Grunt, TinFoil

1. Start meeting
1a. Pick a chairman and a minutes man
Hyronymus was the chairman.
Steve made these great minutes.
1b. Discuss minutes of previous meeting
Everyone liked the minutes.

2. Discuss the previous objectives
  2a. Website - Create Template & 2b. Website - Graphics
Steve's website template at http://www.phoenixscripts.co.uk/tempire/steve/home.php was discussed and people were asked to choose between the green and blue colour schemes. There was much discussion about using The Master's logo with this template and possibly allowing users to choose between the styles. It seemed people waited until the meeting to discuss
such things instead of talking about it on the forums. In a vote, people chose Steve/Zuu's template, over the others.
  2c. Wiki - Re-organize
Nothing was discussed here, instead the discussion took place in 3.
  2d. Coding - SDL Demos
There was discussion about dropping the SDL demos, as well as exploring DirectX. These should be discussed on the forums.
  2e. Design Document - Progress Report
uzurpator said he was fine with writing the Design Document and plans for the next step were outlined in a later section.

3. Website and Wiki Discussion
Noone was able to give a good use for the Wiki and due to problems with its use, it has been decided to no longer use it. The Wiki will remain where it is, incase files are needed, but it will no longer be linked to. It was also decided that sourceforge does not offer us anything of value, so we have decided to seek another host. orudge has offered services on his hosting network but nothing has yet been finalised.

4. New Project Objectives
  4a. User Interface - Collection of ideas
Ideas should be collected about what the user interface needs. This includes the sections of windows, window contents, icons on the screen. General themes can also be discussed. Some of this material is included in the Design Document, so that should be taken into consideration.
  4b. Website - Complete Template
Complete the website template using the results from the previous objectives as well as the information discussed in the previous meetings. This will include making sections for the new parts built in objective 3.
  4c. Website - Code major parts
Coding can start on major parts of the website. These have been identified as:
  1) A news system to allow the project leaders to post meeting dates and other useful news posts.
  2) A system for storing/showing the minutes and logs of the meetings.
  3) A prototype layout of how the Design Document will be displayed on the website.
For these three sections, a full admin system is not necessary. They should incorperate the public section of the website and proper admin controls can be added in a later objective.
  4d. Coding Group - Sort it out
A coding group needs to be properly created so that they can be ready to do relevant coding tasks and help with the project. Confirming who is already part of this group, is covered in this objective. During the meeting there were several people who were interested in coding that have been forgotten, they should be included.
  4e. Design Document - Commenting Part 1
People should read and understand the first three sections of the design document and make comments on them. They can then post these comments in the appropiate thread, before the objective deadline. The comments will then be collected and sorted by the project leaders. Depending on the comment content, they will be discussed with the Design Document creators and possible updates to the Design Document will be created from there.

5. Any other business (AOB)
There was wonderings about where Hellfire has gone.
6. Next meeting
Tuesday 6th September, time and date to be confirmed.
7. End