Face it. We need some serious organization here. We need a virtual file file Cabinet as well. We need to play test and verify changes and keep track of why changes go in.
I propose 2 systems that would go into effect as we let in new members. They would help us manage changes that go into this game as well as keep all WBR members on the same page and enable us to always know why something went in and how it got in.
Proposal 1: Queue System
Generally, the idea is to have a list of any and all changes to this game, from largest and most game changing to the most frivolous/cosmetic. This is so we know what needs to be done and what doesn't need to be done. This list also has priority tiers. So important changes don't go at the bottom (ex, Change 1 would be A Rank Priority and Change 2 would be Rank C. Change 1 would go at the bottom of A Rank and change 2 would go at the bottom of C Rank.)
The system works like this. A change is suggested. The change is nominated by a few WBR members and is essentially added the Queue list and sorted into the right priority. We start from the bottom and work our way down. Every time we start a new item, WBR as a whole discusses it for a certain period of time before a final decision is reached. Based on how important or how high the priority, the discussion time can range from a day or two to two-three weeks. At the end of the discussion, a super majority in favor must be reached in order for the change to go through. 66% or more. If the Super Majority says No, then the change is dropped from the Queue list and can't be re-requested until a later date waaay down the line. If it falls inbetween (50-50ish and around there) then discussion of the topic is extended and a poll is created as the end all vote. If a 50-50ish is reached again, then the change is turned down temporarily for revisiting at a later date and we move onto the next item on the list.
Of course before any discussion is held, the change or changes are put into a private WBR build for playtesting and those who have not playtested shall not be allowed to participate in discussion. We're working on a huge *** project that will take more than a year to even become close to finishing. The least everyone can do is playtest for a period of time based on changes, minimum, before even thinking about contributing to discussion.
Through a method such as this, any and all changes go through most members of WBR before giving the seal of approval, so Ness fair, Samus Jab, etc. Don't happen again.
I'd personally be willing to manage this queue list myself if it means helping WBR get **** done properly.
Proposal 2: File Cabinet
Simple concept. We keep a file of every change and all of its details in a thread for referencing.
Every approved change, reason as to why. When did the change fall through. What the change does. Who made the change. Who supported it. Who/what is it for. Things like that for easy referencing and to keep all WBR members on the same page, which is something we'll need if we're adding new members to this group.
I believe that complete co-operation with these things give WBR much needed help when it comes to changes in this massive project.
This will generally require the co-operation of everyone every, but I know we're all competent enough to do this.
I propose 2 systems that would go into effect as we let in new members. They would help us manage changes that go into this game as well as keep all WBR members on the same page and enable us to always know why something went in and how it got in.
Proposal 1: Queue System
Generally, the idea is to have a list of any and all changes to this game, from largest and most game changing to the most frivolous/cosmetic. This is so we know what needs to be done and what doesn't need to be done. This list also has priority tiers. So important changes don't go at the bottom (ex, Change 1 would be A Rank Priority and Change 2 would be Rank C. Change 1 would go at the bottom of A Rank and change 2 would go at the bottom of C Rank.)
The system works like this. A change is suggested. The change is nominated by a few WBR members and is essentially added the Queue list and sorted into the right priority. We start from the bottom and work our way down. Every time we start a new item, WBR as a whole discusses it for a certain period of time before a final decision is reached. Based on how important or how high the priority, the discussion time can range from a day or two to two-three weeks. At the end of the discussion, a super majority in favor must be reached in order for the change to go through. 66% or more. If the Super Majority says No, then the change is dropped from the Queue list and can't be re-requested until a later date waaay down the line. If it falls inbetween (50-50ish and around there) then discussion of the topic is extended and a poll is created as the end all vote. If a 50-50ish is reached again, then the change is turned down temporarily for revisiting at a later date and we move onto the next item on the list.
Of course before any discussion is held, the change or changes are put into a private WBR build for playtesting and those who have not playtested shall not be allowed to participate in discussion. We're working on a huge *** project that will take more than a year to even become close to finishing. The least everyone can do is playtest for a period of time based on changes, minimum, before even thinking about contributing to discussion.
Through a method such as this, any and all changes go through most members of WBR before giving the seal of approval, so Ness fair, Samus Jab, etc. Don't happen again.
I'd personally be willing to manage this queue list myself if it means helping WBR get **** done properly.
Proposal 2: File Cabinet
Simple concept. We keep a file of every change and all of its details in a thread for referencing.
Every approved change, reason as to why. When did the change fall through. What the change does. Who made the change. Who supported it. Who/what is it for. Things like that for easy referencing and to keep all WBR members on the same page, which is something we'll need if we're adding new members to this group.
I believe that complete co-operation with these things give WBR much needed help when it comes to changes in this massive project.
This will generally require the co-operation of everyone every, but I know we're all competent enough to do this.
