Project:IA64

Description
The Gentoo/IA-64 Project works to keep Gentoo the most up to date and fastest IA-64 distribution available. We are responsible for the maintenance of all IA-64 specific meta-data and the testing of all other non IA-64 specific meta-data on the IA-64 architecture to ensure portability. Portability implies reusable meta-data.

Bugs are tracked and resolved from the Gentoo bug tracker and correspondence is maintained on the various IA-64 related mailing lists. (gentoo-IA-64-user, gentoo-IA-64-dev and those belonging to the sub-projects).

Goals
The goal of the Gentoo IA-64 development project is to guarantee that the IA-64 packages build using Gentoo meta-data are up to date. By continuously enhancing the meta-data, we provide the IA-64 user with the Gentoo community feeling, performance, freedom and up to dateness. The meta-distribution notion allows for a user to to be as bleeding edge as he/she wants:

Gentoo is unique because of its interpretation of the Meta-Distribution notion: all architectures share the same 'generic' meta-data (information about how to build packages - how to build a distribution). The IA-64 developers are responsible for building and testing packages using this meta-data. The meta-data gets marked 'tested' or 'stable' afterwards, depending on the building and testing experience. Our users can use (but don't have to use) this information to build a system that suits their needs.

Herds
The Gentoo IA-64 project maintains the following herds:

Participation
Can you make computers do amazing things? Are you excited about exploring areas of computing never explored before? We are continuously looking for volunteers willing to spend some of their free time on this project. In return for your work, you get the respect of the IA-64 community.

If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through bugs.gentoo.org. There are many many bugs waiting to be found and fixed and many enhancements looking to find someone to code them. Figure out a fix, implement it, test it, and then keep trying to make the patch smaller. Post it for review on bugs.gentoo.org, and keep working on it. If it seems ignored, make a new comment in the bug and/or mention it in.