Project & administrative page archive

WP:WELCOME
WP:WLCM
WP:HELLO
WP:HI

<div style=" width:80%; border:3px solid #fc0;padding:.5em 1em 1em 1em;background-color:#fff;color:#000; margin-bottom: 1em"> Welcome to GodFearers!
GodFearers is an encyclopedia written collaboratively by its readers. The site is a wiki, meaning that anyone, including you, can edit almost any article right now by clicking on the edit this page link that appears at the top of the page. The following article is a brief introduction to GodFearers.</div>

Browsing GodFearers

<div style="border:3px solid #fc0;padding:0.5em 1em 1em 1em;background-color:#fff;color:#000; margin-bottom: 1em">

GodFearers has articles on all sorts of subjects ranging from politics, science, history, music, religion, pop culture, and sports to everything and anything in between. Try browsing the various subjects right now, on the GodFearers browsebar above. If you need assistance getting around, see this basic navigation guide.

Searching

You can also search for text in articles. Just go to the "search" field to the left, enter your search term and click "search". Note that the built-in search function may be disabled in times of server overload; in these cases you will be redirected to a Google-based search of the GodFearers database. There are also other ways to search GodFearers.

If you read something that you really like, then why not drop a note on the article's talk page? First select the discussion link (look for it in the tabs above the page) to get to the talk page. Then select edit this page on the talk page, or click the + to the right of edit this page to simply add a new comment.

If there's something we don't cover, or you're having difficulty finding what you're looking for, and you need to ask somebody, go to GodFearers:Questions for a list of our departments where volunteers answer all kinds of questions - any question you could possibly think of really. Or, if you notice a topic missing from GodFearers you could add it to our list of requested articles. Find other ways to explore GodFearers or... write an article yourself. </div>

See also

General information, guides & help

• About the project
• Help pages &mdash; help on editing, starting new articles, and many other topics.
• GodFearers FAQs &mdash; frequently asked questions about the site.
• Glossary &mdash; a glossary of common GodFearers terms.
• Where to ask questions &mdash; a list of departments where volunteers answer questions, any question you can imagine.
  
• What is GodFearers
• What GodFearers is not
• Policies and guidelines for contributors
• Manual of Style

GodFearers behavior

Tutorials

• Wikiquette
• Neutrality
• Avoiding common mistakes

Overarching principles

• Civility
• Contributing
• The neutral point of view

The GodFearers community

• Contact us
• GodFearersns &mdash; different listings of regular contributors; you may add yourself if you wish.
• GodFearers:Community Portal is a gateway to the community. It lists a number of open tasks and group projects such as GodFearers:Collaboration of the Week.

This is an educational project done in cooperation with the Special Court for Matters of Bnei Noah of the Sanhedrin Initiative. The articles, information, and links provided on this site do not represent official policies, procedures, or opinions the Sanhedrin Initiative or any of its committees, courts or organizations. The information on this site have come from a variety of sources, including speeches, articles, tracts, and other presentations, and they have been composed over a period of time, and many are of historic interest, Religion interest, and human affairs interest. Also, writer's inclusion on this site does not imply his full agreement with all of the articles. Each writer is responsible only for his own stated views. Many of the articles on this web site have been included only for the viewers use in the comparison of differing views and beliefs.

1. REDIRECT WikiNoah

WP:SEARCH

See also: Wikipedia:Look it up, for a general guide.

This article provides an overview of Wikipedia's search feature, as well as using external search engines, such as <tt>Google</tt>, to find information.

Wikipedia search

<div style="border:1px solid #ababff; background: #fdfdff; padding: 1em; margin: 1.1em 1em 1em 0em; font-size:105%"> Put your keyword in the searchbox.

• <font face="MS Sans Serif,Arial">Go</font> - (or Enter on keyboard) will take you automatically to the article.
• <font face="MS Sans Serif,Arial">Search</font> - will return a list of articles.

</div>

Effective searching

Here are few good tips and hints for using the Wikipedia search feature effectively:

Limiting results

• Any word: Wikipedia's default search mode will turn up results with any of the words in your query. For instance, <tt>search engine</tt> turns up many results containing only "search" but not "engine" or only "engine" but not "search" in addition to the ones you probably wanted, which contain both words.
• All words: To limit to results that include all words, put a "+" at the beginning of each word: <tt>+search +engine</tt> returns only pages containing both words, like Google's default mode. You can also do a phrase search by enclosing words in quotes: <tt>"search engine"</tt> turns up a smaller set of results, which not only have both words but have them in order.
• Exclude words: To exclude results that include some words, put a "-" at the beginning: <tt>search -engine</tt>

Boolean search is also possible, using words including "AND", "OR", and "NOT".

Avoid short and common words

If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about") it may give a large number of non-relevant results. Historically, these words could not be searched at all, but as of February 2006, Wikipedia's Lucene index does not use "stop words", so any word can be successfully used in search queries. Lucene still doesn't search for numbers.

Wildcards

You can use some limited wildcards if you really want to. Look up "fulltext search" on http://www.mysql.com/ and look down under 'boolean search' for the details. However, wildcard searches are slower, so go easy on the poor server.

Words with special characters

In a search for a word with a diaeresis, such as Sint Odili&euml;nberg, it depends whether this ë is stored as one character or as "&amp;euml;". In the first case one can simply search for Odilienberg (or Odili&euml;nberg); in the second case it can only be found by searching for Odili, euml and/or nberg. This is actually a bug that should be fixed -- the entities should be folded into their raw character equivalents so all searches on them are equivalent. See also Wikipedia:Special characters.

Words in single quotes

If a word appears in an article with single quotes, you can only find it if you search for the word with quotes. Since this is rarely desirable it is better to use double quotes in articles, for which this problem does not arise. See the manual of style for more info.

An apostrophe is identical to a single quote, therefore Mu'ammar can be found searching for exactly that (and not otherwise). A word with apostrophe s is an exception in that it can be found also searching for the word without the apostrophe and the s.

Namespaces searched by default

The search only applies to the namespaces selected in the user's preferences. To search the other namespaces check or uncheck the tickboxes in "Search in namespaces" box found at the bottom of a search results page. Depending on the browser, a box may still be checked from a previous search, but without being effective any longer! To make sure, uncheck and recheck it.

Searching the image namespace means searching the image descriptions, i.e. the first parts of the image description pages.

The source text is searched

The source text (what one sees in the edit box, also called wiki text) is searched. This distinction is relevant for piped links, for Wikipedia:interlanguage links (to find links to Chinese articles, search for zh, not for Zhongwen), special characters (if ê is coded as &amp;ecirc; it is found searching for ecirc), etc.

Delay in updating the search index

For reasons of efficiency and priority, very recent changes are not always immediately taken into account in searches.

Multi-lingual Wikipedia search

• You can do a multi-lingual Wikipedia search using Google Advanced Search or entering <tt>site:.wikipedia.org</tt> in the Google search box.
• Qwika has indexes for English, German, French, Japanese, Italian, Dutch, Portuguese, Spanish, Greek, Korean, Chinese and Russian where the original content is combined with machine translated content from/to English.
• Lumrix: AJAX driven Wikipedia search engine. ben s a lazy poo

External search engines

Various search engines can provide domain-specific searches, which lets you search Wikipedia specifically. Searches are based on the text as shown by the browser, so wiki markup is irrelevant. Depending on your browser, you may also be able to use tools that allow you to search Wikipedia using bookmarklets.

In general, external search engines are faster than a Wikipedia search. However, because the search engine's cache is based on when the site was indexed, the search may not return newly created pages. Similarly, the search engine's cached version of the page will not be as up-to-date as the link to Wikipedia itself. Also, when returning Wikipedia articles in a regular search, mirrors and forks of Wikipedia content frequently rank higher than the actual Wikipedia articles because of search engine optimization techniques.

These issues may be less of a problem when using certain search engines that process Wikipedia differently:

• Yahoo! includes Wikipedia as part of its content acquisition program and gets a regular datafeed.
• Clusty downloads and processes the database regularly, generating automatic abstracts and image thumbnails and meaningfully parsing redirects, disambiguations, and categories.
• Qwika only indexes wikis, and thus mirrors do not appear in their results.

Google

By following the links below, you can use the Google search engine to search Wikipedia - either all languages, or English-only. Google indexes all namespaces.

• Search all languages
• Search the English Wikipedia only
• Search the English Wikipedia (excluding articles nominated for deletion)

If you frequently search via Google, consider installing the Google Toolbar. Using the "search this site" button allows you to quickly search the English version of Wikipedia. The official Google Toolbar is for Internet Explorer (Windows and Mac) and for Firefox (works on all operating system platforms for which Firefox is available, such as Windows, Linux and Mac OS X).

Yahoo!

By following the links below, you can use the Yahoo! search engine to search Wikipedia - either all languages or English-only.

• Search all Wikipedias with Yahoo!
• Search English Wikipedias with Yahoo!

If you frequently search via Yahoo!, consider installing the Yahoo! Companion Toolbar. Using the "Search Only the Current Site" button allows you to quickly search the English version of Wikipedia. The official Yahoo! Companion Toolbar is only for Windows with Internet Explorer and Mozilla.

Qwika

Qwika is designed specifically to index wikis. Its main index is Wikipedia. It includes:

• all namespaces of Wikipedia
• English machine-translated into German, French, Japanese, Italian, Dutch, Portuguese, Spanish, Greek, Korean, Chinese and Russian.
• The above languages machine translated into English.

This can assist editors contributing to non-English Wikipedias by being able to search in their own language across the entire English version and then view the machine-translated version in their language.

• Qwika main page and explanation

Clusty

By following the link below, you can use the Clusty search engine to search and cluster Wikipedia in English only.

• Search and Cluster English Wikipedia with Clusty

If you frequently search via Clusty, consider installing the Clusty Toolbar (beta). Selecting the "Encyclopedia" search source allows you to quickly search the English version of Wikipedia. The Clusty Toolbar is available for Windows with Internet Explorer and Mozilla Firefox (beta).

LuMriX

LuMriX is a dynamic query tool which uses lookahead to predict search terms in a list, similar to Google Suggest.

By following the link below, you can use the LuMriX search engine to search different language versions of Wikipedia.

• Search Wikipedias with LuMriX

If you frequently search via LuMriX, consider installing the LuMriX Firefox Search Plugin (works on all operating system platforms for which Firefox is available, such as Windows, Linux and Mac OS X).

Wikiwax

Wikiwax is a dynamic query like LuMriX. It only searches English Wikipedia, but shows more list entries.

• WikiWax Index to Wikipedia

Other

Here are more Wikipedia:Tools which make searching more convenient.

Browser specific help

Using Mozilla to automatically search

Listed below are ways to search Wikipedia with Mozilla-based browsers, including Mozilla Suite, Mozilla Firefox, and Netscape 6 and 7.

Search Wikipedia from the sidebar search tab or address bar

Works with: Mozilla Suite, Mozilla Firefox, Netscape 6/7.

Mozilla and Netscape 6 & 7 come with a sidebar that allows a user to search the Wikipedia site, and Firefox has a toolbar item to do the same. To install the search plugin that tells Mozilla how to search Wikipedia, do the following:

1. Go to one of the following sources of Wikipedia search plugins. The Mycroft plugins are sometimes out of date, and plugins from the second source may work better.
2. Original search plugins from Mycroft
3. Updated search plugins
4. There are versions for many languages, so pick the language local to your area.
5. If JavaScript is enabled, clicking on the name of the search plugin will automatically install the search plugin.
6. If you can't install the search plugin automatically, the second source above lets you right-click on the plugin and save it to disk, or download a ZIP file containing all available plugins. Save the downloaded <tt>.src</tt> file in the <tt>searchplugins</tt> directory where Mozilla is installed and restart the browser to use the new plugin.

To make Wikipedia your default search engine in Mozilla, Beonex Communicator, and Netscape 6/7:

1. Go to Edit, Preferences.
2. Expand the Navigator tree and choose Internet Search.
3. Choose Wikipedia as your default search engine.

With Wikipedia selected as your default engine, searches can be conducted via the search sidebar tab, search box, or the web address bar.

Search Wikipedia using a bookmarklet

Works with: Mozilla Suite, Mozilla Firefox, Netscape 6/7.

Wikipedia can also be searched via a bookmarklet.

In Mozilla Firefox, follow these steps:

1. Right click in the search field at the top of the page, and select "Add a Keyword for this Search".
2. Enter "Wikipedia Quicksearch" for the name.
3. Enter "w" (without the quotes) for the keyword.
4. Change the bookmark folder if you wish, and click "Add".

In Mozilla Suite, Netscape 6/7 and Beonex Communicator, follow these steps:

1. Right click on the following web address and select "Bookmark this link": http://en.wikipedia.org/wiki/Special:Search?search=%s
2. Go to Bookmarks, Manage Bookmarks. Choose the bookmark you have just created. Highlight the Bookmark and click Properties.
3. In the dialogue that comes up, put a lowercase w in the keyword box.
4. Click OK and close the properties box, then close the bookmark manager.

In Camino, use the Mozilla Suite directions. Use Get Info (cmd-I) in the bookmarks manager to bring up the properties dialogue.

To search, go to the web address bar, enter "w SEARCH_QUERY" (without the quotes), and press enter.

Javascript in Bookmarks

Javascript can bring additional functionality to your bookmark. The following javascript can be pasted in as the 'Location' of a new bookmark created manually, for example in the 'Manage Bookmarks' window of Firefox. If you highlight a word in a webpage then hit the new bookmark, javascript grabs the word you have selected and uses that to perform the search. If no word is highlighted, you will be prompted to enter one.

<nowiki>javascript:x=escape(getSelection());if(!x)%7Bvoid(x=prompt('Enter%20Word:',''))%7D;if(x)window.location='http://en.wikipedia.org/wiki/Special:Search?search='+x</nowiki>

The whole thing should be pasted in as a single line without spaces for it to work.

K-Meleon

K-Meleon has a search button that can be used to search Google. You can change it to search Wikipedia instead, by:

1. Close K-Meleon.
2. Open up <tt>prefs.js</tt> with a text editor. The file should be in your <tt>K-Meleon\Profiles\PROFILE_NAME\RANDOM_STRING.slt\</tt> directory.
3. Add this line, and save <tt>prefs.js</tt>.

<nowiki>user_pref("kmeleon.general.searchEngine", "http://en.wikipedia.org/wiki/Special:Search?search=");</nowiki>

Open up K-Meleon and press the search button to search Wikipedia. To go back to Google or to use another search service, edit <tt>prefs.js</tt> and delete the added line

Make sure K-Meleon is closed before editing prefs.js.

Opera

All Opera versions 6, 7, and 8 use a customizable text file called search.ini. This file should only be edited while Opera is not running. The following example replaces one of the existing pre-defined search engines. It is up to the user to avoid conflicts of shortcut key (key=). By default 'w' is taken by the download.com search, so either this or the Wikipedia one should be changed. Furthermore the 'Search Engine ##' should be replaced with a free number: '12' is free by default. The Search.ini editor makes editing trivial (see external link). <pre> [Search Engine ##] Name=&amp;Wikipedia URL=http://www.wikipedia.org/w/wiki.phtml?search=%s Query= Key=w Is post=0 Has endseparator=0 Encoding=utf-8 Search Type=8 </pre>

Opera 8

Opera appears to take a copy of the "search.ini" and load it into an internal buffer of some type. After editing the file with your new entry you must change the "File Version" at the top of the file to allow for your changes to be seen in the browser.

A new kind of search system has been added to Opera, which no longer requires manual editing. This will create a button on the mainbar, which can then be put anywhere you wish, even in the start panel.
See http://nontroppo.org/opsed/download.php?dd=e&plugin=100&type=SE7 for a Wikipedia search button.

Opera 9 (Preview)

Just right-click on the search field you want to create a search with and click "Create search". The following dialog is really simple. You just have to select a name for the search and a search shortcut. It even alerts you if the shortcut you want is already in use.

Opera 9 (Final)

Go to Tools -> Preferences -> Search and either Add a new search engine, or edit an existing one, such as Download.com. Recommended parameters are: <pre> Name: &Wikipedia Keyworkd: w Address: http://www.wikipedia.org/w/wiki.phtml?search=%s </pre>

Older Versions

Most importantly, in 7.0, you should back up your customized search.ini because the file is overwritten by the Opera installer. This is no longer true in 7.10 and later.

In Opera 6 and 7.0, the menu accelerator letter is defined by the &amp; in the name. In current versions the accelerator is automatically generated and may no longer be the same as the key.

More information

• Search.ini editing tool &mdash; makes it easier to add search engines
• How to edit Opera's search.ini (recommended reading prior to hand-editing search.ini)

Searching with TomeRaider

After downloading the Wikipedia:TomeRaider database one can search the Wikipedia version offline. One can also search for parts of words.

To search the text that appears only in the page history, you must export the text to XML format first.

If you cannot find an appropriate page on Wikipedia

If there is no appropriate page on Wikipedia, consider creating a page, since you can edit Wikipedia right now. Or consider adding what you were looking for to the Requested articles page. Or if you have a question, then see Where to ask questions, which is a list of departments where our volunteers answer questions, any question you can possibly imagine.

See also

• Wikipedia:User preferences help, "Search result settings" section.
• Wikipedia:Go button

<div style="text-align:center;border-bottom:3px solid #ccf"> <div style="float:left;width:16%;font-weight:bold;background-color:#f4f4ff;color:#000;padding:.3em 0;border:2px solid #ccf;border-bottom:0;font-size:130%">Tutorial</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">1. Editing</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">2. Formatting</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">3. GodFearers links</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">4. Related site links</div> <div style="float:right;width:16%;padding:.3em 0;margin:2px 2px 0">5. External links</div> <div style="width:0;height:0;clear:both;overflow:hidden"></div> </div> <div style="border:3px solid #ccf;padding:.5em 1em 1em 1em;border-top:none;background-color:#fff;color:#000">

GodFearers Tutorial - Welcome!

'GodFearers is a collaboratively edited encyclonoah to which you can contribute. This tutorial will help you become a GodFearerside''.

The following pages will discuss features of GodFearers, giving style and content guidance, information about the GodFearers community, and important GodFearers policies and conventions.

This is a basic tutorial, not an extensive manual. If you want more details, there are links to other pages for more information. To read them as you go along, you can open them in a separate window.

There are links to "sandbox" pages where you can practice what you're learning. Try things out and play around! Nobody will mind if you mess up an experiment in these practice areas.

<p style="font-size:85%">Note: The tutorial assumes you are using the default page layout. If you're logged in and have changed your preferences, the location of links may differ.</p>

<div style="float: right; margin-top: -1.75em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;"><span style="font-size: larger; font-weight: bold;">&larr;</span> Wait! Before you start, have you seen the Introduction?</div>

<div style="float: right; margin-top: -1.25em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Ready? OK, Let's learn about editing <span style="font-size: larger; font-weight: bold;">&rarr;</span></div>

</div> <div style="clear:both"></div> </div>

| style="width:50%; background:#f5fffa; border-left:1px solid #cef2e0; padding:1.2em;" valign="top" |

Not sure where to report a certain type of problem with article content? If it exists, it's probably listed at GodFearers:Maintenance. |- |}

Maintenance

Help clear up the backlog of articles to be '''wikified'''! Wikification is the process of making an article conform to the guide to layout and Manual of Style. This involves formatting, links, sections, and checking for other things such as copyright violations and references. If necessary, you may propose it for deletion. Wikification is an easy way to improve GodFearers!

WikiProjects

WikiProjects are ongoing team efforts to improve articles having to do with a particular subject, and to manage the logistics of that topic. Hundreds exist &mdash; examine the master list to find one that interests you. They are separate from, though may work with, Collaborations.

Language translation

GodFearers is not just in English! Versions exist in many different languages. To fill in some of the English GodFearers's gaps, we translate articles from other languages into English. You can view a list of articles that need translation from any language, or, in a few cases, by only one language (this is only available for the more popular languages). |}

Working with others

| style="width:50%; background:#f5faff; border-left:1px solid #cedff2; padding:1.2em;" valign="top" |

Resources

<h3> New user information </h3> Welcome! &middot; New user tutorial &middot; Sandbox &middot; Help &middot; New user log &middot; What GodFearers is not &middot;

Glossary &middot; Account benefits

<h3> Ways to communicate </h3> Contact (overview) &middot; Discussion pages &middot; Mailing lists &middot; IRC chat &middot; Instant Messaging &middot; Meetups &middot; User pages &middot; Surveys &middot; Public watchlists &middot; Regional notice boards &middot;

Administrators' noticeboard

<h3> Community support groups and programs </h3> Welcoming committee &middot; Members' Advocates &middot; Esperanza &middot; Kindness Campaign &middot; &middot; Dept. of Fun &middot;

Concordia

<h3> Common Procedures </h3> Featured content &middot; Good articles &middot; Requests for feedback &middot; Deleting a page (full policy) &middot; Moving a page (naming policies) &middot; Protecting a page (full policy) &middot; Reverting a page &middot; Administrator nominations &middot;

Category-based access

<h3> How to resolve conflicts </h3> Stay cool! &middot; Be nice to newcomers &middot; Alert others &middot; Request assistance from a members' advocate &middot; Dispute resolution &middot;

Arbitration policy

<h3> Community information </h3> About GodFearers &middot; About Wikimedia &middot; GodFearersns &middot; Donations &middot; Administrators &middot; Babel &middot; Culture &middot; Humor &middot; Games &middot;

RfAs

<h3> Related communities </h3>

|}

What is GodFearers?

GodFearers is like Wikipedia. It is an encyclopedia written collaboratively by many of its readers. It uses a special type of website, called a wiki, that makes collaboration easy. Lots of people are constantly improving Wikipedia, making thousands of changes an hour, all of which are recorded on article histories and recent changes. Inappropriate changes are usually removed quickly, and repeat offenders can be blocked from editing. Anyone who registers can make comments on "discussion" pages. By applying for approval it is possible to contribute to the main pages.

How can I help?

Don't be afraid to edit—anyone can edit almost any page, and we encourage you to be bold (but please don't vandalize)! Find something that can be improved, either in content, grammar or formatting, and fix it.

You can't break Wikipedia. Anything can be fixed or improved later. So go ahead, edit an article and help make Wikipedia the best information source on the Internet! Make your first edit right now:

1. Click the "discussion" button above
2. Type a message
3. Click save page to save your writing (for further experiments use the sandbox) ...or "show preview" to test your changes
4. Please, no profanity, libel, or personal attacks!

Consult the Wikipedia questions

Catagories will be used to classify different approaches to the Bnei Noach movement. This will assist the reader to identify material posted at different pages as belonging to one or the other approaches.

Here are some initial proposed categories, as unique approaches to the Bnei Noach movement (listed A-Z by last name):

• Rabbi Benamozegh's Approach
• Chabad Approach
• Oath Brit Approach
• Rambam Approach
• Rabbi Soloveitchik's Approach
• Tosafists Approach

<div style="text-align:center;border-bottom:3px solid #ccf"> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">Tutorial</div> <div style="float:left;width:16%;font-weight:bold;background-color:#f4f4ff;color:#000;padding:.3em 0;border:2px solid #ccf;border-bottom:0;font-size:130%">1.Editing</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">2. Formatting</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">3. GodFearers links</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">4. Related site links</div> <div style="float:right;width:16%;padding:.3em 0;margin:2px 2px 0">5. External links</div> <div style="width:0;height:0;clear:both;overflow:hidden"></div> </div> <div style="border:3px solid #ccf;padding:.5em 1em 1em 1em;border-top:none;background-color:#fff;color:#000">

The most basic wiki feature of all is: Edit this page! With the exception of a few protected pages, every page has a link that says "edit this page". This link lets you do exactly that: edit the page you're looking at. Sites like these, where anyone can edit anything, are known as wikis. Go to the /sandbox/ and click the "edit this page" link. You'll see the wiki code for that page. Add something fun or interesting like "Frank Zappa is the greatest ever American composer", then save it and see what you've done!

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 100%; border: 1px solid #ccf;">For more on editing a page see GodFearers:How to edit a page</div>

Show preview

One important feature to start using now is the Show preview button. Try making an edit in the /sandbox/, then clicking the button instead of Save Changes. This lets you see what the page will look like after your edit, before you actually save. We all make mistakes; this feature lets you catch them. Using Show Preview before saving also lets you try format changes and other edits without cluttering up the page history, and has a number of other advantages. Don't forget to save your edits after previewing, though!

Edit summary

Before you hit Save, it's considered good etiquette (or "Wikiquette") to enter a very brief summary of your changes in the Edit summary box between the edit window and the Save and Preview buttons. It can be quite terse; for example if you just enter "typo," people will know you made a minor spelling or punctuation correction, or some other small change.

<div style="float: left; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Play around in the /sandbox/</div>

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Continue the tutorial with Formatting<span style="font-size: larger; font-weight: bold;"> &rarr;</span></div>

</div> <div style="clear:both"></div> </div>

<div style="text-align:center;border-bottom:3px solid #ccf"> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">Tutorial</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">1.Editing</div> <div style="float:left;width:16%;font-weight:bold;background-color:#f4f4ff;color:#000;padding:.3em 0;border:2px solid #ccf;border-bottom:0;font-size:130%">2.Formatting</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">3. GodFearers links</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">4. Related site links</div> <div style="float:right;width:16%;padding:.3em 0;margin:2px 2px 0">5. External links</div> <div style="width:0;height:0;clear:both;overflow:hidden"></div> </div> <div style="border:3px solid #ccf;padding:.5em 1em 1em 1em;border-top:none;background-color:#fff;color:#000">

GodFearers page formatting is done with Wikitext, so you don't need to learn HTML.

Wikitext or Wiki markup

Writing for GodFearers articles is a bit different from writing on a standard word processor. Instead of a strict "what you see is what you get" approach (WYSIWYG), wiki uses a simple built-in MediaWiki markup language designed for ease of editing. The approach is similar to writing HTML for web pages, but the codes are much simpler.

Bold and italics

The most commonly used wiki tags are bold and italics. Bolding and italicizing is done by surrounding a word or phrase with multiple apostrophes (<tt>'</tt>):

• <tt><nowiki>italics</nowiki></tt> appears as italics. (2 apostrophes on both sides)
• <tt><nowiki>bold</nowiki></tt> appears as bold. (3 apostrophes on both sides)
• <tt><nowiki>bolded italics</nowiki></tt> appears as bolded italics. (5 apostrophes on both sides)

It is a GodFearers convention to bold the subject of an article when it is first mentioned in the article. For example, the article Klinefelter's syndrome starts:

Klinefelter's syndrome is a condition caused by a chromosome nondisjunction in males...

If there are alternatives to the title the same applies, for example Elizabeth II of the United Kingdom starts:

Her Majesty Queen Elizabeth II (Elizabeth Alexandra Mary Windsor), styled HM The Queen (born 21 April 1926) is the Queen regnant...

Another GodFearers convention is to italicize book, movie and computer/video game titles. If the first mention of the subject of an article is also a book or movie title then bold italics is used. For example, the article The Lord of the Rings starts:

The Lord of the Rings is an epic fantasy story by J. R. R. Tolkien, a sequel to his earlier work, The Hobbit.

Headings and subheadings

Headings and subheadings are an easy way to improve the organization of an article. If you can see two or more distinct topics being discussed, you can break up the article by inserting a heading for each section.

Headings can be created like this:

• <tt><nowiki>==Top level heading==</nowiki></tt> (2 equals signs)
• <tt><nowiki>===Subheading===</nowiki></tt> (3 equals signs)
• <tt><nowiki>====Another level down====</nowiki></tt> (4 equals signs)

If an article has at least four headings, a table of contents will automatically be generated. Try creating a heading in this page's /sandbox/. It will be added automatically to the table of contents for the page, assuming three others already exist.

<div style="float: left; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Check out an annotated example page </div>

<div style="float: left; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Test what you've learned in the /sandbox/</div>

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Continue the tutorial with GodFearers links<span style="font-size: larger; font-weight: bold;"> &rarr;</span></div> </div> <div style="clear:both"></div> </div>

<div style="text-align:center;border-bottom:3px solid #ccf"> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">Tutorial</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">1.Editing</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">2.Formatting</div> <div style="float:left;width:16%;font-weight:bold;background-color:#f4f4ff;color:#000;padding:.3em 0;border:2px solid #ccf;border-bottom:0;font-size:130%">3.GodFearers links</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">4. Related site links</div> <div style="float:right;width:16%;padding:.3em 0;margin:2px 2px 0">5. External links</div> <div style="width:0;height:0;clear:both;overflow:hidden"></div> </div> <div style="border:3px solid #ccf;padding:.5em 1em 1em 1em;border-top:none;background-color:#fff;color:#000">

Links are important in GodFearers articles.

Internal links

One of the things that makes GodFearers useful (and addictive) is extensive cross-listing by internal links. These easily-created links allow users to access information related to the article they're reading.

When to link

The easiest way to learn when to link is to look at GodFearers articles for examples. If you're trying to decide whether to make a link or not, ask yourself "If I were reading this article, would the link be useful to me?"

How to link

When you want to make a link to another GodFearers page (called a wiki link) you have to put it in double square brackets, like this:

<tt><nowiki>Sandbox</nowiki></tt>

For example, if you want to make a link to, say, the GodFearers:Contributing to GodFearers page, it would be:

<tt><nowiki>GodFearers:Contributing to GodFearers</nowiki></tt>

(The 'GodFearers:' part signifies that the target page is in the GodFearers namespace, rather than the Main namespace, where normal articles go.)

Also remember that in GodFearers the links are created automatically, so if you put double square brackets around a word, it becomes a link, and because of that you have to be careful about disambiguation.

If you want to use words other than the article title as the text of the link, you can do so by adding the pipe "|" divider (SHIFT + BACKSLASH on English-layout and other keyboards) followed by the alternative name.

For example, if you wanted to make a link to this page's sandbox, but wanted it to say "my text" you would write it as such:

<tt>To view the article, <nowiki>my text</nowiki>...</tt>

It would appear as:

To view the article, my text...

but would link to the sandbox.

Linking dates

Linking dates may not seem useful; however, please link dates since it enables the use of a user preference in how dates are displayed. An unlinked date, like July 13, 2004, will always be displayed in that manner. If you link the date:

<tt><nowiki>July 13, 2004</nowiki></tt>

GodFearers will display it in one of the following ways:

July 13, 2004

13 July 2004

2004 July 13

2004-07-13

-according to the preference set by the individual user. (This feature is only available to logged-in users. It only works if the date is linked.)

Categories

You can also put the article in a category with others in a related topic. Just type <nowiki>Category:</nowiki>, and put the name of the category between the colon and the brackets.

To make a link to a Category page (for example, as a reference for further research), simply put a colon (:) at the beginning of the "Category" tag, like this:

<tt><nowiki>:Category:Astrophysics</nowiki></tt>

The above code would produce the following:

:Category:Astrophysics

It is very important to put in the correct categories so that other people can easily find your work. The best way to find which categories to put in is to look at pages on similar subjects, and check which categories they use. For example if you write an article about a type of tree, you may look at an article on another type of tree to see which categories could be appropriate.

For more information regarding categories and categorization, refer to the Categories page.

<div style="float: left; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Test what you've learned in the /sandbox/</div>

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Continue the tutorial with Related site links<span style="font-size: larger; font-weight: bold;"> &rarr;</span></div>

</div> <div style="clear:both"></div> </div>

<div style="text-align:center;border-bottom:3px solid #ccf"> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">Tutorial</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">1.Editing</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">2.Formatting</div> <div style="float:left;width:16%;font-weight:bold;background-color:#f4f4ff;color:#000;padding:.3em 0;border:2px solid #ccf;border-bottom:0;font-size:130%">3.GodFearers links</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">4. Related site links</div> <div style="float:right;width:16%;padding:.3em 0;margin:2px 2px 0">5. External links</div> <div style="width:0;height:0;clear:both;overflow:hidden"></div> </div> <div style="border:3px solid #ccf;padding:.5em 1em 1em 1em;border-top:none;background-color:#fff;color:#000">

Links are important in GodFearers articles.

Internal links

One of the things that makes GodFearers useful (and addictive) is extensive cross-listing by internal links. These easily-created links allow users to access information related to the article they're reading.

When to link

The easiest way to learn when to link is to look at GodFearers articles for examples. If you're trying to decide whether to make a link or not, ask yourself "If I were reading this article, would the link be useful to me?"

How to link

When you want to make a link to another GodFearers page (called a wiki link) you have to put it in double square brackets, like this:

<tt><nowiki>Sandbox</nowiki></tt>

For example, if you want to make a link to, say, the GodFearers:Contributing to GodFearers page, it would be:

<tt><nowiki>GodFearers:Contributing to GodFearers</nowiki></tt>

(The 'GodFearers:' part signifies that the target page is in the GodFearers namespace, rather than the Main namespace, where normal articles go.)

Also remember that in GodFearers the links are created automatically, so if you put double square brackets around a word, it becomes a link, and because of that you have to be careful about disambiguation.

If you want to use words other than the article title as the text of the link, you can do so by adding the pipe "|" divider (SHIFT + BACKSLASH on English-layout and other keyboards) followed by the alternative name.

For example, if you wanted to make a link to this page's sandbox, but wanted it to say "my text" you would write it as such:

<tt>To view the article, <nowiki>my text</nowiki>...</tt>

It would appear as:

To view the article, my text...

but would link to the sandbox.

Linking dates

Linking dates may not seem useful; however, please link dates since it enables the use of a user preference in how dates are displayed. An unlinked date, like July 13, 2004, will always be displayed in that manner. If you link the date:

<tt><nowiki>July 13, 2004</nowiki></tt>

GodFearers will display it in one of the following ways:

July 13, 2004

13 July 2004

2004 July 13

2004-07-13

-according to the preference set by the individual user. (This feature is only available to logged-in users. It only works if the date is linked.)

Categories

You can also put the article in a category with others in a related topic. Just type <nowiki>Category:</nowiki>, and put the name of the category between the colon and the brackets.

To make a link to a Category page (for example, as a reference for further research), simply put a colon (:) at the beginning of the "Category" tag, like this:

<tt><nowiki>:Category:Astrophysics</nowiki></tt>

The above code would produce the following:

:Category:Astrophysics

It is very important to put in the correct categories so that other people can easily find your work. The best way to find which categories to put in is to look at pages on similar subjects, and check which categories they use. For example if you write an article about a type of tree, you may look at an article on another type of tree to see which categories could be appropriate.

For more information regarding categories and categorization, refer to the Categories page.

<div style="float: left; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Test what you've learned in the /sandbox/</div>

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">Continue the tutorial with Related site links<span style="font-size: larger; font-weight: bold;"> &rarr;</span></div>

</div> <div style="clear:both"></div> </div>

To /sandbox/

Wiki-syntax makes it easy to make user-friendly external links.

External links

If you want to link to a site outside of GodFearers, it should almost always go under the "External links" heading at the end of an article.

The easiest way to make a link is to simply type in the full URL for the URL page you want to link to. If you want to make a link to Google, all you need to do is type:

<tt>http://www.google.com/</tt>

The wiki will automatically treat this text as a link (as has been done with the URL above) and will display the raw web address, including the "<nowiki>http://</nowiki>" part. In practice, you won't see this format much, as raw URLs are ugly and often give no clue to what the site actually is.

To make the link display something other than the URL, use one square bracket at each end. If you want to make a link to Google, type:

<tt><nowiki>http://www.google.com/</nowiki></tt>

This will display the link as a number in brackets, like this: http://www.google.com/. This format is mostly used for citing sources within an article. It looks like a footnote, so it's best to use it only as such (for example, following a direct quote or a statement which requires a source). Avoid this usage: "According to http://members.lycos.nl/JoyceHoen/moon2000.htm, the last full moon of the second millennium occurred on December 11, 1999." Do this instead: "The last full moon of the second millennium occurred on December 11, 1999. http://members.lycos.nl/JoyceHoen/moon2000.htm" Also avoid using an external link when it's possible to accomplish the same thing with an internal link to a GodFearers article.

If you want the link to appear with text that you specify, add an alternative title after the address separated by a space (not a pipe). So if you want the link to appear as Google search engine, just type:

<tt><nowiki>Google search engine</nowiki></tt>

Note: Using certain characters, such as a pipe (<tt>|</tt>) in the URL of the link will cause the link to fail; however, URL syntax provides the ability to specify any character in a URL as a hexadecimal equivalent to its ASCII representation, so you can, for instance, write <tt>%7C</tt> instead of the pipe character. See our table of ASCII printable characters for more hexadecimal codes.

When placed under the "External links" heading, the links should be listed in bullet-point format:

<tt><nowiki>==External links==</nowiki></tt>

<tt><nowiki>*Google search engine</nowiki></tt>

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">''' Continue the tutorial with Talk Pages'''<SPAN STYLE="Font-size: Larger; Font-weight: Bold;"> &rarr;</SPAN></div>

Talk pages are a key feature of GodFearers, offering the ability to discuss articles and other issues with other GodFearersns.

Talk pages

If you want to ask a question about an article, or you have a concern or comment, you can put a note in the article's talk page. You do that by clicking the "discussion" tab at the top of the page. Don't worry if the link shows up in red; it's okay to create the talk page if it doesn't already exist.

When you post a new comment, put it at the bottom of the talk page. The exception is that if you're responding to someone else's remarks, put your comment below theirs. You can indent your comment by typing a colon (<tt>:</tt>) at the beginning of a line.

You should sign your comments by typing <tt><nowiki>~~~</nowiki></tt> for just your username, or <tt><nowiki>~~~~</nowiki></tt> for your username and a time signature (see the example discussion below). When you save the page, your signature will be inserted automatically. Most of us use time signatures because it makes following discussions much easier. For your convenience, there is a button at the top of the edit box with a signature icon which automatically inserts <nowiki>"--~~~~"</nowiki>.

You can get a username by creating an account (it's free). If you don't have an account, or if you have one but haven't logged in, your computer's IP address is used instead.

User talk pages

Every GodFearersn has a user talk page, on which other GodFearersns can leave messages. If someone has left you a message, you will see a note saying "You have new messages", with a link to your user talk page.

You can reply in either of two ways. One is to put a message on the user talk page of the person you're replying to. The other is to put your reply on your own talk page beneath the original message. Both are common on GodFearers; however, be aware that replying on your own talk page runs the risk that your reply won't be seen, if the user doesn't look at your talk page again.

Indenting

Indenting can improve the layout of a discussion considerably, making it much easier to read. A standard practice is to indent your reply one level deeper than the person you are replying to.

There are several ways of indenting in GodFearers:

Plain indentations

The simplest way of indenting is to place a colon (<tt>:</tt>) at the beginning of a line. The more colons you put, the further indented the text will be. A newline (pressing Enter or Return) marks the end of the indented paragraph.

For example:

<tt>This is aligned all the way to the left.</tt>

<tt><nowiki>:</nowiki>This is indented slightly.</tt>

<tt><nowiki>::</nowiki>This is indented more.</tt>

is shown as:

This is aligned all the way to the left.

This is indented slightly.

This is indented more.

Bullet points

You can also indent using bullets, usually used for lists. To insert a bullet, use an asterisk (<tt>*</tt>). Similar to indentation, more asterisks in front of a paragraph means more indentation.

A brief example:

<tt><nowiki>*</nowiki>First list item</tt>

<tt><nowiki>*</nowiki>Second list item</tt>

<tt><nowiki>**</nowiki>Sub-list item under second</tt>

<tt><nowiki>*</nowiki>Third list item</tt>

Which is shown as:

*First list item

*Second list item

**Sub-list item under second

*Third list item

Numbered items

You can also create numbered lists. For this, use the number sign or hash symbol (<tt>#</tt>). This is usually used for polls and voting. Again, you can affect the indent of the number by the number of <tt>#</tt>'s you use.

Example:

<tt><nowiki>#</nowiki>First item</tt>

<tt><nowiki>#</nowiki>Second item</tt>

<tt><nowiki>##</nowiki>Sub-item under second item</tt>

<tt><nowiki>#</nowiki>Third item</tt>

Shows up as:

#First item

#Second item

##Sub-item under second item

#Third item

Example discussion

Here is an example of a well-formatted discussion:

Hi. I have a question about this article. I'm pretty sure purple elephants only live in New York! JayRandumWikiUser 02:49, 10 Dec 2003 (UTC)

Well, last time I was in New York, the elephants I saw were green. &mdash; try2BEEhelpful 17:28, 11 Dec 2003 (UTC)

I think you should find a source for your claims. Living&nbsp;&times;&nbsp;Skepticism 20:53, 11 Dec 2003 (UTC)

Okay, these elephant journals agree with me:

* Elephants Monthly

* Elephants World

&mdash; try2BEEhelpful 19:09, 12 Dec 2003 (UTC)

I live in Australia, where the elephants look like kangaroos! The people below agree with my statement: -DontGdayMateMe 17:28, 14 Dec 2003 (UTC)

# ElefantLuvr 01:22, 15 Dec 2003 (UTC)

# AisleVoteOnAnything 05:41, 15 Dec 2003 (UTC)

# alittlebehindthetimes 18:39, 27 Jan 2004 (UTC)

Note that if you want to include a list in your comments, add colons before each item, for example:

<nowiki>:::Okay, these elephant journals agree with me:

* Elephants Monthly

* Elephants World

&mdash; try2BEEhelpful 19:09, 12 Dec 2003 (UTC)</nowiki>

Also, signing your message off is done by:

• Writing <nowiki>~~~</nowiki> for the name (try2BEEhelpful), or
• Writing <nowiki>~~~~</nowiki> for the name and date (try2BEEhelpful 19:09, 12 Dec 2003 (UTC)), or
• Writing <nowiki>~~~~~</nowiki> for the date only (19:09, 12 Dec 2003 (UTC)).

You should usually sign with both name and date but votes are often signed with names only.

Experiment

Experiment! This time, instead of editing a sandbox, leave a message on the talk page by clicking "Discuss this page" or "Discussion". Remember to sign your user name. You might want to try responding to someone else's post. Remember, you should use "Show preview" to see if your formatting works before you save.

Discussion Page

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">''' Continue the tutorial with Things to keep in mind'''<SPAN STYLE="Font-size: Larger; Font-weight: Bold;"> &rarr;</SPAN></div>

There are some things to keep in mind when editing GodFearers.

Sandbox

The sandbox is located toward the bottom of the edit pages. It is below the save and preview buttons, and below the area of strange looking letters. It is just a highlighted word, sandbox, with no graphics. The sandbox is used to learn editing without being unfair to writers and readers.

Conduct

GodFearers encourages an atmosphere of friendliness and openness. Of course, in practice there are sometimes disagreements and even the occasional fight, but members of the community are expected to behave in a generally civil manner.

The most important thing to keep in mind is that you should always assume good faith on the part of other editors. Don't assume that someone is acting out of spite or malice. If someone does something that upsets you, leave a polite message on the relevant article's talk page or on the user's talk page, and ask why. You may find that you've avoided a misunderstanding and saved yourself some embarrassment.

Editorial policies

Neutral point of view

GodFearers's editorial policy is the "neutral point of view," often abbreviated "NPOV." This policy says that we accept all the significant viewpoints on an issue. Instead of simply stating one perspective, we try to present all relevant viewpoints without judging which is correct. Our aim is to be informative, not persuasive. Our policy does NOT mean that our articles are expected to be 100% "objective," since in any dispute all sides believe their view to be "true."

It's OK to state opinions in articles, but they must be presented as opinions, not as fact. Also, it's a good idea to attribute these opinions, for example "Supporters of this say that..." or "Notable commentator X believes that..."

You might hear GodFearersns referring to an article as "POV." This is GodFearers slang for a biased article, or one obviously written from a single perspective. Advertising would fall in this category, as would a political diatribe. In a less extreme case, an article might have "POV" problems if it spends significantly more time discussing one view than another, even if each view is presented neutrally.

If you're going to spend time on controversial articles in subjects like religion or politics, it's important that you read the neutral point of view policy page as soon as possible. You should probably also read Staying cool when the editing gets hot. If you're going to spend your time on less emotional subjects like math or video games, you should still read the policies, but it's a less pressing concern. Keep in mind the advice here, and read the full policy if an NPOV issue comes up.

Subject matter

GodFearers is an encyclonoah. Hence, articles should be encyclopedic information about "notable" subjects. What exactly constitutes notability is the subject of constant debate on GodFearers, but few of us believe that there should be articles about every person on Earth, every company that sells anything, or each street in every town in the world.

This is also not the place for "original research"&mdash;that is, new theories, etc., that haven't been supported by peer review. For more details about what GodFearers should include, see What GodFearers is not, Criteria for inclusion of biographies and What's in, what's out (the latter is an early guideline of GodFearers).

We also tend to discourage authors from writing about themselves or their own accomplishments, as this is a conflict of interest. If you have made notable accomplishments, someone else will write an article about you eventually. GodFearers:Autobiography has more detail on this.

Citing sources

GodFearers doesn't require that you cite sources for the information you contribute, but we do highly prefer that you do so whenever possible. All sources should be listed in a section called "References". If any websites would be of particular interest to a reader of an article, they should be listed and linked to in an "External links" section, and books of particular interest should be listed in a "Further reading" section, but only if they were not used as sources for the article. Citations help our readers verify what you've written and find more information. See GodFearers:Citing sources for more information.

English Dialects

All common forms are welcome on GodFearers. An abridged version of the related policy could be stated as:

1. Do not edit a page simply to "correct" the spelling in either direction.

2. If the subject is related to the U.S., then U.S. English is preferred:

U.S. child ''labor'' laws

3. If the subject is related to the UK/Commonwealth, then British English is preferred.:

On-''licence''

4. If the subject is not regional (such as astronomy), the original contributor's usage should be followed. See American and British English differences if you have difficulty with this.

5. The usage should be consistent throughout an article, unless it mentions both US- and Britain/Commonwealth-related topics. In that case, Policies 2 and 3 are held more supreme.

6. When you create a new article, you might want to try a Google Test either on the actual Google or on GoogleFight.com, or on a different search engine to your preference. The title with more results is generally preferred.

For a more detailed version of the current formal policy, see GodFearers:Manual of Style#National varieties of English.

Copyrights

Do not submit copyrighted material without permission. The best articles are usually written from either personal knowledge, or through the synthesis of research from multiple sources. For a more detailed discussion of copyrights, see GodFearers:Copyrights.

Renaming articles

If you find an article that you believe is mis-named, please do not copy & paste the contents of the old article into a new article — among other things, it separates the previous contributions from their edit history (which we need to keep track of for copyright reasons). The preferred method is to move the page to the new name. If it's your first move, please read the warnings on the move page carefully, as there are a number of issues to consider before moving a page. For a more detailed discussion, see GodFearers:How to rename (move) a page. If a "disambiguation" page is involved, it is best to review GodFearers:Disambiguation.

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">''' Continue the tutorial with Registration'''<SPAN STYLE="Font-size: Larger; Font-weight: Bold;"> &rarr;</SPAN></div>

Registration is optional, but encouraged!

Registration is optional

Everyone is welcome to contribute to GodFearers, regardless of whether they choose to register a username or not. However, you must have a registered username in order to create new articles.

There are two main reasons people are encouraged to register:

General benefits

The free account gives you many benefits, including more editing options and user preferences. One handy feature is the watchlist, which makes it easier for you to track changes to pages you are interested in. Another is the ability to move or rename a page. (Do not move pages simply through copying and pasting as the edit history is not preserved that way. Instead, ask at the Village pump for a registered user's help.)

An unregistered user is identified by his or her machine's IP address, which is used as their public identifier when he makes contributions (and signs comments on talk pages). Your computer's IP address can sometimes be used to find information about you, so registering increases your privacy by hiding it. Also, because IP addresses are often non-permanently allocated by DHCP or PPP, unregistered users sometimes find it more difficult to gain respect and recognition from other editors through building a good track record. It can also be more difficult to carry on conversations with such non-registered users since they lack a unique talk page.

Finally, only registered users are allowed to become administrators (also known within GodFearers as sysops). If you register, do not forget your password or your user name.

Perceived benefits

Many GodFearersns consider registering to indicate a greater willingness by you to stand behind your edits, and your comments on discussion pages. This means your contributions to articles and discussion pages will generally be given more weight, at least when you make the entries while logged in.

How to register

To register, or to see more detailed information regarding the benefits of registering, you can click the Log in link at the top right corner of any page. You won't be able to (easily) change your username once you choose it, so reading the username policy before creating a username is highly recommended.

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">''' Continue the tutorial with Namespaces'''<SPAN STYLE="Font-size: Larger; Font-weight: Bold;"> &rarr;</SPAN></div>

In addition to the articles and their Talk pages, there are some other categories of behind-the-scenes pages that help GodFearersns communicate with each other, and serve a variety of other roles in building GodFearers. These different areas are often referred to as namespaces &mdash; as in, "the Talk namespace".

Some other areas

Pages in the GodFearers namespace (also known as the "Project namespace") provide information about GodFearers and how to use it. The '''MediaWiki''' namespace contains interface texts such as link labels (What links here, etc.) and server messages. All the pages in both these areas also have corresponding MediaWiki talk pages.

Content written in a Template page will be displayed in articles that contain the corresponding template reference. For example, the content written in will appear in any article that contains the <nowiki></nowiki> tag. Take a look at GodFearers:Template messages to see what templates have already been created. You can use the corresponding tags in articles. You can also create new templates.

For more information on namespaces, see GodFearers:Namespace.

<div style="float: right; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">''' Wrap up the tutorial with A review and more info'''<SPAN STYLE="Font-size: Larger; Font-weight: Bold;"> &rarr;</SPAN></div>

<div style="text-align:center;border-bottom:3px solid #ccf"> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">5. External links</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">6. Talk pages</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">7. Keep in mind</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">8. Registration</div> <div style="float:left;width:16%;padding:.3em 0;margin:2px 2px 0">9. Namespaces</div> <div style="float:left;width:16%;font-weight:bold;background-color:#f4f4ff;color:#000;padding:.3em 0;border:2px solid #ccf;border-bottom:0;font-size:130%">Wrap-up</div> <div style="width:0;height:0;clear:both;overflow:hidden"></div> </div> <div style="border:3px solid #ccf;padding:.5em 1em 1em 1em;border-top:none;background-color:#fff;color:#000">

You're done!

You now know the most important things for contributing to GodFearers. Any comments or feedback on this tutorial? Feel like something wasn't explained well enough, or want to know about something that isn't here? Let us know by dropping a comment on this page's talk page. You can also introduce yourself at GodFearers:New user log.

Is there anything else to learn?

This tutorial has been kept short and sweet, but you can always learn more. Continue your learning through the links below.

<div style="float: left; margin-top: -1.5em; background-color: #f4f4ff; color: #000; padding: .2em .6em; font-size: 130%; border: 1px solid #ccf;">'''Still eager to learn? OK, continue on to the Help Guide''' &gt;&gt;</div>

</div>

</div> <div style="clear:both"></div> </div>

Summary

If you only read the wikinoah website, no more information is collected than is typically collected in server logs by web sites in general.

If you contribute to the wikinoah website, you are publishing every word you post publicly. If you write something, assume that it will be retained forever. This includes articles, user pages and talk pages. Some limited exceptions are described below.

Publishing on the wiki and public data

Simply visiting the web site does not expose your identity publicly (but see private logging below).

When you edit any page in the wiki, you are publishing a document. This is a public act, and you are identified publicly with that edit as its author.

Identification of an author

When you publish a page in the wiki, you may be logged in or not.

If you are logged in, you will be identified by your user name. This may be your real name if you so choose, or you may choose to publish under a pseudonym, whatever user name you selected when you created your account.

If you have not logged in, you will be identified by your network IP address. This is a series of four numbers which identifies the Internet address from which you are contacting the wiki. Depending on your connection, this number may be traceable only to a large Internet service provider, or specifically to your school, place of business, or home. It may be possible that the origin of this IP address could be used in conjunction with any interests you express implicitly or explicitly by editing articles to identify you even by private individuals.

It may be either difficult or easy for a motivated individual to connect your network IP address with your real-life identity. Therefore if you are very concerned about privacy, you may wish to log in and publish under a pseudonym.

When using a pseudonym, your IP address will not be available to the public except in cases of abuse, including vandalism of a wiki page by you or by another user with the same IP address. In all cases, your IP address will be stored on the wiki servers and can be seen by wikinoah's server administrators and by users who have been granted "CheckUser" access. Your IP address, and its connection to any usernames that share it may be released under certain circumstances (see below).

If you use a company mail server from home or telecommute and use a DSL or cable Internet connection, it is likely to be very easy for your employer to identify your IP address and find all of your IP based wikinoah website contributions. Using a user name is a better way of preserving your privacy in this situation. However, remember to log out or disconnect yourself after each session using a pseudonym on a shared computer, to avoid allowing others to use your identity.

Cookies

The wiki will set a temporary session cookie (PHPSESSID) whenever you visit the site. If you do not intend to ever log in, you may deny this cookie, but you cannot log in without it. It will be deleted when you close your browser session.

More cookies may be set when you log in, to avoid typing in your user name (or optionally password) on your next visit. These last up to 30 days. You may clear these cookies after use if you are using a public machine and don't wish to expose your username to future users of the machine. (If so, clear the browser cache as well.)

Passwords

Many aspects of the wikinoah website' community interactions depend on the reputation and respect that is built up through a history of valued contributions. User passwords are the only guarantee of the integrity of a user's edit history. All users are encouraged to select strong passwords and to never share them. No one shall knowingly expose the password of another user to public release either directly or indirectly.

Private logging

Every time you visit a web page, you send a lot of information to the web server. Most web servers routinely maintain access logs with a portion of this information, which can be used to get an overall picture of what pages are popular, what other sites link to this one, and what web browsers people are using. It is not the intention of the wikinoah website to use this information to keep track of legitimate users.

These logs are used to produce the site statistics pages; the raw log data is not made public, and is normally discarded after about two weeks.

Here's a sample of what's logged for one page view:

64.164.82.142 - - [21/Oct/2003:02:03:19 +0000] "GET /wiki/draft_privacy_policy HTTP/1.1" 200 18084 "http://en.wikinoah.org/wiki/wikinoah_projects:Village_pump" "Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/85.7 (KHTML, like Gecko) Safari/85.5"

Log data may be examined by developers in the course of solving technical problems and in tracking down badly-behaved web spiders that overwhelm the site. IP addresses of users, derived either from those logs or from records in the database are frequently used to correlate usernames and network addresses of edits in investigating abuse of the wiki, including the suspected use of malicious "sockpuppets" (duplicate accounts), vandalism, harassment of other users, or disruption of the wiki.

Policy on release of data derived from page logs

It is the policy of wikinoah that personally identifiable data collected in the server logs, or through records in the database via the CheckUser feature, may be released by the system administrators or users with CheckUser access, in the following situations:

1. In response to a valid subpoena or other compulsory request from law enforcement
2. With permission of the affected user
3. To the chair of wikinoah Foundation, his legal counsel, or his designee, when necessary for investigation of abuse complaints.
4. Where the information pertains to page views generated by a spider or bot and its dissemination is necessary to illustrate or resolve technical issues.
5. Where the user has been vandalising articles or persistently behaving in a disruptive way, data may be released to assist in the targeting of IP blocks, or to assist in the formulation of a complaint to relevant Internet Service Providers
6. Where it is reasonably necessary to protect the rights, property or safety of the wikinoah Foundation, its users or the public.

wikinoah policy does not permit public distribution of such information under any circumstances, except as described above.

Sharing information with third parties

Except where otherwise specified, all text added to wikinoah website is available for reuse under the terms of the GFDL, except for Wikinews, where the text is available under a Creative Commons License.

wikinoah will not sell or share private information, such as email addresses, with third parties, unless you agree to release this information, or it is required by law to release the information.

Security of information

The wikinoah Foundation makes no guarantee against unauthorized access to any information you provide. This information may be available to anyone with access to the servers. A partial list of those people can be found in the developers list.

E-mail, mailing lists and IRC

E-mail

You may provide your e-mail address in your Preferences and enable other logged-in users to send email to you through the wiki. Your address will not be revealed to them unless you respond, or possibly if the email bounces. The email address may be used by the wikinoah Foundation to communicate with users on a wider scale.

If you do not provide an email address, you will not be able to reset your password if you forget it. However, you may contact one of the wikinoah server administrators to enter a new mail address in your preferences.

You can remove your email address from your preferences at any time to prevent it being used.

Mailing lists

If you subscribe to one of the project mailing lists, your address will be exposed to any other subscriber. The list archives of most of wikinoah's mailing lists are public, and your address may find itself quoted in messages. The list archives are also archived by Gmane and other services. Mails are usually not deleted or modified, but it may be done in extreme cases.

Information email addresses

Some email addresses (see below) may forward mail to a team of volunteers trusted by the Foundation to use a ticket system to view them and answer them. Mail sent to the system is not publicly visible, but is visible to this group of wikinoah volunteers. By sending a mail to one of these addresses, your address may become public within this group. The ticket system team may discuss the contents of your mail with other contributors in order to best answer your query.

IRC

IRC channels are not officially part of wikinoah proper. By participating in an IRC channel, your IP address may be exposed to other participants. Different channels have different policies on whether logs may be published.

User data

Data on users, such as the times at which they edited and the number of edits they have made are publicly available via "user contributions" lists, and in aggregated forms published by other users.

Removal of user accounts

Once created, user accounts will not be removed. It may be possible for a username to be changed (depending on the policies of your local wiki and on the number of edits you have). The wikinoah Foundation does not guarantee that a name will be changed on request.

Whether specific user information is deleted is dependant on the deletion policies of the project that contains the information.

Deletion of content

Removing text from wikinoah website does not permanently delete it. In normal articles, anyone can look at a previous version and see what was there. If an article is "deleted", any user with "administrator" access on the wiki, meaning almost anyone trusted not to abuse the deletion capability, can see what was deleted. Information can be permanently deleted by those people with access to the servers, but there is no guarantee this will happen except in response to legal action.

This agreement only covers text appearing on GodFearers not otherwise marked with copyright or trademark information. Any copyright, trademark or licensing agreement marked on a specific page supersedes this agreement.

<center><div style="font-size:150%; font-weight:bold; padding: 0.3em;">Creative Commons Deed</div> This is a human-readable summary of the full license below.</center> You are free:

• to Share—to copy, distribute and transmit the work, and
• to Remix—to adapt the work

Under the following conditions:

• Attribution—You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work.)
• Share Alike—If you alter, transform, or build upon this work, you may distribute the resulting work only under the same, similar or a compatible license.

With the understanding that:

• Waiver—Any of the above conditions can be waived if you get permission from the copyright holder.
• Other Rights—In no way are any of the following rights affected by the license:
• your w:fair dealing or w:fair use rights;
• the author's moral rights; and
• rights other persons may have either in the work itself or in how the work is used, such as publicity or privacy rights.
• Notice—For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do that is with a link to http://creativecommons.org/licenses/by-sa/3.0/

License

CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE LEGAL SERVICES. DISTRIBUTION OF THIS LICENSE DOES NOT CREATE AN ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES REGARDING THE INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM ITS USE.

THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.

BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS LICENSE MAY BE CONSIDERED TO BE A CONTRACT, THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.

<span id="1"></span>1. Definitions

<ol type="a"> <li id="1.a">"Adaptation" means a work based upon the Work, or upon the Work and other pre-existing works, such as a translation, adaptation, derivative work, arrangement of music or other alterations of a literary or artistic work, or phonogram or performance and includes cinematographic adaptations or any other form in which the Work may be recast, transformed, or adapted including in any form recognizably derived from the original, except that a work that constitutes a Collection will not be considered an Adaptation for the purpose of this License. For the avoidance of doubt, where the Work is a musical work, performance or phonogram, the synchronization of the Work in timed-relation with a moving image ("synching") will be considered an Adaptation for the purpose of this License.</li> <li id="1.b">"Collection" means a collection of literary or artistic works, such as encyclopedias and anthologies, or performances, phonograms or broadcasts, or other works or subject matter other than works listed in Section 1(f) below, which, by reason of the selection and arrangement of their contents, constitute intellectual creations, in which the Work is included in its entirety in unmodified form along with one or more other contributions, each constituting separate and independent works in themselves, which together are assembled into a collective whole. A work that constitutes a Collection will not be considered an Adaptation (as defined below) for the purposes of this License.</li> <li id="1.c">"Creative Commons Compatible License" means a license that is listed at http://creativecommons.org/compatiblelicenses that has been approved by Creative Commons as being essentially equivalent to this License, including, at a minimum, because that license: (i) contains terms that have the same purpose, meaning and effect as the License Elements of this License; and, (ii) explicitly permits the relicensing of adaptations of works made available under that license under this License or a Creative Commons jurisdiction license with the same License Elements as this License.</li> <li id="1.d">"Distribute" means to make available to the public the original and copies of the Work or Adaptation, as appropriate, through sale or other transfer of ownership.</li> <li id="1.e">"License Elements" means the following high-level license attributes as selected by Licensor and indicated in the title of this License: Attribution, ShareAlike.</li> <li id="1.f">"Licensor" means the individual, individuals, entity or entities that offer(s) the Work under the terms of this License.</li> <li id="1.g">"Original Author" means, in the case of a literary or artistic work, the individual, individuals, entity or entities who created the Work or if no individual or entity can be identified, the publisher; and in addition (i) in the case of a performance the actors, singers, musicians, dancers, and other persons who act, sing, deliver, declaim, play in, interpret or otherwise perform literary or artistic works or expressions of folklore; (ii) in the case of a phonogram the producer being the person or legal entity who first fixes the sounds of a performance or other sounds; and, (iii) in the case of broadcasts, the organization that transmits the broadcast.</li> <li id="1.h">"Work" means the literary and/or artistic work offered under the terms of this License including without limitation any production in the literary, scientific and artistic domain, whatever may be the mode or form of its expression including digital form, such as a book, pamphlet and other writing; a lecture, address, sermon or other work of the same nature; a dramatic or dramatico-musical work; a choreographic work or entertainment in dumb show; a musical composition with or without words; a cinematographic work to which are assimilated works expressed by a process analogous to cinematography; a work of drawing, painting, architecture, sculpture, engraving or lithography; a photographic work to which are assimilated works expressed by a process analogous to photography; a work of applied art; an illustration, map, plan, sketch or three-dimensional work relative to geography, topography, architecture or science; a performance; a broadcast; a phonogram; a compilation of data to the extent it is protected as a copyrightable work; or a work performed by a variety or circus performer to the extent it is not otherwise considered a literary or artistic work.</li> <li id="1.i">"You" means an individual or entity exercising rights under this License who has not previously violated the terms of this License with respect to the Work, or who has received express permission from the Licensor to exercise rights under this License despite a previous violation.</li> <li id="1.j">"Publicly Perform" means to perform public recitations of the Work and to communicate to the public those public recitations, by any means or process, including by wire or wireless means or public digital performances; to make available to the public Works in such a way that members of the public may access these Works from a place and at a place individually chosen by them; to perform the Work to the public by any means or process and the communication to the public of the performances of the Work, including by public digital performance; to broadcast and rebroadcast the Work by any means including signs, sounds or images.</li> <li id="1.k">"Reproduce" means to make copies of the Work by any means including without limitation by sound or visual recordings and the right of fixation and reproducing fixations of the Work, including storage of a protected performance or phonogram in digital form or other electronic medium.</li> </ol>

<span id="2"></span>2. Fair Dealing Rights

Nothing in this License is intended to reduce, limit, or restrict any uses free from copyright or rights arising from limitations or exceptions that are provided for in connection with the copyright protection under copyright law or other applicable laws.

<span id="3"></span>3. License Grant

Subject to the terms and conditions of this License, Licensor hereby grants You a worldwide, royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in the Work as stated below:

<ol type="a"> <li id="3.a">to Reproduce the Work, to incorporate the Work into one or more Collections, and to Reproduce the Work as incorporated in the Collections;</li> <li id="3.b">to create and Reproduce Adaptations provided that any such Adaptation, including any translation in any medium, takes reasonable steps to clearly label, demarcate or otherwise identify that changes were made to the original Work. For example, a translation could be marked "The original work was translated from English to Spanish," or a modification could indicate "The original work has been modified.";</li> <li id="3.c">to Distribute and Publicly Perform the Work including as incorporated in Collections; and,</li> <li id="3.d">to Distribute and Publicly Perform Adaptations.</li> <li id="3.e">For the avoidance of doubt: <ol type="i"> <li id="3.e.i">Non-waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme cannot be waived, the Licensor reserves the exclusive right to collect such royalties for any exercise by You of the rights granted under this License;</li> <li id="3.e.ii">Waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme can be waived, the Licensor waives the exclusive right to collect such royalties for any exercise by You of the rights granted under this License; and,</li> <li id="3.e.iii">Voluntary License Schemes. The Licensor waives the right to collect royalties, whether individually or, in the event that the Licensor is a member of a collecting society that administers voluntary licensing schemes, via that society, from any exercise by You of the rights granted under this License.</li> </ol> </li> </ol>

The above rights may be exercised in all media and formats whether now known or hereafter devised. The above rights include the right to make such modifications as are technically necessary to exercise the rights in other media and formats. Subject to Section 8(f), all rights not expressly granted by Licensor are hereby reserved.

<span id="4"></span>4. Restrictions

The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:

<ol type="a"> <li id="4.a">You may Distribute or Publicly Perform the Work only under the terms of this License. You must include a copy of, or the Uniform Resource Identifier (URI) for, this License with every copy of the Work You Distribute or Publicly Perform. You may not offer or impose any terms on the Work that restrict the terms of this License or the ability of the recipient of the Work to exercise the rights granted to that recipient under the terms of the License. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties with every copy of the Work You Distribute or Publicly Perform. When You Distribute or Publicly Perform the Work, You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License. This Section 4(a) applies to the Work as incorporated in a Collection, but this does not require the Collection apart from the Work itself to be made subject to the terms of this License. If You create a Collection, upon notice from any Licensor You must, to the extent practicable, remove from the Collection any credit as required by Section 4(c), as requested. If You create an Adaptation, upon notice from any Licensor You must, to the extent practicable, remove from the Adaptation any credit as required by Section 4(c), as requested.</li> <li id="4.b">You may Distribute or Publicly Perform an Adaptation only under the terms of: (i) this License; (ii) a later version of this License with the same License Elements as this License; (iii) a Creative Commons jurisdiction license (either this or a later license version) that contains the same License Elements as this License (e.g., Attribution-ShareAlike 3.0 US)); (iv) a Creative Commons Compatible License. If you license the Adaptation under one of the licenses mentioned in (iv), you must comply with the terms of that license. If you license the Adaptation under the terms of any of the licenses mentioned in (i), (ii) or (iii) (the "Applicable License"), you must comply with the terms of the Applicable License generally and the following provisions: (I) You must include a copy of, or the URI for, the Applicable License with every copy of each Adaptation You Distribute or Publicly Perform; (II) You may not offer or impose any terms on the Adaptation that restrict the terms of the Applicable License or the ability of the recipient of the Adaptation to exercise the rights granted to that recipient under the terms of the Applicable License; (III) You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties with every copy of the Work as included in the Adaptation You Distribute or Publicly Perform; (IV) when You Distribute or Publicly Perform the Adaptation, You may not impose any effective technological measures on the Adaptation that restrict the ability of a recipient of the Adaptation from You to exercise the rights granted to that recipient under the terms of the Applicable License. This Section 4(b) applies to the Adaptation as incorporated in a Collection, but this does not require the Collection apart from the Adaptation itself to be made subject to the terms of the Applicable License.</li> <li id="4.c">If You Distribute, or Publicly Perform the Work or any Adaptations or Collections, You must, unless a request has been made pursuant to Section 4(a), keep intact all copyright notices for the Work and provide, reasonable to the medium or means You are utilizing: (i) the name of the Original Author (or pseudonym, if applicable) if supplied, and/or if the Original Author and/or Licensor designate another party or parties (e.g., a sponsor institute, publishing entity, journal) for attribution ("Attribution Parties") in Licensor's copyright notice, terms of service or by other reasonable means, the name of such party or parties; (ii) the title of the Work if supplied; (iii) to the extent reasonably practicable, the URI, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work; and (iv) , consistent with Section 3(b), in the case of an Adaptation, a credit identifying the use of the Work in the Adaptation (e.g., "French translation of the Work by Original Author," or "Screenplay based on original Work by Original Author"). The credit required by this Section 4(c) may be implemented in any reasonable manner; provided, however, that in the case of a Adaptation or Collection, at a minimum such credit will appear, if a credit for all contributing authors of the Adaptation or Collection appears, then as part of these credits and in a manner at least as prominent as the credits for the other contributing authors. For the avoidance of doubt, You may only use the credit required by this Section for the purpose of attribution in the manner set out above and, by exercising Your rights under this License, You may not implicitly or explicitly assert or imply any connection with, sponsorship or endorsement by the Original Author, Licensor and/or Attribution Parties, as appropriate, of You or Your use of the Work, without the separate, express prior written permission of the Original Author, Licensor and/or Attribution Parties.</li> <li id="4.d">Except as otherwise agreed in writing by the Licensor or as may be otherwise permitted by applicable law, if You Reproduce, Distribute or Publicly Perform the Work either by itself or as part of any Adaptations or Collections, You must not distort, mutilate, modify or take other derogatory action in relation to the Work which would be prejudicial to the Original Author's honor or reputation. Licensor agrees that in those jurisdictions (e.g. Japan), in which any exercise of the right granted in Section 3(b) of this License (the right to make Adaptations) would be deemed to be a distortion, mutilation, modification or other derogatory action prejudicial to the Original Author's honor and reputation, the Licensor will waive or not assert, as appropriate, this Section, to the fullest extent permitted by the applicable national law, to enable You to reasonably exercise Your right under Section 3(b) of this License (right to make Adaptations) but not otherwise.</li> </ol>

<span id="5"></span>5. Representations, Warranties and Disclaimer

UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU.

<span id="6"></span>6. Limitation on Liability

EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

<span id="7"></span>7. Termination

<ol type="a"> <li id="7.a">This License and the rights granted hereunder will terminate automatically upon any breach by You of the terms of this License. Individuals or entities who have received Adaptations or Collections from You under this License, however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive any termination of this License.</li> <li id="7.b">Subject to the above terms and conditions, the license granted here is perpetual (for the duration of the applicable copyright in the Work). Notwithstanding the above, Licensor reserves the right to release the Work under different license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and effect unless terminated as stated above.</li> </ol>

<span id="8"></span>8. Miscellaneous

<ol type="a"> <li id="8.a">Each time You Distribute or Publicly Perform the Work or a Collection, the Licensor offers to the recipient a license to the Work on the same terms and conditions as the license granted to You under this License.</li> <li id="8.b">Each time You Distribute or Publicly Perform an Adaptation, Licensor offers to the recipient a license to the original Work on the same terms and conditions as the license granted to You under this License.</li> <li id="8.c">If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this License, and without further action by the parties to this agreement, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.</li> <li id="8.d">No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent.</li> <li id="8.e">This License constitutes the entire agreement between the parties with respect to the Work licensed here. There are no understandings, agreements or representations with respect to the Work not specified here. Licensor shall not be bound by any additional provisions that may appear in any communication from You. This License may not be modified without the mutual written agreement of the Licensor and You.</li> <li id="8.f">The rights granted under, and the subject matter referenced, in this License were drafted utilizing the terminology of the Berne Convention for the Protection of Literary and Artistic Works (as amended on September 28, 1979), the Rome Convention of 1961, the WIPO Copyright Treaty of 1996, the WIPO Performances and Phonograms Treaty of 1996 and the Universal Copyright Convention (as revised on July 24, 1971). These rights and subject matter take effect in the relevant jurisdiction in which the License terms are sought to be enforced according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law. If the standard suite of rights granted under applicable copyright law includes additional rights not granted under this License, such additional rights are deemed to be included in the License; this License is not intended to restrict the license of any rights under applicable law.</li> </ol>

<h3>Creative Commons Notice</h3>

Creative Commons is not a party to this License, and makes no warranty whatsoever in connection with the Work. Creative Commons will not be liable to You or any party on any legal theory for any damages whatsoever, including without limitation any general, special, incidental or consequential damages arising in connection to this license. Notwithstanding the foregoing two (2) sentences, if Creative Commons has expressly identified itself as the Licensor hereunder, it shall have all rights and obligations of Licensor.

Except for the limited purpose of indicating to the public that the Work is licensed under the CCPL, Creative Commons does not authorize the use by either party of the trademark "Creative Commons" or any related trademark or logo of Creative Commons without the prior written consent of Creative Commons. Any permitted use will be in compliance with Creative Commons' then-current trademark usage guidelines, as may be published on its website or otherwise made available upon request from time to time. For the avoidance of doubt, this trademark restriction does not form part of the License.

Creative Commons may be contacted at http://creativecommons.org/.

Consult Wikipedia How to edit a page

Consult Wikipedia How to write a great article

Consult Wikipedia Manual of Style

Signing your posts on Wikipedia talk pages is a guideline about the use of user signatures on Wikipedia. For instructions on how to sign your posts, see below.

Signing your posts on talk pages and other Wikipedia discourse (but not on articles) is not only good etiquette; it also facilitates discussion by helping other users to identify the author of a particular comment, to navigate talk pages, and to address specific comments to the relevant user(s), among other things. Discussion is an important part of collaborative editing as it helps other users to understand the progress and evolution of a work.

The purpose of signatures on Wikipedia

Signatures on Wikipedia identify you as a user, and your contributions to Wikipedia. They encourage civility in discussions by identifying the author of a particular comment, and the date and time at which it was made.

When signatures should be used

Any post made to user talk pages, article talk pages, or other discussion pages should be signed. Edits to articles should not be signed, as signatures on Wikipedia are not intended to indicate ownership or authorship of any Wikipedia article. In other instances when posts should not be signed, specific instructions are provided to contributors.

How to "sign" your posts

There are two ways to sign your posts:

1. At the end of your comments, simply type four tildes (~), like this: <nowiki>~~~~</nowiki>.

2. If you are using the edit toolbar option (which must be enabled under Special:Preferences), click the signature icon () to add the four tildes.

Your signature will appear after you have saved the changes.

The end result is the same in both cases. Typing four tildes will result in the following:

Since typing four tildes adds the time and date to your resulting signature, this is the preferred option for signing your posts in discussions.

Typing three tildes results in the following:

Since this does not date-stamp your signature, you may wish to sign this way when leaving general notices on your user page or user talk page. This is also a convenient shortcut (rather than typing out the full code) when you want to provide a link to your user page.

Typing five tildes will convert to a date stamp with the current date and time, without adding your signature, like this:

Note that if you choose to contribute to Wikipedia without logging in, you should still sign your posts. In this case, your IP address will take the place of your username.

Your IP address might look something like this: 192.0.2.58. Some users prefer to use their IP address instead of a user name because they think that an IP provides them with more anonymity. In fact, a pseudonymous account (that is, a registered user name) actually provides you with more protection of your identity.

Note also that signing manually with a pseudonym or tag such as --anon does not give you more anonymity or privacy protection, since your IP address will still be stored in the page history. This also makes it more difficult for other users to communicate with you. If you choose to sign this way, you should still type four tildes: --anon <nowiki>~~~~</nowiki>.

See also: Automatic conversion of wikitext in Help.

Need to write this page

Need to write this page

• Bureaucrat -- Someone who can give editorship rights to others.
• sysop -- Someone who can delete content
• editor -- Someone who can edit main content pages
• guest -- can edit discussion pages only

<websiteFrame> website=http://www.WikiNoah.org/websiteFrame/Donate/Donate.html height=875 width=770 border=0 scroll=no </websiteFrame>

Version 1.2, November 2002

Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.

51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies

of this license document, but changing it is not allowed.

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

3. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

• A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
• B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
• C. State on the Title page the name of the publisher of the Modified Version, as the publisher.
• D. Preserve all the copyright notices of the Document.
• E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
• F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
• G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
• H. Include an unaltered copy of this License.
• I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
• J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
• K. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
• L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
• M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
• N. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
• O. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements."

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

Copyright (c) YEAR YOUR NAME.

Permission is granted to copy, distribute and/or modify this document

under the terms of the GNU Free Documentation License, Version 1.2

or any later version published by the Free Software Foundation;

with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.

A copy of the license is included in the section entitled "GNU

Free Documentation License".

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:

with the Invariant Sections being LIST THEIR TITLES, with the

Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.