This wiki is archived and useful information is being migrated to the main bzflag.org website
Editing BZFlagWiki:Content Policy
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.
The administrator who locked it offered this explanation: Archived wiki
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 2: | Line 2: | ||
== Overview == | == Overview == | ||
− | The BZFlag wiki is provided as shared informational resource for the player community. | + | The BZFlag wiki is provided as shared informational resource for the player community. It's intended content is factual information regarding the BZFlag game and it's community. To do this it must maintain a level of impartiality when dealing with that content. Bellow is a set of guidelines for users posting articles here. |
== Subjects == | == Subjects == | ||
− | All articles on the | + | All articles on the BZflag wiki MUST have a direct bearing on the game itself. Articles that are not directly related to the game will be removed from the wiki. |
− | + | ||
=== Acceptable Subjects === | === Acceptable Subjects === | ||
The following are acceptable subjects for BZFlag Wiki Articles. | The following are acceptable subjects for BZFlag Wiki Articles. | ||
Line 12: | Line 11: | ||
* Documentation of BZFlag terms and concepts. | * Documentation of BZFlag terms and concepts. | ||
* Documentation of tasks specific to the direct use of the BZFlag source code, or software. | * Documentation of tasks specific to the direct use of the BZFlag source code, or software. | ||
− | + | * Factual historical references of BZFlag , software, source code, and developers. | |
− | + | * General Information about specific maps, and links to there location. | |
− | * Factual historical references | + | * General Information about specific servers, and links to there administration and websites. |
− | * General Information about specific maps, and links to | + | * General Information about server networks, and links to there administration and websites. |
− | * General Information about specific servers, and links to | + | |
− | * General Information about server networks, and links to | + | |
=== Unacceptable Subjects === | === Unacceptable Subjects === | ||
Line 24: | Line 21: | ||
* Advertisements for specific servers, users, or maps. | * Advertisements for specific servers, users, or maps. | ||
− | == Article | + | == Article contents == |
The contents of articles must be presented in an impartial and factual manner. Wiki articles should be considered descriptive of their subjects, and at all times informational. If a statement can not be backed up with facts, it does not belong in the article. If the fact has no bearing on the subject matter in a descriptive way, it does not belong in the article. Some articles will have more or less factual content following these rules. The further away a subject is from the core game, the less information is applicable to the wiki. The page describing the command line options of the BZFS server will have significantly more applicable information then an article on a network of servers will. | The contents of articles must be presented in an impartial and factual manner. Wiki articles should be considered descriptive of their subjects, and at all times informational. If a statement can not be backed up with facts, it does not belong in the article. If the fact has no bearing on the subject matter in a descriptive way, it does not belong in the article. Some articles will have more or less factual content following these rules. The further away a subject is from the core game, the less information is applicable to the wiki. The page describing the command line options of the BZFS server will have significantly more applicable information then an article on a network of servers will. | ||
If the article does not deal directly with the BZFlag software or development process, and needs to reference information that is available on other websites, then the article should simply link to them. This includes items such as server rules, and other information that is elsewhere. | If the article does not deal directly with the BZFlag software or development process, and needs to reference information that is available on other websites, then the article should simply link to them. This includes items such as server rules, and other information that is elsewhere. | ||
− | Articles should not be written to promote or hinder any one specific server, network, group, or person. No statements should be based on opinion | + | Articles should not be written to promote or hinder any one specific server, network, group, or person. No statements should be based on opinion. |
− | + | == Writing style == | |
− | + | As previously stated articles should be written to be descriptive. Personal words like "you", "me", "your", etc.. should not be used, as the wiki is not a conversation. If part of the article is a description of steps of action, then they should simply be described as the action taken, not the actions of the specific user. | |
− | == Writing | + | |
− | As previously stated articles should be written to be descriptive. Personal words like "you", "me", "your", etc.. should not be used, as the wiki is not a conversation. If part of the article is a description of steps of action, then they should simply be described as the action taken, not the actions of the specific user | + | |
== Content Disputes == | == Content Disputes == | ||
− | As the wiki is user edited, conflicts and edits in the contents or articles can and will occur. When an article is changed, the previous author should read the changes and attempt to understand them before taking any action. Users changing articles should leave descriptive comments with the change indicating why they changed the article | + | As the wiki is user edited, conflicts and edits in the contents or articles can and will occur. When an article is changed, the previous author should read the changes and attempt to understand them before taking any action. Users changing articles should leave descriptive comments with the change indicating why they changed the article. If a previous author disputes the changes, they should attempt to work out an amicable solution on the talk page of the article. The use of the Revert function should not be used in haste, it is primarily intended to assist with article vandalism, or when a change blatantly disregards this policy ( no "revert wars ). Users that are unable to work out acceptable content for an article should contact the Project Administrators and be prepared to explain the issue and how the desired content will follow this policy. |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + |