View source

From HTN

You do not have permission to do that, for the following reason:
The action you have requested is limited to users in the group user.
You can view and copy the source of this page:
HTN POLICIES Draft—31July 2008 (MS&amp;JV) 

<br> Security 

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 HTN to use this information to keep track of legitimate users. 

Policy on release of data derived from page logs 

It is the policy of IEEE HTN that personally identifiable data collected in the server logs may only be released in the following situations: In response to a valid subpoena or other compulsory request from law enforcement. With permission of the affected user.  To the chair of the IEEE Humanitarian Technology Challenge, his/her legal counsel, or his/her designee, when necessary for investigation of abuse complaints. Where the user has been vandalizing 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 Where it is reasonably necessary to protect the rights, property or safety of IEEE, its users or the public. 

IEEE policy does not permit public distribution of such information under any circumstances, except as described above. IEEE 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. 

<br> Security of information 

IEEE makes no guarantee against unauthorized access to any information you provide. This information may be available to anyone with access to the servers. 

<br> 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 IEEE to communicate with users on a wider scale. 

<br> Deletion of content 

Removing text from the IEEE HTN 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. 

<br> Retrieved from "http://wikimediafoundation.org/wiki/Privacy_policy" 

User identity and user info available to other users and administrator 

Includes – User Identity 

User Identity: 

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. 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 IEEE web account. 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 IEEE's server administrators. 

Cookies 

The wiki will set a temporary session cookie (PHPSESSID) whenever you visit the site. 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 IEEE HTN's 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. 

<br> 

Intellectual property issues 

Includes – How to cite the website, Copyrights, Copyright Violations 

How to cite the website: 

A wiki is an unusual medium, and as such doesn't conform well to the usual book-citation formats. Wiki is not paper, so you will need to use an electronic-citation format instead. The exact format will depend upon the citation guide that you are following, but here are a few general principles to consider: . You should not cite any particular author or authors for a IEEE HTN article, in general, because much of IEEE HTN content will be collaboratively written. However, if you do need to find the list of authors of a particular article, you can check the Page history. Authors are listed by the chosen user name; you normally. Your citation should normally list both the article title and IEEE Humanitarian Technology Network much as you would for an article in a paper publication. Every article should be a separate citation. Most citation styles will likely require the full article URL. You can click "Permanent link" in the toolbox at the left of this page. This lets the URL include a unique identifier such that you can tie your reference back to the exact version of the article you are referencing. It may or may not be desirable to adopt this approach, depending upon the context of your reference. This lets you show what you saw and ignore any changes made after you accessed the page. The citation style may request the full date and time of the article revision you are using. If you use the permanent link feature, this may not be necessary. However, the date and time of the last revision can be found at the bottom of every page (above the copyright notice). This page also gives examples in particular formats such as APA, MLA, Chicago, etc. 

Copyrights 

Important note: The IEEE does not own copyright on IEEE HTN article texts and illustrations except on locked pages where indicated. It is therefore useless to email our contact addresses asking for permission to reproduce content. Permission to reproduce content under the license and technical conditions applicable to IEEE HTN. The license the IEEE HTN uses, grants free access to our content in the same sense that free software is licensed freely. This principle is known as copyleftcopyleft. HTN content can be copied, modified, and redistributed so long as the new version grants the same freedoms to others and acknowledges the authors of the IEEE HTN article used (a direct link back to the article is generally thought to satisfy the attribution requirement). IEEE HTN articles therefore will remain free under the GNU Free Documentation License (GFDL) and can be used by anybody subject to certain restrictions, most of which aim to ensure that freedom. To this end, the text contained in the HTN is copyrighted (automatically, under the Berne Convention) by IEEE HTN contributors and licensed to the public under the GFDL). 

<br> Text of the GNU Free Documentation License 

<br> 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 non-commercially. 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. 

<br> Contributors' rights and obligations 

If you contribute material to the IEEE HTN, you thereby license it to the public under the GFDL (with no invariant sections, front-cover texts, or back-cover texts). In order to contribute, you must be in a position to grant this license, which means that either you hold the copyright to the material, for instance because you produced it yourself, or you acquired the material from a source that allows the licensing under GFDL, for instance because the material is in the public domain or is itself published under GFDL. In the first case, you retain copyright to your materials. You can later republish and relicense them in any way you like. However, you can never retract the GFDL license for the copies of materials that you place here; these copies will remain under GFDL until they enter the public domain. In the second case, if you incorporate external GFDL materials, as a requirement of the GFDL, you need to acknowledge the authorship and provide a link back to the network location of the original copy. 

<br> Using copyrighted work from others 

All works are copyrighted unless either they fall into the public domain or their copyright is explicitly disclaimed. If you use part of a copyrighted work under "fair use", or if you obtain special permission to use a copyrighted work from the copyright holder under the terms of our license, you must make a note of that fact (along with names and dates). It is our goal to be able to freely redistribute as much of the HTN’s material as possible, so original images and sound files licensed under the GFDL or in the public domain are greatly preferred to copyrighted media files used under fair use. Never use materials that infringe the copyrights of others. This could create legal liabilities and seriously hurt the project. If in doubt, write it yourself. Note that copyright law governs the creative expression of ideas, not the ideas or information themselves. Therefore, it is legal to read an encyclopedia article or other work, reformulate the concepts in your own words, and submit it to the HTN. However, it would still be unethical (but not illegal) to do so without citing the original as a reference. 

<br> Linking to copyrighted works 

Since most recently-created works are copyrighted, almost any IEEE HTN article which cites its sources will link to copyrighted material. It is not necessary to obtain the permission of a copyright holder before linking to copyrighted material, just as an author of a book does not need permission to cite someone else's work in their bibliography. Likewise, the HTN is not restricted to linking only to GFDL-free or open-source content. However, if you know that an external Web site is carrying a work in violation of the creator's copyright, do not link to that copy of the work. Knowingly and intentionally directing others to a site that violates copyright has been considered a form of contributory infringement in the United States. 

<br> Copyright violations 

Contributors who repeatedly post copyrighted material despite appropriate warnings may be blocked from editing by any administrator to prevent further problems. If you suspect a copyright violation, you should at least bring up the issue on that page's discussion page. Others can then examine the situation and take action if needed. Some cases will be false alarms. 

<br> Image guidelines 

Images and photographs, like written works, are subject to copyright. Someone holds the copyright unless they have been explicitly placed in the public domain. Images on the internet need to be licensed directly from the copyright holder or someone able to license on their behalf. In some cases, fair use guidelines may allow an image to be used irrespective of any copyright claims. Works produced by civilian and military employees of the United States federal government in the scope of their employment are public domain by statute in the United States (though they may be protected by copyright outside of the U.S.). Under guidelines for non-free content, brief selections of copyrighted text may be used, but only with full attribution and only when the purpose is to comment on or criticize the text quoted. 

Disclaimer 

From Citizendium, the Citizens' Compendium Jump to: navigation, search All unapproved IEEE HTN articles may contain errors of fact, bias, grammar, etc. An article is unapproved unless it is specifically and prominently marked at the top of the page (with a certain green template, illustrated for example on this page) as approved. The IEEE and the participants in the IEEE HTN make no representations about the reliability of these articles or, generally, their suitability for any purpose. 

Approved articles are intended to have few errors; however, we make no representations about the reliability or suitability of these articles. 

<br> Ethical issues 

Includes – Attack Pages, Personal Attacks, Conflict of Interest, Civility Vandalism is any addition, removal, or change of content made in a deliberate attempt to compromise the integrity of the HTN. The most common types of vandalism include the addition of obscenities or crude humor, page blanking, or the insertion of nonsense into articles. Any good-faith effort to improve the encyclopedia, even if misguided or ill-considered, is not vandalism. Even harmful edits that are not explicitly made in bad faith are not considered vandalism. For example, adding a personal opinion to an article once is not vandalism — it's just not helpful, and should be removed or restated. Not all vandalism is obvious, nor are all massive or controversial changes vandalism. Careful attention needs to be given to whether changes made are beneficial, detrimental but well intended, or outright vandalism. Committing vandalism violates HTN policy. If you find that another user has vandalized the HTN, you should revert the changes and warn the user (see below for specific instructions). Users who vandalize the HTN repeatedly, despite warnings to stop, should be reported to HTN:Administrator intervention against vandalism, and administrators may block them. Note that warning is not an absolute prerequisite for blocking; accounts whose main or only use is obvious vandalism or other forbidden activity may be blocked without warning. Blocking is the method by which administrators may technically prevent users from editing the HTN. Blocks are used to prevent damage or disruption to the HTN, not to punish users.[1] Any user may request a block at the administrators' noticeboard for incidents or a specialized venue such as the administrator intervention against vandalism noticeboard. Users requesting blocks should supply credible evidence of the circumstances warranting a block. Administrators are never obliged to place a block and are free to investigate the situation themselves. If you wish to contest a block, see HTN:Appealing a block for further instructions. Except in cases of unambiguous error, administrators should not undo other administrators' blocks without prior discussion; see below. Purpose and goal 

All blocks ultimately exist to protect the project from harm, and reduce likely future problems. When lesser measures are inadequate, or problematic conduct persists, appropriate use of a block can help achieve this in four important ways: Preventing imminent or continuing damage and disruption to the HTN. Deterring the continuation of disruptive behavior by making it more difficult to edit. Encouraging a rapid understanding that the present behavior cannot continue and will not be tolerated. Encouraging a more productive, congenial editing style within community norms. 

Important note – Blocks are intended to reduce the likelihood of future problems, by either removing, or encouraging change in, a source of disruption. They are not intended for use in retaliation, as punishment, or where there is no current conduct issue which is of concern. 

<br> For the purposes of protection and encouragement, blocks may escalate in duration to protect the HTN while allowing for the cessation of disruptive editing and the return to respected editing. Attack Pages- An IEEE HTN article, page, template, category, redirect or image created for the sole purpose of disparaging its subject is an attack page. Under the criteria for speedy deletion, these pages are subject to being deleted by any administrator at any time. Non-administrative users who find such pages should add the {{db-attack}} tag to them, and should warn the user who created them by putting the {{attack|page}} tag on their talk page. If the subject of the article is notable, but the existing page consists solely or primarily of personal attacks against that subject and there's no good revision to revert to, then the attack page should be deleted and an appropriate stub article should be written in its place. This is not meant to apply to requests for comment, requests for mediation and similar processes (although these processes have their own guidelines for deletion of requests that are invalid or in bad faith). On the other hand, keeping a "list of enemies" or "list of everything bad that some user ever did" is not constructive or appropriate. Bear in mind that the key to resolving a dispute is not to find and list all the dirt you can find on somebody. 

<br> In addition to observing the legal requirements, it is necessary for users to maintain civility and appropriate language at all times 

Dealing with IP and Intellectual Issues 

Anyone violating the HTN’s norms, or assisted someone else in doing so, can be blocked from the site by the HTN Oversight Committee at their discretion. 

Content policies (e.g. insistence on history, avoid being taken into “how-does-it-work” content, quality/level of writing, point of view, position on original research) Note: Neutral Point of View (NPOV) applies to standard articles, but will not be relevant for first-hand accounts. What about gray zone when First-hand account slips into standard article? 

The neutral point of view—wiki articles only 

The neutral point of view is a means of dealing with conflicting verifiable perspectives on a topic as evidenced by reliable sources. The policy requires that where multiple or conflicting perspectives exist within a topic each should be presented fairly. None of the views should be given undue weight or asserted as being judged as "the truth", in order that the various significant published viewpoints are made accessible to the reader, not just the most popular one. It should also not be asserted that the most popular view, or some sort of intermediate view among the different views, is the correct one to the extent that other views are mentioned only pejoratively. Readers should be allowed to form their own opinions. As the name suggests, the neutral point of view is a point of view, not the absence or elimination of viewpoints. The neutral point of view policy is often misunderstood. The acronym NPOV does not mean "no points of view". The elimination of article content cannot be justified under this policy by simply labeling it "POV". The neutral point of view is neither sympathetic nor in opposition to its subject: it neither endorses nor discourages viewpoints. Debates within topics are clearly described, represented and characterized, but not engaged in. Background is provided on who believes what and why, and which view is more popular. Detailed articles might also contain the mutual evaluations of each viewpoint, but must studiously refrain from asserting which is better. 

Quality control – 

The IEEE HTN welcomes the contribution of both first-hand accounts and standard articles. Stylistically speaking, remember that the IEEE HTN is not a dictionary, so make your sentences engaging and pithy. If writing a standard article, the HTN insists upon the use of references. For questions on citation, please see here.
Templates used on this page:
Return to HTN:Terms.
Retrieved from "http://ieeehtn.org/htn/index.php/HTN:Terms"