@Nick Once we have a playable demo we will do nightly builds and stable release. What I'm referring to right now is having the Automation System pull and update and delete an asset build for us every night so that when new content is generated it is build an ready to download the full archive via probably ftp. So let say Mel is done with the image she is working on now and you need it you would just have to wait till tomorrow to do a sync of the ftp to have it and it will be in the right naming conversion and folder structure we use. Filezillia has a lot of feature I'm sure we can use it to sync with.

@Johannes No its good I am going to add the GUI part into it but other then that its good to go for now. I will edit it after this sprint is over.

Normally when you are done and you need it reviewed we put it in "Request Review" mode which can be done either by checking the box when you enter time or on the agenda itself by hitting the button at the bottom to "Request Review".

@James That's a little over my head, but what I've seen from projects that do nightly builds. They seem to also do a previously stable build (periodically) just in case the nightly build fails, so there is something to fall back on.

@James- I reviewed and made some tweaks on chapter 2. It's done but there's not agenda assigned. I can make one if you want but it will likely require approval like last time. For now, I'll move one to a wiki for some ideas for the leads to review.

@Johannes That is better thank you I will do a full review of them later tonight or early tomorrow morning.

Can you explain to me what makes the editor hard to use for you their might be something I can do to fix it.

I would like for most are documentation to be keep this way so that the team can use the search and everything is in one place so no body is guess where information they need is located. This goes for all content on the site. If you notice the forum house the meeting notes, kanban, etc this way information for discussion is in one place. The GDD and all supporting documentation for the team is in the wiki for this reason.

@JamesI formatted a little bit and separated them, on the add on is everything I have of the gdd. On the other wiki page is everything essential.I'm not completely sure if that's what you meant, just tell me if not.

Editing such a big document with this editor here is not very easy, but if you want me to, I can improve it more.

@Nick After reviewing the assets to be synced. I notice this will probably take a lot of time out of our schedule to do this every time a new asset is created or an old on is re-done. So I think a better solution to this would be to add into the Automation System that run every night a build process that would download and organize our teams assets for the game. Then all we would have to do when updating asset is copy it from the server which I can automate as well. This will also make sure asset folder structure is followed as well. Thoughts?

@Melisa Will you please review Sean tracks? Their was an idea passed around awhile back of having sound for when switching between screens. We will try these out and see if it make sense and sound good in a later sprint.

@Johannes Well sort of :) we will need it formatted better and anything that is in the original GDD that is not in yours will need to be placed into another wiki page I have made for this agenda. We want to keep in as organized as possible for the whole team to review. These are the master copy everyone has links too so they should be as easy as possible to read.