|Gentoo Linux s390 Development|
|Description||The s390 Development Project is devoted to keeping Gentoo in good shape on the s390 architecture.|
No lead election date set
(and inherited members)
|Parent Project||Gentoo Base System|
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 meta-data and the testing of all other non s390 specific meta-data on the s390 architecture to ensure portability. Portability implies reuseable metadata.
Bugs are tracked and resolved from the Gentoo bug tracker.
The goal of the Gentoo s390 development project is to guarantee that the s390 packages build using Gentoo meta-data are up to date. 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 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.
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 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 #gentoo-zseries.