Guild of Writers

TODO:
* Add pictures in each of the sections
* Write-up Wiki page for archiving an age, using [http://www.dpwr.net/forums/index.php?s=&showtopic=5447&view=findpost&p=24546 Horatio's instructions] [DONE]
* Try out those archiving instructions on Ahra Pahts
* Add a link to Inanna's journal discussion on Myst's puzzles [DONE]
* Turn Jishin's Bugzilla post into a Wiki page and link to that instead [DONE]
* Redo the GoMe section, according to [http://messengers.sixpencemedia.com/forum/viewtopic.php?p=4696#p4696 Szark's writeup] [DONE]
* Add a note in the idea section about adding hooks to allow for future expansion (see [http://forums.guildofgreeters.com/index.php?showtopic=14811&view=findpost&p=230071 Robyn's post]) [DONE]

== Suggestions from Natales (GoC) ==

See original post [http://www.uruobsession.com/forum/index.php?s=64fc939e6afff2238777de0050dff14a&act=ST&f=65&t=34006&st= here].

* Add reference to [http://www.eldalamberon.com/dni_dict.htm D'ni Dictionary] in "Giving it a name" [DONE]
* Refer people to [http://www.google.com/language_tools Google Translator] for making English translations, then finding someone to clean it up [DONE]
* When PMing people to review your idea, thank those who respond and ask if you can share the response in your thread, in order to help others understand your idea better and to bump the thread  [DONE]
* When asking the GoC to make a map, do so in the [http://www.uruobsession.com/forum/index.php?act=ST&f=65&t=33635 Task Thread].  Natales watches this thread and should respond in a few days. [DONE]
* In volunteer notes, mention how the experienced people may not be available to work on your age, and that your team will most likely be made up of novices.  The experienced could serve as consultants/advisors, answering questions by the team. [DONE]
* In volunteer notes, incorporate the following: "Volunteers are not employees nor are they slaves. Volunteers cannot be told what to do nor when to do it. Make known what needs to be done, ask for help. Set milestones and ask when they think they may complete the task(s). Check to see how they are progressing and how likely they think they will complete on THEIR timeline. Adjust as necessary. Find out if they need help. Be gentle and understanding whenever asking about schedules. There can be a lot of emotion on these issues. Leadership is about how well you handle the issues." [DONE]
* Add a step before massing model to produce a layout design.  You can help a fledgling artist  obtain membership status in the GoC or GoFA by producing a decent map for your age. [DONE]
* For configuration management, cite examples such as GIT Bash [DONE]
* In the Test Age section, note that the formation of the working map can happen at this stage.  When the mapmaker is done, they can submit their work to the GoC Tech Data site.  Maybe put details on separate Wiki topic. [DONE]
* Incorporate Natales' Improving Your Age comments into "Adding placeholders for expansion" subsection. [DONE]

== Suggestion from Chacal ==
Versioning: even when not using version control software, it is essential that you keep incremental versions of your work, for example by incrementing a version number in the .blend file name, or by using a new folder for each version. Do this every 2-4 hours. Even if Blender doesn't crash on you, it is possible (even probable) that a change you make breaks the entire Age, and that you can't find the error. Having a recent version tucked away means you can revert to it, losing a little work. Having only one version means you could lose WEEKS of work. [DONE]