by natty dread on Sat Dec 31, 2011 11:08 am
Ok, I want to clarify a few things I've said in this thread.
Of course, the CA:s and the Foreman have to monitor the standards of the maps in the foundry. They have a thankless job, everyone always complains when they have to make hard decisions. So if the CA:s/Foreman are of the opinion that some map isn't suitable for CC, or doesn't fulfill the foundry standards, then they absolutely do have the right to stop that map from being developed.
All I'm saying is, that the CA:s and Foreman should try to use good judgement, and watch out that they don't misuse this power. Blocking a map should only be used in extreme cases. I don't mean that the CA:s and Foreman should not have the power to do it at their discretion, they absolutely should, that's what they're in their jobs for. However, what I'm saying is, they should be careful not to take it too far, to a level where mapmakers and foundry commentators start to get the feeling that their opinions don't matter, that their feedback is irrelevant. That's all I'm saying.
I mean, it's also up to the foundry regulars to uphold the standards, and ideally I think the CA:s and Foreman should work together with the foundry community towards making the best decisions, and the best maps, for the foundry. The ultimate authority should of course always be within the CA:s and, ultimately, the Foreman. They should have the right to pull the plug on a map if they so choose, even if people complain about the decision. I mean, ideally, I think the CA:s and Foreman should interact with the community, and try to guide the process so that they - most of the time - don't have to resort to decisions like that. But when the situation calls for it, then they should absolutely do it.
These are all my opinions and how I feel the foundry process should ideally work. They may not reflect the views of the CA:s or Foreman or how the process actually works.