Project:PowerPC

Has Name::PowerPC Development
Description Has Description::The PowerPC Development Project is devoted to keeping Gentoo in good shape on both 32-bit and 64-bit PowerPC architecture.
Project email Has Contact::ppc@gentoo.org
IRC channel #gentoo-powerpc
Lead(s) none
No lead election date set
Member(s) SMW::off
  • Agostino Sarubbo (ago)
    ppc/ppc64 stabilization/security
  • Anthony G. Basile (blueness)
    ppc/ppc64 keywording/stabilization
  • Georgy Yakovlev (gyakovlev)
    everything ppc64/openpower
  • Luca Barbato (lu_zero)
    ppc/ppc64 keywording/stabilization
  • Matt Turner (mattst88)
  • Sam James (sam)
  • Sergei Trofimovich (slyfox)
    ppc/ppc64 keywording/stabilization
  • Mike Frysinger (vapier)
    ppc/ppc64 keywording/stabilization
  • Mikle Kolyada (Zlogene)
    ppc/ppc64 keywording/stabilization
SMW::on
Subproject(s)
(and inherited member(s))
(none)
Parent Project Base System
Project listing

The Gentoo/PowerPC Project works to ensure that Gentoo is the most up to date and robust PowerPC distribution available for both server and desktop applications.

Bugs are tracked and resolved from the Gentoo bug tracker . For PowerPC bugs, please see this link . Correspondence is maintained on the PowerPC related mailing lists, gentoo-ppc-user and gentoo-ppc-dev. For more information on PowerPC mailing lists, please see the Gentoo Mailing list overview . Additionally, the PowerPC team is almost always available in #gentoo-powerpc on freenode.

Goals

The goal of the Gentoo PowerPC development project is to guarantee that the PowerPC packages built using Gentoo meta-data (ebuilds) are functional and up to date. By continuously testing new packages, maintaining existing packages and providing user support, the Gentoo PowerPC team provides the PowerPC user with a modern distro based on community, performance and freedom. Utilizing Gentoo's meta-data based distribution allows a user to to be as bleeding edge or as conservative as is desired.

Gentoo is unique because all of its supported architectures share the same generic meta-data information (ebuilds) which describe how to build packages. These packages are combined to form the foundation of this distribution. The PowerPC developers are responsible for building and testing ebuilds and marking them as tested (~ppc/~ppc64) or stable (ppc/ppc64). Our users can use this information, along with the Portage application, to build a system that suits their needs, whether it is a stable server, embedded system or a bleeding edge desktop system.

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.

If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through our bugs . There are always packages that need to be tested, bugs waiting to be found and fixed and enhancements waiting for someone to code them. Feel free to ask the PPC development team on IRC what you can help us with!

For more information on how the PPC team recruits please read our recruitment page.

See also

  • PPC — a landing page for those interested in the ppc and ppc64 architectures.
This article is issued from Gentoo. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.