NetSec:Editing policy
Scope
This wiki is dedicated to learning above all else. Anything that's about hacking, security, or coding, including anything that explains those elements of them in-depth is considered on-topic. An article on an Operating System for instance may not be directly correlated with how to hack or keep them secure, but it does give a greater understanding.
We do not have a requirement for reading our wiki. The goal is to explain all topics so those completely inexperienced can learn about any of even the advanced topics with nothing required but aptitude.
Rules
- To avoid abuse, mainspace article creation is disabled for most users. If you would like to create a new article, please do so on your user page and tag it with {{editrequest}}. This will mark it for review and assuming it is within scope and follows policy, it will be moved promptly. This is not to discourage article creation, and all users are urged to not be afraid of creating new articles on new topics.
- Nothing that interferes with or breaks the law including but not limited to copyright violations and attacks on other users or websites is allowed. We are a how-to site for security, not an attack front for personal drama.
- This wiki is not for advertisement. You are allowed to post any source code or how-to's for anything you write that falls into our scope, but anybody obviously pushing their own product or idea for personal gain will have their contributions removed.
- When editing, be as concise as possible. Avoid overcomplicated wording that people can't understand. Opt for password instead of "authentification credential." Avoid repetitive content in favor of making reading easy on the audience.
- This is a professional wiki. A basic command of English is required, so keep edits to the mainspace professional. This means avoid things like bad grammar, swearing, and text speak when editing articles.
- Edit warring, that is the continued reverting of another user, is counter-productive. Don't do it. For clarification: don't revert anybody on an article more than twice in a given day. If you have a problem with a particular persistent editor, instead of fighting in main space and clogging up the history, take it to the talk pages. Either talk with them directly and find out why they're doing it or take it to the article's talk page for a group consensus on the edit.
- Regardless of copyright status and licensing, do not use content from other sources. Add only content you have personally written.
Talk Page Etiquette
Talk pages are venues for discussion on the topic, both for requested edits to the article or the discussion in general. While more lax than what you can post on the mainspace, there are still a few rules to abide by.
- New sections go at the bottom. If this confuses you, just use the [+] at the top of the page next to the edit button.
- Sign all posts by adding ~~~~ to the end. This will print your signature (found in preferences) as well as the date and time.
- The rules about advertising and the law applies to talk pages as well. Don't post for personal gain, and don't talk about how you hacked somebody.
- Don't edit or remove anybody else's comments. This is seen as deceitful and rude. The general rule of thumb is if it's signed, don't touch it.
- Some people prefer to respond to a comment on their own page to keep conversations in one place while others prefer to address a person directly on their page. Either are fine, but keep in mind if you don't at least tell the user on their talk page that you've responded on your own page, they'll likely not get the message. A quick easy way to tell them is simply by tossing {{Talkback}} or {{tb}} on their talk page so they get the message.
- To respond to a comment, add a : below their comment to indent one further than the person you're responding to. For example:
|
Has anybody gotten to read the SQL Injection article yet? -User:Hatter 23 May 2012 (MSK)
|
