From ArchWiki

This article is a stub. It may be confusing, not contain enough information, or be a placeholder for an article to come. People are invited to expand it to full article status and remove this box.

This entry is mainly based on this[1] post in Arch's bbs

First of all, 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. You also are part of the community, or at least you should if you're reading this; to provide help to others means, at the same time, to help yourself.

[edit] What should 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 and gain some "popularity" towards Arch's developers:

• Become well known in the community by helping people.
• Answer questions on the forum, IRC, and mailing lists.
• Join the Trusted Users to gain packaging experience to show your skills.
• Submit packages to 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 the wiki, add new pages, clean up existing pages, and make sure the procedures are up-to-date.
• Submit translations.

[edit] Will I be chosen?

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.