From Gentoo Wiki
Jump to:navigation Jump to:search
s390 Development
Description The s390 Development Project is devoted to keeping Gentoo in good shape on the s390 architecture.
Project email
Packages p.g.o/

Bugs Related bugs
No lead election date set
(and inherited member(s))
Parent Project Gentoo
Project listing

The Gentoo/s390 Project works to keep Gentoo the most up to date and fastest s390 distribution available. We are responsible for the maintenance of all s390 specific packages as well as testing other packages one might want to use on s390.

Bugs are tracked and resolved from the Gentoo bug tracker. Resources are listed here.


The goal of the Gentoo s390 development project is to guarantee that the s390 packages build and run correctly. By continuously enhancing the meta-data, we provide the s390 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' metadata (information about how to build packages - how to build a distribution). The s390 developers are responsible for building and testing packages using this metadata. The metadata 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.

How to participate

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 s390 community.

If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through 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, and keep working on it.