GuildWiki talk:Build vetting procedure

This page
I tried to write down accurately the way things are currently handled on the wiki. Note that this describes how things are done but ultimatively, we want this page also to describe how things should be done. But since exactly how they should be done is a currently ongoing debate, please refrain from major edits to this page, going in the direction of "it should be done like this" until we have agreed on a new procedure. Of course all edits regarding language, style, things I forgot about builds and such are ok. --Xeeron 06:49, 9 October 2006 (CDT)

Vetted builds
I'm not entirely sure what kind of system we should use for builds at this point, but I think one thing we could do to improve matters (both now and in the future when we have our shiny new system) is protect all vetted/approved/tested/whatever builds from edits by unregistered users. I've seen several builds that are approved (and therefore shouldn't be changed) end up being pretty drastically altered or vandalised, and generally speaking if these changes are for the worst they're by an unregistered user. Once a build is approved it shouldn't need much alteration, a low level of protection should make things a bit easier to keep track of. --NieA7 10:06, 9 October 2006 (CDT)
 * I'm against it, its unwiki like. Most grammar/spellcheck comes from anons and it's easy to revert &mdash; Skuld 10:13, 9 October 2006 (CDT)
 * I agree with Skuld. If vetting a build grants it immunity from criticism, I don't think that is very good at all. Just look at the 55/SS team. It was vetted under nearly a COMPLETELY different set of attributes and skills, but maintained the same idea. The point of it is that any build no matter how good it is always has room for improvement/constructive alteration. — Jyro X [[Image:Spiteful_Spirit.jpg|25px]] (contribs) 10:16, 9 October 2006 (CDT)
 * I'm thinking in terms of practicalities rather than politics. The B/P Tombs build is an example - from being approved it changed so much that User:Honorable Sarah had to re-write the whole thing more or less from scratch. I'd rather present consistently accurate information than consistently editable information. If a build is to be approved it should have all its spelling and grammar checked anyway, and nobody would be stopping somebody signing up for an account/mentioning the problem on the talk page. I'm not saying that it should be immune from all criticism, far from it - I don't want global protection, just protection from unregistered users. --NieA7 10:23, 9 October 2006 (CDT)
 * Everything you say does make sense and I would approve of this if it was on a typical fan site but I still think it's unwiki-like and anyone that wants to change a build so bad can still register and demolish things just as easily (or improve it). Good thing is that we can always revert it if it goes awry or clean it up if it gets too messy.[[Image:VallenIconwhitesmall.JPG]]  Vallen Frostweaver  07:37, 18 October 2006 (CDT)

Archive?
On the article page it states the below:


 * Re-voting


 * If the build has been sufficiently altered to render old votes invalid, sometimes a new vote is called. To do so, archive the old vote and put up a fresh Rate-a-Build section.

I understand this but don't know how to archive anything. No links were attached to help describe this process either so I'm looking for some direction here on how to accomplish this should the need arise. Thanks.  Vallen Frostweaver  07:40, 18 October 2006 (CDT)