User:Junkie/Help:Editing

From FedoraProject

< User:Junkie(Difference between revisions)
Jump to: navigation, search
(help:editing zh tran init(not completed))
 
(tran title)
Line 1: Line 1:
{{admon/important|2008-09-06 Wiki 结构页面位置|[[Help:Wiki_structure]] 描述了本wiki的结构,包括了页面的命名.}}
+
{{admon/important|2008-09-06 Wiki 结构页面位置|[[Help:Wiki_structure]] 描述了本wiki的结构, 包括了页面的命名.}}
  
 
{{admon/note|标记语言的其它资源|[http://meta.wikimedia.org/wiki/Help:Editing Help:Editing from Mediawiki.org] 是一个不错的标记语言帮助. 这有一张方便的 [http://meta.wikimedia.org/wiki/Help:Reference_card reference card] 图片.}}
 
{{admon/note|标记语言的其它资源|[http://meta.wikimedia.org/wiki/Help:Editing Help:Editing from Mediawiki.org] 是一个不错的标记语言帮助. 这有一张方便的 [http://meta.wikimedia.org/wiki/Help:Reference_card reference card] 图片.}}
Line 7: Line 7:
 
{{admon/tip|Wiki 迁移需要做的事|阅读 [[FedoraProject:Wiki migration to-do]] 后决定是否你需要为你的用户或 SIG/subProject 页面做些什么.}}
 
{{admon/tip|Wiki 迁移需要做的事|阅读 [[FedoraProject:Wiki migration to-do]] 后决定是否你需要为你的用户或 SIG/subProject 页面做些什么.}}
  
Fedora Project Wiki 对编辑来说入门是很容易的,刚开始使用 wiki 需花点时间,我们准备了很多向导你应该看看的.这页的内容就提供了这些向导和技巧来帮助你.
+
Fedora Project Wiki 对编辑来说入门是很容易的, 刚开始使用 wiki 需花点时间, 你应该看看我们准备的一些准则. 本页的内容提供了这些准则和技巧来帮助你.
  
  
Line 13: Line 13:
  
 
{{Anchor|Getting_Edit_Access}}
 
{{Anchor|Getting_Edit_Access}}
== Gaining Edit Access ==
+
== 获得编辑权限 ==
  
In order to avoid malicious users defacing the Fedora Project Wiki, we have had to restrict edit access a little. To gain edit access to the wiki, you must follow a few simple steps. '''Anyone can gain edit access.'''
+
为了防止不怀好意的人破坏 Fedora Project Wiki, 我们不得不对编辑权限做限制. 要获得 wiki 的编辑权限, 你必须完成下面的步骤. '''任何人都可以获得编辑权限'''
  
# Familiarize yourself with the information on this page and the pages that it links to. Basic guidelines that should be followed throughout the wiki are covered here.  Failure to follow these guidelines creates unnecessary work for other volunteers and may result in revocation of editing privileges.
+
# 熟悉本页信息及本页链接到的页面信息. wiki 所遵循的基本准则都在这里. 没有遵循这些准则造成不必要的工作, 其他志愿者可能撤销你的编辑特权。
 
# Complete the Contributor License Agreement through the [[Infrastructure/AccountSystem|Fedora Account System]]. Signing the CLA gives the Fedora Project the ability to license your contributions to the wiki under the ''[[Legal/Licenses/OPL|  Open Publication License 1.0]]  without options''.  This assures that your contributions will remain forever Free for the community to use, modify, and redistribute, just like the Fedora distribution.  See our [[Legal]]  section for more information. Follow the instructions at [[Infrastructure/AccountSystem/CLAHowTo]].
 
# Complete the Contributor License Agreement through the [[Infrastructure/AccountSystem|Fedora Account System]]. Signing the CLA gives the Fedora Project the ability to license your contributions to the wiki under the ''[[Legal/Licenses/OPL|  Open Publication License 1.0]]  without options''.  This assures that your contributions will remain forever Free for the community to use, modify, and redistribute, just like the Fedora distribution.  See our [[Legal]]  section for more information. Follow the instructions at [[Infrastructure/AccountSystem/CLAHowTo]].
  
 
{{Admon/note|If you are interested in more general website maintenance, or wish to be part of the Fedora Websites team, please see the [[Websites]] page. | Information on writing new formal Fedora documentation using the wiki is available from [[DocsProject/WritingUsingTheWiki|Writing Wiki Documentation]].}}
 
{{Admon/note|If you are interested in more general website maintenance, or wish to be part of the Fedora Websites team, please see the [[Websites]] page. | Information on writing new formal Fedora documentation using the wiki is available from [[DocsProject/WritingUsingTheWiki|Writing Wiki Documentation]].}}
  
== Guidelines and Wiki Etiquette ==
+
== 准则和 Wiki 礼节 ==
  
 
There are a few simple points you should follow as you make changes to the wiki. Below are some examples. In general, be courteous and use common sense.  Defying these guidelines and causing problems are a good way to get your edit privileges revoked.  If you have questions, you can ask on #fedora-websites on [http://freenode.net/ freenode].
 
There are a few simple points you should follow as you make changes to the wiki. Below are some examples. In general, be courteous and use common sense.  Defying these guidelines and causing problems are a good way to get your edit privileges revoked.  If you have questions, you can ask on #fedora-websites on [http://freenode.net/ freenode].
  
=== Introduce yourself ===
+
=== 介绍你自己 ===
  
 
Before you start editing any page, kindly introduce yourself by adding your information to your wiki page. After you have registered your name in the wiki, you automatically have a personal wiki page located at <code><nowiki>http://fedoraproject.org/wiki/User:</nowiki><username></code>, where <code><username></code> is replaced by your Fedora Account System account name. You can also easily get to your wiki page by clicking your username in the top right-hand corner of each page of the wiki.
 
Before you start editing any page, kindly introduce yourself by adding your information to your wiki page. After you have registered your name in the wiki, you automatically have a personal wiki page located at <code><nowiki>http://fedoraproject.org/wiki/User:</nowiki><username></code>, where <code><username></code> is replaced by your Fedora Account System account name. You can also easily get to your wiki page by clicking your username in the top right-hand corner of each page of the wiki.
Line 34: Line 34:
 
Make sure you mention at least your email address and, if you are on IRC often, your IRC nick and channels you are often in.
 
Make sure you mention at least your email address and, if you are on IRC often, your IRC nick and channels you are often in.
  
=== Always watch pages that you create or edit ===
+
=== 总是关注你产生或编辑的页面 ===
  
 
It is important that you follow changes to pages you create or edit, so you can coordinate with others working in the wiki content. Wiki editors usually add notes to the pages to convey information to each other as part of working together, and it helps to keep track of these changes.
 
It is important that you follow changes to pages you create or edit, so you can coordinate with others working in the wiki content. Wiki editors usually add notes to the pages to convey information to each other as part of working together, and it helps to keep track of these changes.
Line 40: Line 40:
 
You can find the '''watch''' link in the tab bar at the top of a page when you are logged in.
 
You can find the '''watch''' link in the tab bar at the top of a page when you are logged in.
  
=== Be Bold ===
+
=== 设为粗体 ===
  
 
Be '''bold''' while editing changes. Wiki changes are tracked and can be reverted when necessary. This doesn't mean you should be reckless especially when making large changes to key documents.
 
Be '''bold''' while editing changes. Wiki changes are tracked and can be reverted when necessary. This doesn't mean you should be reckless especially when making large changes to key documents.
Line 46: Line 46:
 
For more information on being '''bold''', take a look at the [[wikipedia:Wikipedia:Be_bold |be '''bold''' editing guideline on Wikipedia]].
 
For more information on being '''bold''', take a look at the [[wikipedia:Wikipedia:Be_bold |be '''bold''' editing guideline on Wikipedia]].
  
=== Avoid unnecessary edits of pages that discuss legal issues ===
+
=== 避免对法律问题页面不必要的修改 ===
  
 
These pages have been carefully written, and the words chosen carefully. When changing these documents, it is usually best to ask for review before applying changes. You can contact the [[Board|Fedora Advisory Board]] for assistance.
 
These pages have been carefully written, and the words chosen carefully. When changing these documents, it is usually best to ask for review before applying changes. You can contact the [[Board|Fedora Advisory Board]] for assistance.
  
=== Do not provide details of forbidden items ===
+
=== 不要提供详细的禁止项目 ===
  
 
Do not add any information that violates the law.  Remember that the Fedora Project is an entity in the United States, and is governed by its laws.  Avoid linking to or adding information about software that is not free and open source or that is legally encumbered.  If you think you have a special exception, bring it to the attention of the [[Websites]]  team for discussion.  See the [[ForbiddenItems]] page for examples of items that should be avoided.
 
Do not add any information that violates the law.  Remember that the Fedora Project is an entity in the United States, and is governed by its laws.  Avoid linking to or adding information about software that is not free and open source or that is legally encumbered.  If you think you have a special exception, bring it to the attention of the [[Websites]]  team for discussion.  See the [[ForbiddenItems]] page for examples of items that should be avoided.
Line 56: Line 56:
 
Bring questions to the [[Websites]]  team for discussion.  If needed, they can get the official word.
 
Bring questions to the [[Websites]]  team for discussion.  If needed, they can get the official word.
  
=== Be careful when editing key guides or pages ===
+
=== 小心编辑向导或页面 ===
  
 
Large and important guides, such as the [[Packaging/Guidelines| Packaging Guidelines]] , are generally managed by a specific individual or small group.  It is best to work with them when you feel that changes are needed.
 
Large and important guides, such as the [[Packaging/Guidelines| Packaging Guidelines]] , are generally managed by a specific individual or small group.  It is best to work with them when you feel that changes are needed.
Line 62: Line 62:
 
Important pages, like the FedoraMain or [[Distribution/Download|  Download]]  pages, are the first thing that many visitors see.  Changes to such pages should generally be left to experienced contributors.  If you feel that something on such a page should be altered, bring the issue to the [[Websites]]  team for discussion.
 
Important pages, like the FedoraMain or [[Distribution/Download|  Download]]  pages, are the first thing that many visitors see.  Changes to such pages should generally be left to experienced contributors.  If you feel that something on such a page should be altered, bring the issue to the [[Websites]]  team for discussion.
  
=== Do not edit pages just to edit pages ===
+
=== 不要编辑页面只为编辑页面 ===
  
 
Senseless edits should be avoided. Making an alteration to a page just to put your name in the edit log is unacceptable. There are plenty of pages (most of them, in fact) that have real errors that can be corrected. Instead of making pointless edits, such as removing or adding whitespace or changing links from fedoraproject.org to www.fedoraproject.org (the former is preferred), try finding errors in spelling, grammar or punctuation that can be corrected.  Also, when correcting a small error, mark "This is a minor edit" using the appropriate checkbox before you save it.
 
Senseless edits should be avoided. Making an alteration to a page just to put your name in the edit log is unacceptable. There are plenty of pages (most of them, in fact) that have real errors that can be corrected. Instead of making pointless edits, such as removing or adding whitespace or changing links from fedoraproject.org to www.fedoraproject.org (the former is preferred), try finding errors in spelling, grammar or punctuation that can be corrected.  Also, when correcting a small error, mark "This is a minor edit" using the appropriate checkbox before you save it.
  
=== Avoid renaming pages or moving content without coordination ===
+
=== 避免没有协调好就重命名或移动页面的内容 ===
  
 
Wiki pages are generally referred to and linked to from various other locations. It is important that you coordinate with the appropriate groups before moving content or renaming existing pages. It would be better to avoid doing that without strong rationale. If you wish to discuss moving a particular item, bring your questions to the [[Websites]] team.
 
Wiki pages are generally referred to and linked to from various other locations. It is important that you coordinate with the appropriate groups before moving content or renaming existing pages. It would be better to avoid doing that without strong rationale. If you wish to discuss moving a particular item, bring your questions to the [[Websites]] team.
  
=== Deleting Pages ===
+
=== 删除页面 ===
  
 
Wiki pages that are no longer needed can be tagged for deletion by adding <nowiki>{{Delete|Reason}}</nowiki> to the beginning of the page, this gives Wiki Administrators the ability to ensure that important or archivable content is not lost.
 
Wiki pages that are no longer needed can be tagged for deletion by adding <nowiki>{{Delete|Reason}}</nowiki> to the beginning of the page, this gives Wiki Administrators the ability to ensure that important or archivable content is not lost.
Line 78: Line 78:
 
For example, try to remain desktop-neutral and user-friendly, especially for non-technical users who are new to Linux and to Fedora. Users may use GNOME, KDE, the console, or some other environment. Try to keep that in mind when writing instructions. Make sure that Fedora's devotion to free and open source technology is also represented properly.
 
For example, try to remain desktop-neutral and user-friendly, especially for non-technical users who are new to Linux and to Fedora. Users may use GNOME, KDE, the console, or some other environment. Try to keep that in mind when writing instructions. Make sure that Fedora's devotion to free and open source technology is also represented properly.
  
=== Sign your attachments ===
+
=== 对附件签名 ===
  
 
When you attach a file to a wiki page, you should create a detached signature with your GPG key.  Some file formats, such as RPM packages, support GPG keys, in which case you do not need to create a detached signature -- a signature in the file will be enough.  A detached signature can be attached to the page alongside the original attachment, or can be included in the page itself.
 
When you attach a file to a wiki page, you should create a detached signature with your GPG key.  Some file formats, such as RPM packages, support GPG keys, in which case you do not need to create a detached signature -- a signature in the file will be enough.  A detached signature can be attached to the page alongside the original attachment, or can be included in the page itself.
Line 88: Line 88:
 
If you do not have a GPG key or want to learn more, see the [[Cryptography]]  page.
 
If you do not have a GPG key or want to learn more, see the [[Cryptography]]  page.
  
=== Review your changes for errors ===
+
=== 审查更改防止错误 ===
  
 
Whether you are a skilled writer, or your English skills are not strong, invite someone else to review. Well-written documents are important to Fedora's image. Even the best writers are prone to typos or other errors. Take a moment to review your changes to catch small errors. Use the '''Show preview''' button when editing a page to check your syntax.
 
Whether you are a skilled writer, or your English skills are not strong, invite someone else to review. Well-written documents are important to Fedora's image. Even the best writers are prone to typos or other errors. Take a moment to review your changes to catch small errors. Use the '''Show preview''' button when editing a page to check your syntax.
  
=== Fedora is a community ===
+
=== Fedora 是一个社区 ===
  
 
When writing content, for the wiki or elsewhere, remember that Fedora is a community.  ''We'' operate as one, unified group, moving towards common goals.  ''We'' do not need to distinguish one group or class against another.  For example, there is no need to distinguish between contributors who work for Red Hat and those who do not.  All contributors are part of the same community.  There will be cases where classification is necessary, but it can be avoided otherwise.
 
When writing content, for the wiki or elsewhere, remember that Fedora is a community.  ''We'' operate as one, unified group, moving towards common goals.  ''We'' do not need to distinguish one group or class against another.  For example, there is no need to distinguish between contributors who work for Red Hat and those who do not.  All contributors are part of the same community.  There will be cases where classification is necessary, but it can be avoided otherwise.
  
=== If you aren't sure about something, feel free to ask ===
+
=== 如果你有不知道, 随时提问 ===
  
 
Other community members will be happy to assist you. The #fedora-websites channel on [http://freenode.net/ freenode]  is the perfect place to discuss the wiki or other Fedora websites.
 
Other community members will be happy to assist you. The #fedora-websites channel on [http://freenode.net/ freenode]  is the perfect place to discuss the wiki or other Fedora websites.
  
 
{{Anchor|Watch-Your-Pages}}
 
{{Anchor|Watch-Your-Pages}}
=== Watch your pages, and other ones, too ===
+
=== 关注你的页面, 其他人的页面 ===
  
 
Two details make a Wiki successful as an open content collaboration tool.  First is being able to watch content you are responsible for, to make certain it stays true to its mission.  Second is being able to watch other content develop, grow, and occasionally need your help.
 
Two details make a Wiki successful as an open content collaboration tool.  First is being able to watch content you are responsible for, to make certain it stays true to its mission.  Second is being able to watch other content develop, grow, and occasionally need your help.
Line 109: Line 109:
 
To receive emails for every edit, go to '''[[Special:Preferences|my preferences]]''' (at the top of the page by your name) and make sure to check the appropriate boxes in the '''User profile''' tab, under '''Email'''.
 
To receive emails for every edit, go to '''[[Special:Preferences|my preferences]]''' (at the top of the page by your name) and make sure to check the appropriate boxes in the '''User profile''' tab, under '''Email'''.
  
==== Using Special:Watchlist ====
+
==== 使用 Special:Watchlist ====
 
[[Special:Watchlist]] (available by clicking '''my watchlist''' at the top of each page when you are logged in) displays pages you are currently watching. For more information on how to use this special page, please [http://www.mediawiki.org/wiki/Manual:Watchlist the manual page at Mediawiki.org].
 
[[Special:Watchlist]] (available by clicking '''my watchlist''' at the top of each page when you are logged in) displays pages you are currently watching. For more information on how to use this special page, please [http://www.mediawiki.org/wiki/Manual:Watchlist the manual page at Mediawiki.org].
  
 
We are now maintaining a stand-alone [[Watchlist_How-To]] to help Fedora contributors with specific suggestions and tools.
 
We are now maintaining a stand-alone [[Watchlist_How-To]] to help Fedora contributors with specific suggestions and tools.
  
=== Summarize your changes (aka commit log message) -- this is the rule ===
+
=== 概述更改 (又叫提交日志信息) -- 这是准则 ===
  
 
We all need to be able to quickly glance at a change and know the substance of it.  A full diff is not always available. You must supply a summary of your change (''Summary:'' field when editing). This is akin to a changelog message.  Explain what you did and why, as well as other useful links and details.
 
We all need to be able to quickly glance at a change and know the substance of it.  A full diff is not always available. You must supply a summary of your change (''Summary:'' field when editing). This is akin to a changelog message.  Explain what you did and why, as well as other useful links and details.
Line 120: Line 120:
 
If you choose to not put in a summary, it should be the rare exception.  One reason is when doing a minor edit.  In that case, be sure to check ''This is a minor edit'' when saving.
 
If you choose to not put in a summary, it should be the rare exception.  One reason is when doing a minor edit.  In that case, be sure to check ''This is a minor edit'' when saving.
  
== Editing with Mediawiki ==
+
== 编辑 Mediawiki ==
  
 
{{admon/note|If you need help with syntax that is not listed here, the [http://www.mediawiki.org/wiki/Help:Contents Mediawiki Help] should contain it.}}
 
{{admon/note|If you need help with syntax that is not listed here, the [http://www.mediawiki.org/wiki/Help:Contents Mediawiki Help] should contain it.}}
  
=== Basic Syntax ===
+
=== 基本语法 ===
 
{|
 
{|
 
! What you type !! What it looks like
 
! What you type !! What it looks like
Line 137: Line 137:
 
|}
 
|}
  
=== Lists ===
+
=== 列表 ===
 
{|
 
{|
 
! What you type !! What it looks like
 
! What you type !! What it looks like
Line 175: Line 175:
 
{{anchor|Linking}}
 
{{anchor|Linking}}
  
=== Links ===
+
=== 链接 ===
 
{|
 
{|
 
! What you type !! What it looks like
 
! What you type !! What it looks like
Line 214: Line 214:
 
{{admon/note|There are two ways to use the Category links|Be sure to use the ':' before the word Category when you intend to link to a category page.  Omit the ':' when the page is supposed to be in that category.  Refer to the examples above.}}
 
{{admon/note|There are two ways to use the Category links|Be sure to use the ':' before the word Category when you intend to link to a category page.  Omit the ':' when the page is supposed to be in that category.  Refer to the examples above.}}
  
=== Tables ===
+
=== 表格 ===
 
Tables should be used sparingly and only when necessary.
 
Tables should be used sparingly and only when necessary.
  
Line 233: Line 233:
 
|}
 
|}
  
=== IRC Logs ===
+
=== IRC 日志 ===
 
IRC logs can either be surrounded in <code><nowiki><pre></nowiki></code> tags, or converted into MediaWiki pipe-tables with [http://mg.pov.lt/irclog2html/ irclog2html] and [http://ianweller.fedorapeople.org/irclog2html/ Ian's MediaWiki patch for irclog2html].
 
IRC logs can either be surrounded in <code><nowiki><pre></nowiki></code> tags, or converted into MediaWiki pipe-tables with [http://mg.pov.lt/irclog2html/ irclog2html] and [http://ianweller.fedorapeople.org/irclog2html/ Ian's MediaWiki patch for irclog2html].
  
 
{{Anchor|Structure_of_a_Wiki_Page}}
 
{{Anchor|Structure_of_a_Wiki_Page}}
  
== Structure of a Wiki Page ==
+
== WiKi 页面的结构 ==
  
 
This section describes the common structure of a wiki page.  Follow these guidelines for every wiki page.  There are additional rules used for formal Fedora documentation, covered in [[DocsProject/WritingUsingTheWiki]] ; those rules are only required for content written to follow the procedures of the [[DocsProject| Fedora Documentation Project]].  Pages that are templates of standard content that are drawn into other pages may have a different structure.
 
This section describes the common structure of a wiki page.  Follow these guidelines for every wiki page.  There are additional rules used for formal Fedora documentation, covered in [[DocsProject/WritingUsingTheWiki]] ; those rules are only required for content written to follow the procedures of the [[DocsProject| Fedora Documentation Project]].  Pages that are templates of standard content that are drawn into other pages may have a different structure.
Line 281: Line 281:
 
{{Anchor|Admonitions}}
 
{{Anchor|Admonitions}}
  
=== Notes, Tips, and Other Admonitions ===
+
=== 注解, 技巧, 其它警告 ===
  
 
These are collectively known as admonitions, and [http://docs.fedoraproject.org/documentation-guide/en_US/sn-xml-admon.html are used in DocBook]. To make a paragraph into an admonition, use the special admonition template.  A short title and a longer descriptive paragraph are recommended.
 
These are collectively known as admonitions, and [http://docs.fedoraproject.org/documentation-guide/en_US/sn-xml-admon.html are used in DocBook]. To make a paragraph into an admonition, use the special admonition template.  A short title and a longer descriptive paragraph are recommended.
Line 320: Line 320:
 
|}
 
|}
  
==== Admonition examples ====
+
==== 警告样例 ====
  
 
Examples showing context for using these admonitions:
 
Examples showing context for using these admonitions:
Line 335: Line 335:
 
{{Anchor|Marking_Technical_Terms}}
 
{{Anchor|Marking_Technical_Terms}}
  
=== Marking Technical Terms ===
+
=== 技术术语的标记 ===
  
 
Use the ''code'' markup (<code>&lt;code&gt;</code>) to mark the names of applications, files, directories, software packages, user accounts, and other words that have a specific technical meaning. This displays the marked words as <code>monospace</code>.
 
Use the ''code'' markup (<code>&lt;code&gt;</code>) to mark the names of applications, files, directories, software packages, user accounts, and other words that have a specific technical meaning. This displays the marked words as <code>monospace</code>.
Line 387: Line 387:
 
{{Anchor|Writing_Example_Commands}}
 
{{Anchor|Writing_Example_Commands}}
  
=== Writing Example Commands ===
+
=== 命令样例 ===
  
 
Example commands are one or more commands set apart from the body of the explanation.  Do not use prompt symbols or any other content that shows machine name, user, directory, etc. (which are details set in the $PS1 environment variable.)
 
Example commands are one or more commands set apart from the body of the explanation.  Do not use prompt symbols or any other content that shows machine name, user, directory, etc. (which are details set in the $PS1 environment variable.)
Line 429: Line 429:
 
</pre>
 
</pre>
  
==== Example command output ====
+
==== 命令输出样例 ====
  
 
When the example shows a command as part of showing the output to the screen, you may use a command prompt to clarify commands and output.
 
When the example shows a command as part of showing the output to the screen, you may use a command prompt to clarify commands and output.
Line 445: Line 445:
 
</pre>
 
</pre>
  
=== Try it Out Yourself ===
+
=== 你自己试试 ===
 
Try new things in the [[WikiSandBox|  Fedora Wiki Sandbox]] .  It is also a good place to see lots small samples at work.
 
Try new things in the [[WikiSandBox|  Fedora Wiki Sandbox]] .  It is also a good place to see lots small samples at work.
  
=== Creating New Pages in the Wiki ===
+
=== 在 WiKi 建立新页面 ===
  
 
The Fedora Project Wiki is large, and so there is a need to maintain a proper hierarchy and organization.  The best way to learn about these is to review [[Help:Subpages]]  and [[Help:Categories]], and then to review the existing layout of the wiki.
 
The Fedora Project Wiki is large, and so there is a need to maintain a proper hierarchy and organization.  The best way to learn about these is to review [[Help:Subpages]]  and [[Help:Categories]], and then to review the existing layout of the wiki.
Line 458: Line 458:
 
If you have questions, feel free to ask the [[Websites]]  team.
 
If you have questions, feel free to ask the [[Websites]]  team.
  
=== Important Pages ===
+
=== 重要的页面 ===
  
 
Key pages, such as Main Page, should be edited sparingly. Changes to such pages should generally be discussed on the mailing lists or on IRC before being applied. Some parts of the wiki may have different permissions. For example, the [[DocsProject]] has a section for the creation of new documentation which is restricted a bit more than the rest of the wiki. In order to gain edit access to such pages, you may have to complete additional steps. You can usually find instructions on those pages.
 
Key pages, such as Main Page, should be edited sparingly. Changes to such pages should generally be discussed on the mailing lists or on IRC before being applied. Some parts of the wiki may have different permissions. For example, the [[DocsProject]] has a section for the creation of new documentation which is restricted a bit more than the rest of the wiki. In order to gain edit access to such pages, you may have to complete additional steps. You can usually find instructions on those pages.
  
== Getting Help ==
+
== 获得帮助 ==
  
 
If ever you have questions about editing the Fedora Project wiki, or if you need help, please feel free to contact the [[Websites]] team. They have an IRC channel (#fedora-websites on freenode) and a mailing list ([http://www.redhat.com/mailman/listinfo/fedora-websites-list fedora-websites-list]) that are both effective for getting the answers you need.
 
If ever you have questions about editing the Fedora Project wiki, or if you need help, please feel free to contact the [[Websites]] team. They have an IRC channel (#fedora-websites on freenode) and a mailing list ([http://www.redhat.com/mailman/listinfo/fedora-websites-list fedora-websites-list]) that are both effective for getting the answers you need.
  
If you would like to do a lot of editing on the wiki, you should consider [[Websites/Join|joining the Websites team]].
+
如果你愿意对 wiki 做大量编辑, 你应当关心 [[Websites/Join|joining the Websites team]].
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]

Revision as of 03:27, 28 November 2008

Important.png
2008-09-06 Wiki 结构页面位置
Help:Wiki_structure 描述了本wiki的结构, 包括了页面的命名.
Note.png
标记语言的其它资源
Help:Editing from Mediawiki.org 是一个不错的标记语言帮助. 这有一张方便的 reference card 图片.
Idea.png
旧的 wiki 内容也会有帮助
旧的 wiki 和内容快照在 http://fedoraproject.org/wikiold/.
Idea.png
Wiki 迁移需要做的事
阅读 FedoraProject:Wiki migration to-do 后决定是否你需要为你的用户或 SIG/subProject 页面做些什么.

Fedora Project Wiki 对编辑来说入门是很容易的, 刚开始使用 wiki 需花点时间, 你应该看看我们准备的一些准则. 本页的内容提供了这些准则和技巧来帮助你.


这个文档分为3部分: 获得编辑权限, wiki 基本编辑, 高级编辑.

Contents

获得编辑权限

为了防止不怀好意的人破坏 Fedora Project Wiki, 我们不得不对编辑权限做限制. 要获得 wiki 的编辑权限, 你必须完成下面的步骤. 任何人都可以获得编辑权限

  1. 熟悉本页信息及本页链接到的页面信息. wiki 所遵循的基本准则都在这里. 没有遵循这些准则造成不必要的工作, 其他志愿者可能撤销你的编辑特权。
  2. Complete the Contributor License Agreement through the Fedora Account System. Signing the CLA gives the Fedora Project the ability to license your contributions to the wiki under the Open Publication License 1.0 without options. This assures that your contributions will remain forever Free for the community to use, modify, and redistribute, just like the Fedora distribution. See our Legal section for more information. Follow the instructions at Infrastructure/AccountSystem/CLAHowTo.
Note.png
If you are interested in more general website maintenance, or wish to be part of the Fedora Websites team, please see the Websites page.
Information on writing new formal Fedora documentation using the wiki is available from Writing Wiki Documentation.

准则和 Wiki 礼节

There are a few simple points you should follow as you make changes to the wiki. Below are some examples. In general, be courteous and use common sense. Defying these guidelines and causing problems are a good way to get your edit privileges revoked. If you have questions, you can ask on #fedora-websites on freenode.

介绍你自己

Before you start editing any page, kindly introduce yourself by adding your information to your wiki page. After you have registered your name in the wiki, you automatically have a personal wiki page located at http://fedoraproject.org/wiki/User:<username>, where <username> is replaced by your Fedora Account System account name. You can also easily get to your wiki page by clicking your username in the top right-hand corner of each page of the wiki.

For examples, take a look at some wiki pages of our contributors.

Make sure you mention at least your email address and, if you are on IRC often, your IRC nick and channels you are often in.

总是关注你产生或编辑的页面

It is important that you follow changes to pages you create or edit, so you can coordinate with others working in the wiki content. Wiki editors usually add notes to the pages to convey information to each other as part of working together, and it helps to keep track of these changes.

You can find the watch link in the tab bar at the top of a page when you are logged in.

设为粗体

Be bold while editing changes. Wiki changes are tracked and can be reverted when necessary. This doesn't mean you should be reckless especially when making large changes to key documents.

For more information on being bold, take a look at the be bold editing guideline on Wikipedia.

避免对法律问题页面不必要的修改

These pages have been carefully written, and the words chosen carefully. When changing these documents, it is usually best to ask for review before applying changes. You can contact the Fedora Advisory Board for assistance.

不要提供详细的禁止项目

Do not add any information that violates the law. Remember that the Fedora Project is an entity in the United States, and is governed by its laws. Avoid linking to or adding information about software that is not free and open source or that is legally encumbered. If you think you have a special exception, bring it to the attention of the Websites team for discussion. See the ForbiddenItems page for examples of items that should be avoided.

Bring questions to the Websites team for discussion. If needed, they can get the official word.

小心编辑向导或页面

Large and important guides, such as the Packaging Guidelines , are generally managed by a specific individual or small group. It is best to work with them when you feel that changes are needed.

Important pages, like the FedoraMain or Download pages, are the first thing that many visitors see. Changes to such pages should generally be left to experienced contributors. If you feel that something on such a page should be altered, bring the issue to the Websites team for discussion.

不要编辑页面只为编辑页面

Senseless edits should be avoided. Making an alteration to a page just to put your name in the edit log is unacceptable. There are plenty of pages (most of them, in fact) that have real errors that can be corrected. Instead of making pointless edits, such as removing or adding whitespace or changing links from fedoraproject.org to www.fedoraproject.org (the former is preferred), try finding errors in spelling, grammar or punctuation that can be corrected. Also, when correcting a small error, mark "This is a minor edit" using the appropriate checkbox before you save it.

避免没有协调好就重命名或移动页面的内容

Wiki pages are generally referred to and linked to from various other locations. It is important that you coordinate with the appropriate groups before moving content or renaming existing pages. It would be better to avoid doing that without strong rationale. If you wish to discuss moving a particular item, bring your questions to the Websites team.

删除页面

Wiki pages that are no longer needed can be tagged for deletion by adding {{Delete|Reason}} to the beginning of the page, this gives Wiki Administrators the ability to ensure that important or archivable content is not lost.

Follow the ideals that Fedora holds important

For example, try to remain desktop-neutral and user-friendly, especially for non-technical users who are new to Linux and to Fedora. Users may use GNOME, KDE, the console, or some other environment. Try to keep that in mind when writing instructions. Make sure that Fedora's devotion to free and open source technology is also represented properly.

对附件签名

When you attach a file to a wiki page, you should create a detached signature with your GPG key. Some file formats, such as RPM packages, support GPG keys, in which case you do not need to create a detached signature -- a signature in the file will be enough. A detached signature can be attached to the page alongside the original attachment, or can be included in the page itself.

GPG signatures allow others who download your file to verify that it came from you and has not been modified or corrupted. They do not violate your privacy in any way, they simply allow others to have confidence in the origin of your files.

Images and simple documents are safe to leave without a signature, but there would be no harm in adding one anyway to verify that you were the author.

If you do not have a GPG key or want to learn more, see the Cryptography page.

审查更改防止错误

Whether you are a skilled writer, or your English skills are not strong, invite someone else to review. Well-written documents are important to Fedora's image. Even the best writers are prone to typos or other errors. Take a moment to review your changes to catch small errors. Use the Show preview button when editing a page to check your syntax.

Fedora 是一个社区

When writing content, for the wiki or elsewhere, remember that Fedora is a community. We operate as one, unified group, moving towards common goals. We do not need to distinguish one group or class against another. For example, there is no need to distinguish between contributors who work for Red Hat and those who do not. All contributors are part of the same community. There will be cases where classification is necessary, but it can be avoided otherwise.

如果你有不知道, 随时提问

Other community members will be happy to assist you. The #fedora-websites channel on freenode is the perfect place to discuss the wiki or other Fedora websites.

关注你的页面, 其他人的页面

Two details make a Wiki successful as an open content collaboration tool. First is being able to watch content you are responsible for, to make certain it stays true to its mission. Second is being able to watch other content develop, grow, and occasionally need your help.

To watch any page on the wiki, after logging in, click the watch link in the tab bar at the top of a page. It should change to unwatch after it has finished. If a page has unwatch at the top, you are already watching that page. You can click unwatch to unwatch a page.

To receive emails for every edit, go to my preferences (at the top of the page by your name) and make sure to check the appropriate boxes in the User profile tab, under Email.

使用 Special:Watchlist

Special:Watchlist (available by clicking my watchlist at the top of each page when you are logged in) displays pages you are currently watching. For more information on how to use this special page, please the manual page at Mediawiki.org.

We are now maintaining a stand-alone Watchlist_How-To to help Fedora contributors with specific suggestions and tools.

概述更改 (又叫提交日志信息) -- 这是准则

We all need to be able to quickly glance at a change and know the substance of it. A full diff is not always available. You must supply a summary of your change (Summary: field when editing). This is akin to a changelog message. Explain what you did and why, as well as other useful links and details.

If you choose to not put in a summary, it should be the rare exception. One reason is when doing a minor edit. In that case, be sure to check This is a minor edit when saving.

编辑 Mediawiki

Note.png
If you need help with syntax that is not listed here, the Mediawiki Help should contain it.

基本语法

What you type What it looks like
'''bold text'''
bold text
''italics''
italics
'''''bold italics'''''
bold italics
<code>Monospace text</code>
Monospace text

列表

What you type What it looks like
* A list item
* Another list item
** Oh joy, more list items!
  • A list item
  • Another list item
    • Oh joy, more list items!
# A numbered item
# Another numbered item
## Sub items
## More sub items
# Third numbered item
  1. A numbered item
  2. Another numbered item
    1. Sub items
    2. More sub items
  3. Third numbered item
* An unordered item...
*# With a sub-list that is ordered
*# More steps
* Back to the first list
*# Another ordered list
*#* With its own sub point
  • An unordered item...
    1. With a sub-list that is ordered
    2. More steps
  • Back to the first list
    1. Another ordered list
      • With its own sub point

链接

What you type What it looks like
Visit [[DocsProject]] to learn more about
Fedora's documentation.
Visit DocsProject to learn more about Fedora's documentation.
Our [[Websites|websites team]] offers many
individuals who can help Fedora.
Our websites team offers many individuals who can help Fedora.
See [[Artwork#Join]] on how to
join the Art Team.
See Artwork#Join on how to join the Art Team.
[[The weather in London]] is a
page that doesn't exist yet.
The weather in London is a page that doesn't exist yet.
http://fedoraproject.org/
http://fedoraproject.org/
Here are some sites:
[http://www.deviantart.com]
[http://www.flickr.com]
Here are some sites: [1] [2]
[http://fedoraproject.org Our home page]
is full of interesting information.
Our home page is full of interesting information.
Use a ':' in the link to link
to an [[:Image:Growth_wide.jpg|image]].
Use a ':' in the link to link to an image.
The [[:Category:Documentation]] lists all 
end-user documentation.
The Category:Documentation lists all end-user documentation.
The [[Category:Documentation]] link puts
this page in the listed category; the link
appears automatically on the bottom of the
page and not inline.
The [[Category:Documentation]] link puts this page in the listed category; the link appears automatically on the bottom of the page and not inline.
Note.png
There are two ways to use the Category links
Be sure to use the ':' before the word Category when you intend to link to a category page. Omit the ':' when the page is supposed to be in that category. Refer to the examples above.

表格

Tables should be used sparingly and only when necessary.

For more advanced table usage, read up on Mediawiki.org's page on tables.

What you want How to get it
Start a table
{|
Table header
! Column 1 !! Column 2 !! Column 3
New row
|-
Table row
| Cell 1 || Cell 2 || Cell 3
End a table
|}

IRC 日志

IRC logs can either be surrounded in <pre> tags, or converted into MediaWiki pipe-tables with irclog2html and Ian's MediaWiki patch for irclog2html.

WiKi 页面的结构

This section describes the common structure of a wiki page. Follow these guidelines for every wiki page. There are additional rules used for formal Fedora documentation, covered in DocsProject/WritingUsingTheWiki ; those rules are only required for content written to follow the procedures of the Fedora Documentation Project. Pages that are templates of standard content that are drawn into other pages may have a different structure.

Note.png
Header 1 (h1) deprecated for use in markup
The header 1 is defined by the page title. When making new or migrating pages, either re-nest or re-structure the page to have only header 2 and below.
  • The title of the page is a first-level header. It is created automatically from the page title.
  • Sections are created using the equals symbols in pairs:
== Header 2 ==
=== Header 3 ===
==== Header 4 ====
===== Don't do this, 5 levels of nesting means you need a new page or three =====
  • The table of contents is automatically created and populated when the page grows big enough.
  • Anchors to sections are automatically created, with specific symbols used in place of punctuation and spaces:
This page ==> This_page
This, that, and the other page ==> This%2C_that%2C_and_the_other_page


Idea.png
You can use .2C instead of %2C for anchors
The substitute of '.' for '%' works for anchors against a specific section.

Quick Tips

These are the basic things that you need to know to edit this Wiki.

Note.png
For more information on drafting documentation on the Wiki, refer to Writing Wiki Documentation.

Learn by Example

Among the better ways to learn how to edit the wiki is reviewing the code of existing pages. This is very easy to do:

  1. Find a page whose source you would like to view.
  2. In the Navigation bar, find the combo box that reads 'More Actions:' and click on it.
  3. Select the 'Show Raw Text' option.

The wiki will display the plaintext form of that page. This is particularly valuable for learning some of the clever tricks used by wiki editors ahead of you. Those 'clever tricks' are valuable, as they allow you to do unique, interesting, and powerful things you might not have thought were possible. You might try this on pages like FedoraMain.

注解, 技巧, 其它警告

These are collectively known as admonitions, and are used in DocBook. To make a paragraph into an admonition, use the special admonition template. A short title and a longer descriptive paragraph are recommended.

What you type What you see
{{admon/note|A title|Here is more information about
this tip, with information that provides more insight
into the informative title of the initial paragraph.}}
Note.png
A title
Here is more information about this tip, with information that provides more insight into the informative title of the initial paragraph.

Indent the initial and second paragraph by one space, to ensure that the box aligns correctly.

These are the standard types of admonition:

What you type What you see
{{admon/note|This is a note|Informational paragraph
that tells more about what is going on.}}
Note.png
This is a note
Informational paragraph that tells more about what is going on.
{{admon/tip|This is a tip|Informational paragraph
that tells more about what is going on.}}
Idea.png
This is a tip
Informational paragraph that tells more about what is going on.
{{admon/important|This is important|Informational paragraph
that tells more about what is going on.}}
Important.png
This is important
Informational paragraph that tells more about what is going on.
{{admon/caution|This is a caution|Informational paragraph
that tells more about what is going on.}}
Stop (medium size).png
This is a caution
Informational paragraph that tells more about what is going on.
{{admon/warning|This is a warning|Informational paragraph
that tells more about what is going on.}}
Warning (medium size).png
This is a warning
Informational paragraph that tells more about what is going on.

警告样例

Examples showing context for using these admonitions:

Note.png
Cliffs can be very high
Wikipedia can vouch for this.
Idea.png
Standing away from cliff edges is a way to stay safe
For more information, read the cliffs(1) man page.
Important.png
Keep your children away from the cliff edge to your right
Children move around quite a bit and can easily fall off. You should hold their hand.
Stop (medium size).png
You are getting near the cliff edge
As mentioned earlier, cliffs can be very high, and it would be bad to fall.
Warning (medium size).png
You are about to fall off the cliff
Move away as quickly as possible to avert falling.

Refer to the Fedora Documentation Guide for descriptions of the types of admonition: http://docs.fedoraproject.org/documentation-guide/en_US/sn-xml-admon.html

技术术语的标记

Use the code markup (<code>) to mark the names of applications, files, directories, software packages, user accounts, and other words that have a specific technical meaning. This displays the marked words as monospace.

Use two single-quotes () to mark the names of menu items and other elements of the graphical interface. This displays the marked words in italic.

Term Mark Up Formatted example
Names of GUI applications
 '''boldface''' 
Firefox
Files, directories
 <code>inline code tags</code> 
/usr/bin/firefox
Software packages
 <code>package name</code> 
firefox-1.2.3
User accounts
 <code>username</code> 
username
Other words that have a specific technical meaning
 <code>technical term</code> 
... the class org.fedora.someJava.classname ...
Graphical menus and menu items
 ''Menu name'' 
Applications > Internet > Firefox Web Browser
Other GUI or WebUI interface element
 ''two single-ticks'' 
... click the Submit button ...
Inline command and daemons
 <code>command -option</code> <code>daemon</code>
grep httpd to find the PIDs of the running httpd processes.
Blocks of code, configuration files, etc.
 <pre>whitespace preserved< /pre> 
whitespace
    is preservered
  here
Inline pieces of code, configuration files, etc.
 <code>inline whitespace not preserved</code> 
... Next, modify the variables for set() in /path/to/org/dev108/classname ...
First term, glossary term
 ''term'' 
... Firefox is an example of a graphical user interface or GUI.
Keystrokes
 '''[Key]''' 
Press the [Enter] key ...

For example:

The <code>thunderbird</code> package installs the '''Mozilla Thunderbird'''
e-mail application. To start '''Thunderbird''', select:
  ''Applications > Internet > Thunderbird Email''.

Which produces:

The thunderbird package installs the Mozilla Thunderbird e-mail application. To start Thunderbird, select: Applications > Internet > Thunderbird Email.

命令样例

Example commands are one or more commands set apart from the body of the explanation. Do not use prompt symbols or any other content that shows machine name, user, directory, etc. (which are details set in the $PS1 environment variable.)

Enclose any example command in <pre></pre> tags:

<pre>
su -c "yum install awesome-application"
</pre>

Enter the <code>root</code> password when prompted.

Which produces:

su -c "yum install awesome-application"

Enter the root password when prompted.

Note.png
Command examples and root
Many commands require root privileges. The reader should not be logged into their system as root, and so you must specify either su -c or su - when explaining such commands.

If the command requires elements to be quoted, nesting should be " ", with the single quote marks surrounded by one containing set of double quote marks. For example:

su -c "command -o 'Some Text' -file 'More text' foo/bar"

If you need to have a series of commands or su -c is not responding as expected, have the user switch to root and warn the user to return to a normal user shell afterward.

su -
Password:
service food stop
cp /etc/foo.d/foo.conf /etc/foo.d/foo.conf.backup
vi /etc/foo.d/foo.conf
food --test-config
...
service food start
exit

命令输出样例

When the example shows a command as part of showing the output to the screen, you may use a command prompt to clarify commands and output.

$ su -c "ls -l /root"
Password: 
total 148
-rw------- 1 root root  1961 2007-09-21 02:46 anaconda-ks.cfg
-rw-r--r-- 1 root root 46725 2007-09-21 02:46 install.log
-rw-r--r-- 1 root root  6079 2007-09-21 02:42 install.log.syslog
-rw-r--r-- 1 root root  3699 2008-07-28 17:24 scsrun.log
-rw-r--r-- 1 root root 45038 2008-01-10 10:21 upgrade.log
-rw-r--r-- 1 root root  1317 2008-01-10 10:20 upgrade.log.syslog

你自己试试

Try new things in the Fedora Wiki Sandbox . It is also a good place to see lots small samples at work.

在 WiKi 建立新页面

The Fedora Project Wiki is large, and so there is a need to maintain a proper hierarchy and organization. The best way to learn about these is to review Help:Subpages and Help:Categories, and then to review the existing layout of the wiki.

Redundant names (such as Foo/FooBar/FooBarGrue) should be avoided. Remember that including 'Fedora' in the page name is redundant. Major Fedora projects do not need to have 'Project' in their page names, either. For example, the Fedora Websites Project has its page named 'Websites', not 'FedoraWebsitesProject'.

For the most part, pages should be grouped as subpages by the projects or programs they are part of. Categories will generally be created for different projects and programs, and should be created sparingly. Most pages you create should be part of a category, and many should also have appropriate tags. If you are thinking about creating a new category or tag, please ask the Websites team for advice first.

If you have questions, feel free to ask the Websites team.

重要的页面

Key pages, such as Main Page, should be edited sparingly. Changes to such pages should generally be discussed on the mailing lists or on IRC before being applied. Some parts of the wiki may have different permissions. For example, the DocsProject has a section for the creation of new documentation which is restricted a bit more than the rest of the wiki. In order to gain edit access to such pages, you may have to complete additional steps. You can usually find instructions on those pages.

获得帮助

If ever you have questions about editing the Fedora Project wiki, or if you need help, please feel free to contact the Websites team. They have an IRC channel (#fedora-websites on freenode) and a mailing list (fedora-websites-list) that are both effective for getting the answers you need.

如果你愿意对 wiki 做大量编辑, 你应当关心 joining the Websites team.