Changes: GuildWiki:Builds

Revision as of 21:48, 8 October 2006

NOTE: This is a currently proposed policy, per the guidelines set out in GuildWiki:Policy. If consensus is reached in the talk page, this notice can be removed and the policy category can be added.

Creating a build and rating it is a complicated process, which consists of three parts: creation, nomination and voting.

Creation

A Build Stub is initially created.
Build Stub is worked on by author(s).
Build Stub author leaves a note on talk page indicating he feels it's finished.

Nomination

Any non-author(the nominator) visits the build stub, and evaluates the build for it's written quality and content.
The nominator then sees if the style is correct, which is defined in the article GuildWiki:Style_and_formatting/Builds. If this is not so, the nominator may not continue before this is amended.

Note that if a nominator decides not to continue and leaves a notice on the talk page, another nominator can override this and nominate the build stub anyway.

Testing

The Untested Build is commented on and voted on. During this process the autor may refine the notes; if he decides to change the build however, he or any other contributor is allowed to call for a re-vote. In such a case, the current vote should be archived, and the voting can start fresh.
After a minimum of four votes, the build is moved to Favored/Neutral/Unfavored. A build that has an excess of three positive votes will be favored, and a build with an excess of three negative votes will be unfavored. This will be unbalanced when the number of votes increases too much, so for every ten votes an additional excess vote will be required (though this will rarely happen)

Deletion Process before Testing is Completed

Any Build Stub or Untested Build will be flagged for deletion two weeks after the last modified Article or Article Talk date. At this point, it is assumed abandoned. If this is not so, a contributor may remove the tag and continue editing the page. (If no addition is made, not even an explanation of the removal, someone may revert that action.)
Any Build Stub/Untested Build will be deleted two weeks after the Delete tag is added.

Voting Criteria

The Build functions as written.
The Build has significant differences with other Builds.
The Build functions comparably to other Builds with a similar purpose and using the same Primary Profession that require a similar level of expertise to use.

Note that before voting:

a voter must have read all the comments.
he must have tried the build in-game if he is casting a positive vote, and preferably if he is castin a negative vote as well.
he may not personally attack the author or other voters.
he should take into account the criteria that define a build as good or bad, and preferably refer to the one(s) he thinks are not met.

Notes

If this policy is implemented, some more explanation and wikilinks should be added.

@@ Line 7: / Line 7: @@
 #A Build Stub is initially created.
 #Build Stub is worked on by author(s).
-#The author adds three links to the talk pages of the builds he has voted upon. [[GuildWiki Talk:Builds#Three_to_One|*]]
 #Build Stub author leaves a note on talk page indicating he feels it's finished.
@@ Line 13: / Line 12: @@
 #Any non-author(the nominator) visits the build stub, and evaluates the build for it's written quality and content.
 #The nominator then sees if the style is correct, which is defined in the article [[GuildWiki:Style_and_formatting/Builds]]. If this is not so, the nominator may not continue before this is amended.
-#The nominator checks the votes, to see if they were made seriously, and not rushed for the sake of getting the build through the nomination process.[[GuildWiki Talk:Builds#Three_to_One|*]]
 *Note that if a nominator decides not to continue and leaves a notice on the talk page, another nominator can override this and nominate the build stub anyway.