Getting involved (Українська)

From ArchWiki
Jump to: navigation, search

Tango-preferences-desktop-locale.pngThis article or section needs to be translated.Tango-preferences-desktop-locale.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Getting involved (Українська)#)

В біології, мутулізм - взаємокорисний механізм співіснування декількох організмів. Даний принцип можна застосувати і по відношенню до активних і мотивованих учасників спільноти Arch, які бажають прийняти участь у її розвитку та внести свій вклад в улюблений дистрибутив GNU/Linux. Така діяльність приносить користь не лише учасникам спільноти Arch, а й, потенційно, всім фанам вільного програмного забезпечення.

Arch Linux survives because of the tireless efforts of many people in the community and the core development circle. None of us are paid for our work, and we do not have the personal funds to sustain server costs ourselves. There are many ways to help support Arch Linux. If technical development, documentation, or support aren't your strong points, you could certainly help us by dropping a few bucks our way.


One of the easiest ways to get involved is participating in the Arch Linux Forums. Please read Forum etiquette first, then feel free to share your ideas, lend a helping hand to new users, and get to know your community. Use the forum Report feature (at the lower right of all forum posts) to alert the forum team of abuse.


Wikis, by design, thrive on collaboration.

ArchWiki is a community documentation process. The contents are created by the community for the community. Contributors volunteer their time and energy to share their knowledge and skill with the community. All users are encouraged to contribute. Tasks on ArchWiki can roughly be divided into the following:

  • Technical maintenance
  • Content management
  • Content editing
  • Content creation and translation

If you feel capable of editing wiki pages, please see if you can manage tasks outlined in this section.

  1. Flag articles with appropriate article status templates (e.g. {{Deletion}}, {{Out of date}}, {{Translateme}}, 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 or outdated content, spelling, grammar, language, and style.
  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. 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 [community] 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.

Arch projects

You can find here the list of git repositories for official Arch Projects.

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

Rc.conf GUI Frontends

Graphical front-ends for rc.conf


Projects that do not quite fit into any existing category
Google Earth Arch user map
A third-party package repository and online discussion board for Arch Linux pro-audio users emails, Gmail based
Arch Linux Blogs
Mobile access to the emails
  • Arch Quote Database (dead)
A collection of humorous quotes from #archlinux
Arch Linux group for users and professionals.
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.
  • Pacman on OS X (dead as of 2011-03-23)
Arch-OS X - Package management for OS X via pacman. Here is the forum thread.
An ALPM package and PKGBUILD parser in Python
Xyne's contributions to the Arch Linux community

As a developer...

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.

What can I do?

Here is a list, in no particular order, of things that you may want to do in order to make yourself useful to the community:

  • Establish a reputation as being helpful by offering assistance whenever possible
  • Answer questions on the forum, IRC, and mailing lists
  • Join the Trusted Users to gain packaging experience to show your skills
  • Submit packages to the AUR
  • Join one of the offshoot projects that may be incorporated into Arch mainstream someday, or start your own
  • Work on pacman, makepkg, initscripts, or other source code and submit patches to the bug tracker
  • Traverse the bug tracker and fix existing bugs
  • Find and submit new bugs
  • Fix wiki errors, add new pages, clean up existing pages, and make sure the procedures are up-to-date
  • Help patrolling the Recent Changes in the wiki
  • Submit translations

How can I become an Arch developer?

Usually, new developers are picked by the existing developers as the workload increases. Sometimes they post a position and you can apply to fill it, but more often, they just invite somebody they know would be good at it and would fit in well with the rest of the team. Having a portfolio of Arch contributions is the best way to make it on the team.

As an artist...

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

See also:


Current cleanups

Earlier cleanups