GuildWiki talk:Publish your build

Intriguing, and a seemingly nice compromise.--Nog64Talk 22:48, 4 April 2007 (CDT)
 * Well yeah, if we're ever going to get any of these build policies off the ground we're going to have to reach a compromise. Thanks for taking the time and writing this up Vazze, a friend and I were doing something very similiar to this as a policy suggestion. This looks generally good. Needs to be expanded a bit more, but a good start. Isis In De Nile 23:58, 4 April 2007 (CDT)

Navigation
Here is something; John Doe wants to look over all Original Builds that have to do with Necromancers. However, this would require John Doe to go through journal after journal (which are all listed on the library) to look at each one individually. There should be some framework in which John Doe, if he chooses, to have access to all Necromancer builds that exist within all the journals. Just a small point raised here. Isis In De Nile 00:19, 5 April 2007 (CDT)
 * A build type [GvG,HA..Farming...Running]  X    profession [Mo, N...Team]) table that contains links to build directories in different libraries will probably help. As long as there are less than say 3-5 links for a given combination, this is ok. The idea is to decentralize the builds section to ease the load on the management side, creating pages that combine libraries goes the opposite direction.--Vazze 13:14, 5 April 2007 (CDT)

And how is this different from the system that is already in place? We are going to experience the same problems. =| Caramel Ni 13:17, 5 April 2007 (CDT)
 * We? No, perhaps the editors, but since the library is in their userspace, they can solve their problems very efficiently, or if they don't, you just stop visiting that page, and use another library. --Vazze 13:50, 5 April 2007 (CDT)
 * So this is a variation of GW:NOB where no build section exists? In NOB popular, well known, succesfull builds are allowed in the build name space and everything else is allowed in the user name space, hoping that some nice rules will be created by users for their own user name space to be used for original builds. --[[Image:Gem-icon-sm.png]] (gem / talk) 14:02, 5 April 2007 (CDT)


 * Ahh, thanks for the help. I thought you were talking about having just ONE library. But also, don't you think it will use alot of server space with each person having their OWN library, holding builds that hundreds of other people already have listed? or is the suggestion that it just links? Caramel Ni 14:21, 5 April 2007 (CDT)


 * I think that there wont be too much same builds in the user name spaces as all popular builds are documented in the build name space. Remember that even now with the old policy people have their own builds in their name space. This system would just allow users to categorise all builds and build ideas in their user name space to easy-to-search categories.
 * The reason why I like the idea of allowing users to post builds in any user name space (if the name space owner has rules for posting builds in his/her name space) is that users may select freely which rules they want to follow as different name space owners will surely have different rules for veting/deletion etc. --[[Image:Gem-icon-sm.png]] (gem / talk) 14:28, 5 April 2007 (CDT)
 * I did not specify whether builds or build links should be submitted to editors. If it is build link only, and the editor trusts the author that he/she will keep updating the build but he/she will not make substantial changes, it can be good for the editor. However, some editors might want to update builds themselves or with their team. Build size (kB) may also present some problems for the editor. But I think the best thing is not to define the way builds are stored on the editor pages (it is user name space after all). --Vazze 14:59, 5 April 2007 (CDT)
 * I think it's up to the user who allows others to post in his user name space to decide what the rules are. For example someone might say that anyone can submit a build, but if the user name space owner has an opinnion on the build, his changes may not be reverted. Another one might implement a vetting system of some kind and so on. --[[Image:Gem-icon-sm.png]] (gem / talk) 15:15, 5 April 2007 (CDT)