Getting involved (正體中文)

From ArchWiki
Revision as of 08:18, 5 March 2011 by Thestinger (Talk | contribs) (rm eng cats)

Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary end

生物學裡,互利共生(Mutualism):是指在生物界中某兩物種間的一種互相依賴、雙方獲利的專性共生關係。這一觀念同樣適用於 Arch 社群裡主動積極想參與並貢獻一己之力於其所喜愛的 GNU / Linux 發行版的成員。這種參與不僅有利於社群的成員和他們的Archers同胞們,也能造福所有自由和開放源碼軟體_(en)愛好者.


其中一個最簡單的參與方式便是加入Arch Linux的論壇。請閱讀論壇禮儀,然後再隨時分享您的想法,伸出手來幫助新用戶,並結識您的社群。使用論壇的報告功能(在右下角的所有論壇帖子)提醒論壇團隊有關的濫用。


ArchWiki 是一個 社群化 的文件工程。若你覺得有能力協助編輯,請看看你是否可以管理下列標示的任務。

  1. Flag articles with appropriate article status templates (e.g. Template:Codeline, Template:Codeline, Template:Codeline, etc.)
  2. Add content to stubs and expand incomplete or poorly-written articles.
  3. Add or improve translations; ensure that translations are in sync with each other.
  4. Reduce and combine duplicate pages.
  5. Correct inaccurate content.
  6. Reduce the number of categories. Scan the wiki for similar categories that should be combined; improve wiki navigation.
  7. Categorize uncategorized pages.
  8. Add article summary boxes to all articles.
  9. Update the FAQ with relevant questions from the forum and remove obsolete questions.

Other useful pages for cleanup:

In the long run, the goal is a professional and easily-navigated wiki, such that supplementary guides, documenters, etc. are unnecessary. This is a community effort, but wiki maintenance is often a tedious and thankless task. So please consider the following while editing the wiki:

  1. Correct spelling, grammar, language, and style.
    • Remove extraneous links and content; text should be concise, tight, and readable.
    • Remove personal references ("I like to...", "My machine...") to maintain a professional tone.
    • Ensure all pages follow a similar style and layout.
  2. Do not post scripts that you have not tested, especially when replacing a working script.
  3. Giving credit is not "pimping". Respect others and their contributions.
  4. Disparaging comments/terms are inappropriate.
If you take on the task seriously, a formal position as a wiki maintainer may be in order. This gives the job purpose and recognition.


Opening (and closing) bug reports on the Arch Linux Bugtracker is one of the possible ways to help the community. However, ineffective use of the bug-tracker can be counter-productive instead of being useful. This article will guide anyone wanting to help the community efficiently by reporting or hunting bugs.

See also: Bug Squashing Day


The Arch User Repository is a community-driven repository of PKGBUILDs for Arch users. Packages in the AUR are built by the PKGBUILDs and are not pre-built binaries like from the official repositories. The AUR was created to organize and share new packages from the community and to help expedite popular packages' inclusion into the Template:Codeline repository.

'Rolling Release' ezine

Contribute to Rolling Release, the official Arch Linux ezine. It is a community-backed, web-based publication that is always looking for contributers, artists, and the like.

Community projects

Arch has a vital and active community of software developers and contributing projects. If you have a project you would like to link to, this is a great place to do it. Include a link to your project, the date your project started, and a brief (one or two sentence) description of your project.

Note: All projects listed here are community projects. None of these projects are considered official Arch projects.

Arch Based Distributions

Other distributions based on Arch Linux

AUR Helpers

Utilities to aid end users in using the AUR

Pacman GUI Frontends

Graphical front-ends for pacman


Projects that don't quite fit into any existing category

A third-party package repository and online discussion board for Arch Linux pro-audio users
A project to get a working Arch system on GNU/Hurd.
A collection of some of the popular games in [unsupported], to save archers compilation time. They've also patched up many broken games that wouldn't compile. emails, Gmail based
Arch Linux Blogs
Mobile access to the emails
Shell + GTK+ GUI application that gives you control over services in rc.d and settings in rc.conf
Google Earth Arch user map
A collection of humorous quotes from #archlinux
Making Arch suitable for server use
Useful scripts, mods, and tips
namcap is an utility for Arch Linux which helps in automatic detection of common mistakes and errors in PKGBUILDs. This page is an automatically generated report obtained after running namcap against the core, extra and community trees.
Arch-OS X - Package management for OS X via Template:Codeline. Here is the forum thread.
An ALPM package and PKGBUILD parser in Python
Xyne's contributions to the Arch Linux community
Collect & Share PKGBUILD in Git's way

As a developer...

This entry is mainly based on this post in Arch's BBS

Firstly, remember that the main motivation for your work on Arch should be helping the whole community, and not trying to become an "Arch developer" by any means. Secondly, you are also part of the community; to provide help to others means you will also help yourself.



As an artist...

Feel free to share wallpapers, splash screens, color palettes, widgets, themes, etc. with the community on the forum.

See also: