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