Main Issues:
Majority Vote regarding Vetoes
It isn't feasible to hold a vote across the entire BNG. Something like selecting x amount of readily available BN's would be better. I think 7 is the most feasible. Selection should be random, of course, and participation in vetoes should become a mandatory responsibility of BN's. Currently, it seems as if people who don't want to participate in votes can just not. There is no penalty for not participating, but as a result the vote may be skewed. Therefore, in order to ensure participation, I feel BN's who are chosen to participate in any veto mediation vote must also provide a short opinion on their choice (yes or no). I think it only has to be 2-3 sentences, nothing major, but this is to at least acknowledge that the BN has participated in the veto and isn't just going to blindly vote yes/no to everything and be non-toxic. (Voting no to a veto mediation is NOT being toxic, let's not set any bad precedents).
What happens after a Veto?
This one's rather straightforward. After a veto has been placed, and has been maintained through voting, the mapper is then forced to change the pattern or leave the map to be graved. Who will lift the veto? I'm assuming the original BN. But what if they continue to maintain that the mapper hasn't fully addressed the issue, or the mapper continues to call the veto'ing BN back to recheck without completely fixing the issue?
I want to add two additional rules to flesh out veto mediation scenarios:
- After a veto has been maintained, If the veto'ing BN does not recheck (and/or approve) the changes made to the map one month after the mapper has called them back for a recheck, the veto will be lifted. This will resolve both issues. It allows for mappers to "escape" a veto if the BN is not willing, or has grown tired of enforcing the veto and constantly rechecking the map. However, it also allows the BN time before having to recheck. If the mapper continues to call the BN back without addressing changes adequately, the BN is also welcome to take other requests, ask the mapper to rethink their concepts, and recheck a few weeks later. I think this is fair, as some vetoes for core issues are not fixable without major reworks anyways.
- If the veto'ing BN is removed, any of the BN's who voted "no" in the veto mediation can replace the BN and uphold the veto. If no one wishes to do so, then after 1 month, the veto will be lifted.
How to get into Management Team?
I'm sure a few people (hi Ascendance) will be interested primarily in this. Is there a process to get into Management Team? And what will happen to other aspects of the mapping/modding community? I'm talking about pushing forward new amendments and changes to the Ranking Criteria mainly. (Which is another subset issue). How will people be chosen for this specialized team?
BN Acceptance
Will there be any change to the way BN's are accepted going forward, now that reviews are no longer every 3 months but on a rolling basis? Will activity count be lowered etc...? I'm also interested in changes to selection criteria. Seeing as how this can potentially mean a lot more BN's entering more frequently, (as well as exiting).
Also if someone is rejected, what is the cooldown before they can reapply again?
Another note: I feel severity of a kick should be considered too. For example, BN's kicked for missing too many unrankable elements, or are inactive etc... should not be subject to a 3 month cooldown imo. I feel that for unrankable elements, this suggests the BN needs more training, or isn't thorough enough, but 1-2 months should be enough. For inactivity, well, can't a BN just resign if they know they will get kicked for inactivity? Then they would be able to reapply 2 weeks later. On the other end, I think behavior-related kicks could be 3 months. I think having a flat # of months is not necessary, and you guys could change the cooldown to suit the specific case of the BN being removed. Basically, make cooldowns more case-by-case and not necessarily do 3 months for everyone.