Hi everyone,
The ppc and ppc64 team members just had a meeting. One of our main
issues was reconstituting those teams because they were in a state of
disorganization. We've come up with a plan to move forward and address
Pacho's original concern about ppc/ppc64 falling behind. Here's what we
came up with:
1. We elected jmorgan as the lead for both ppc and ppc64. He's our
point person for any ppc/ppc64 related issues.
2. If you are interested in helping out, whether you are a current team
member or not, please speak up! There are people formally listed as
part of the ppc/ppc64 herds, but there's so much inactivity, we'd like
to know who's going to be active. Of course we understand there is this
thing called "real life" but there is a difference between a little help
and no involvement at all. We are considering culling the team members
accordingly. (/me hides!)
3. We are going to try to keep ppc and ppc64 going as it has been, with
the usual STABLEREQ and KEYWORDREQ. We think we can do it without
overloading ourselves, especially if we get help. We do have a shared
ppc64 system. The bigger problem is actually KEYWORDREQ's so we are
going to request maintainers not ever drop ~ppc or ~ppc64 even when they
feel a major bump has occurred, eg a deep rewrite to a library. We know
this is living dangerously but we'll going to make use of the community
in this regard --- either someone will bug us on a broken ~ppc/~ppc64
package, or we'll catch it at stabilization.
We'll try to move ppc/ppc64 chatter to those lists, but it was important
that everyone know where we're at.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : bluen...@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
