1 |
On Wed, 4 Oct 2006 09:21:08 -0400 |
2 |
"Thomas Cort" <linuxgeek@×××××.com> wrote: |
3 |
|
4 |
> > The "minority" arches like mips, sparc etc seem to get along quite |
5 |
> > happily. |
6 |
> |
7 |
> Not the "minority" arches like m68k, s390, alpha, ... |
8 |
|
9 |
I haven't seen any significant numbers of complaints. What exactly |
10 |
about those arches do you think is a problem? |
11 |
|
12 |
> > > - Reduce the number of projects by eliminating the dead, weak, |
13 |
> > > understaffed, and unnecessary projects |
14 |
> > |
15 |
> > Weak: Be more specific. What are the "weak" projects, and why? |
16 |
> |
17 |
> Projects that don't achieve anything, have no goals, and don't show |
18 |
> any promise of doing anything productive. |
19 |
|
20 |
By "specific" I meant which projects exactly - i.e name some, and |
21 |
explain how the weakness you perceive is a problem. |
22 |
|
23 |
> > Understaffed: this issue manifests itself as a project being slow to |
24 |
> > update. However the only place this is an issue is for security |
25 |
> > issue management. Another solution to under-staffing is to reduce |
26 |
> > expectations. |
27 |
> |
28 |
> The more we reduce expectations, the more it will hurt users. We |
29 |
> should be raising expectations and following through. |
30 |
|
31 |
You should only raise expectations when you know you can follow through, |
32 |
not the other way around. Raising expectations before being able to |
33 |
follow through leads to disappointment, which is bad. |
34 |
|
35 |
> > Unnecessary: again, be more specific. What are the "unnecessary" |
36 |
> > projects, and why? |
37 |
> |
38 |
> Projects that aren't needed to further Gentoo and are not helpful to |
39 |
> users or developers. |
40 |
|
41 |
Again, by "specific" I meant which projects, by name, do you think meet |
42 |
those criteria. Explain why you consider those projects to be a |
43 |
hindrance to users or developers. |
44 |
|
45 |
-- |
46 |
Kevin F. Quinn |