Getting involved (Italiano)
|- | style="text-align: left; padding: 3px" | Quest'articolo descrive vari modi in cui gli utenti di Arch (sia nuovi che veterani) possono contribuire a questa comunità. Notare che questa non è una lista esaustiva. |- style="text-align: center; height: 1.5em; border-bottom: 5px #08c solid;" ! style="background: #333; color: white; padding: 2px;" | Pagine correlate |- | style="text-align: left; padding: 3px" | Arch User Repository (Italiano) |- | style="text-align: left; padding: 3px" | Help:Editing (Italiano) |}
In biologia, il mutualismo è l'interazione tra due organismi dalla quale entrambi ricavano un beneficio. Questo principio si può anche applicare ai membri volenterosi e motivati della comunità di Arch che vogliono essere coinvolti e contribuire alla loro distribuzione GNU/Linux preferita. Da questa partecipazione traggono vantaggio non solo i membri della comunità e i loro compagni Arcieri (da Archers), ma potenzialmente tutti i fan del software libero ed open source.
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.
- Flag articles with appropriate article status templates (e.g. Template:Codeline, Template:Codeline, Template:Codeline, etc.)
- Add content to stubs and expand incomplete or poorly-written articles.
- Add or improve translations; ensure that translations are in sync with each other.
- Reduce and combine duplicate pages.
- Correct inaccurate content.
- Reduce the number of categories. Scan the wiki for similar categories that should be combined; improve wiki navigation.
- Categorize uncategorized pages.
- Add article summary boxes to all articles.
- 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:
- 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.
- Do not post scripts that you have not tested, especially when replacing a working script.
- 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.
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.
- Other distributions based on Arch Linux
- Utilities to aid end users in using the AUR
- 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.
- @archlinux.us emails, Gmail based
- Arch Linux Blogs
- Mobile access to the @archlinux.us 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.
- 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: http://www.archlinux.org/art/