This page is not updated at all. I need a real list of people who want and can do things for the project. If you want to be on the member list, please let me know.
Table of Contents
Membership requirement...the small print
Member listing, in no particular order:
SinisterDeath
Now the Great Lord comes.
Job Title: Project Lead
Area of Responsibilities: Landscape and exterior building. Collecting and merging team member's work.
Skills: Landscape, exteriors, interiors, quest building
SinisterDeath@noidea.com
http://noidea.comBack to Top
Kiriel
None
Job Title: Project Lead
Area of Responsibilities: Scripting, design spec document steward, storyline and quest building
Skills: Scripting, documentation, dialog, interiors, texturing
kiriel@direcway.com
http://kiriel.home.att.netBack to Top
Lews Therin
"Oh, Light, why do I have a madman in my head? Why? Why?"
-Lews Therin Telamon.Job Title: Project Lead
Area of Responsibilities: Lore, characterization, storyline
Skills: Interiors, exteriors, dialog, quest building
lewstherin@noidea.com
http://noidea.comBack to Top
Warren
Personal caption goes here.
Job Title: Consultant?
Area of Responsibilities: Lore
warren@noidea.com
http://noidea.comBack to Top
Daduke
Job Title: Team member
Area of Responsibilities: Modeler and texturing
Skills: Modeling and texturing
daduke@noidea.com
http://noidea.com
Lord Raven
Job Title: Team member
Area of Responsibilities: Jack of all trade
Skills: Exterior and interior building. Dialog. Programming (general) Wants to try modeling and retexturing.
lordraven@noidea.com
http://noidea.com
Back to Top
Membership Requirements....the small print
Leaving the team
When a team member decides to leave the team, they are asked to turn over all over work they have not yet uploaded. If they are owners of websites, forums, or other tools that can be re-assigned to another, they are asked to do this as well. Exceptions are if the site was not created for the project and is a personal resource for the member. The team will then move to a new site. The leaving member is asked to archive and send to the team leads anything that was stored on their site.
This is all just a curtsey. We do not list any legal rights. If a team member wants to leave or has real life issues and circumstances that do not allow them to continue on the project, we wish them the best of luck. The WOT team would like their leaving to have as little impact on the project as necessary.
Members who leave will still be credited with all the work they have completed and design they have contributed.
Contact information
Those members who take leading roles in the WOT team are required to provide personal information to the project leads. This is mainly name, phone number and address information. This information will never be displayed on this page or any other location. Nor will this information be revealed here, in any forum, no matter what the circumstances of the parting from the team.
This is merely to prevent loss of data when a team member decides to quit. Other teams have been devastated when key people disappear from projects taking needed work with them. Members who have a significant portion of the project need to turn it over when they can no longer work on it. Contact information will then be destroyed and never used. Real life contact information will only be used to recover necessary data in order for the project to continue.
Those who do not wish to provide personal information but wish to take a lead role must explain why and their explanation needs to be approved by the rest of the leads. This project will take a significant amount of time to finish. We will be working very closely together. Some concrete connection needs to be available to contact the member who has disappeared from the radar. It shows the level of trust and commitment the team member has for this project.
Hopefully, these rules will not keep members from joining.
Team Management
Like all teams, this one will have its own philosophy and rules. They are stated here so that all will understand how we want this team to run and members know where to go when they have issues.
Team Philosophy
The team will be run on a consensus bases. Consensus means that the majority of voters win. Anyone can vote on any issue. No one will wait until you finally vote. So keeping up with the forums and polls is a good idea. Everything will have a time limit.
There are exceptions to this. Ties. Or just plain wrong answers. This is where the team leads or Decision Makers come into play. Decision Makers can override a vote if they feel it is against the lore of the Wheel of Time or the planned game experience. This will not be done often though. Decision Makers will also be used to break the ties. In that case, their votes will count as more. If the vote is in their area of responsibility, they get more voting points than anyone.
Decision Makers or team leads can be anyone. Anyone who wants to be responsible for an area may ask to be a decision maker. If no one else has that responsibility, they will most likely get it. Decision Makers are required to be fair and not take personal feelings into account. Kind of like a jury member. Decision Makers are responsible for their area so they must be prepared to research and bring together all the information available. They are responsible for knowing what we are trying to create and have their decisions be in accordance to the overall plan. Lazy Decision Makers will lose their leadership roles after they show they do not really want the responsibility.
Decision Makers will also provide the guidelines for building things in their area of expertise. If you have questions on whether a certain script will interfere with others, then see Kiriel. If you want to know if you should turn in several esp's instead of one, then see SinisterDeath. If you want to know if a certain quest will conflict with the nature of a character, see Lews Therin. Same with any other question you have.
Decision Makers also know their limits. If something in your area overlaps another, discussion may be needed. Or just opinions from the group on how something works or looks or feels while playing.
Not knowing. Do not be afraid to look stupid. Do not be afraid to not know the answers. Every time you ask the rest of the group for help you will learn more and become better. Do not hide ignorance. No one loses their leadership or Decision Maker status for not knowing everything about their area. We all have one goal. To provide a great mod that makes the player feel like they are in Robert Jordan's creation. In order to provide that, we need to shoot bullets at everything we design and create. It needs to pass the test of fire. A team is better than a single brain. Brainstorming is better than making the wrong, hasty decisions.
It takes a thick skin to put your ideas out and have people shoot at them. It takes confidence to say "I don't know." or "I don't understand." or "I need help." But you will find that no one thinks you are stupid for saying these things. Not knowing is not stupidity. It shows an open minded person who is confident in themselves. Confident that they don't need to know everything and they are willing to learn.
Taking something to the team. Only the larger issues will go to a vote or discussion. If you disagree with the Decision Maker on their decision, ask them to take it to the group. A Decision Maker will not refuse or punish anyone for this. It is part of their role and responsibility.
If you have an issue that you feel needs some more brains working on it, take it to the group. Start a new message thread and ask for opinions.
If you have a sample and want to see if everyone thinks it looks right, take it to the group.
If you have some scripting or dialog to test to see if it makes sense or works smoothly, take it to the group. Don't confuse this with our bug testing though. If dialog seems wrong, take it to the group for an opinion. If scripting messages seem cumbersome, take it to the group. You never know when the team can come up with something that works great.
Disagree and Commit. When you lose a debate or vote, you are asked to disagree and commit. This means you fought the best fight. You came to the table with all the information you could find to support your side. The more important an issue is to you the more important it is for you to investigate and be prepared for your side's evidence. But you lost anyway. Now you need to do your best to make the decided solution work. No sabotage, no matter how subtle. No continued battle for your side.
It also means that if at a later date it was determined that you were right, you should really try not to say, "I told you so." It is difficult. We won't hold it against you if you do so. But try not to. Everyone will remember your epic battle and know you were right all along.
Summary. This is basically it. We will work together, as a team, to create the world of Robert Jordan's Wheel of Time. We will respect each other's opinion (no matter how stupid you think they are - keep that to yourself and fight your side with concrete information.) We will take victory and defeat and keep moving ahead. Everyone gets to participate at the level they want. Anyone who wants to take a leadership role gets the opportunity.