1 |
Fellow developers, |
2 |
|
3 |
the following is my manifesto for this council election. |
4 |
|
5 |
My background: |
6 |
|
7 |
I have been a gentoo developer since 2004, and a user since approximately |
8 |
2001. I also have some experience with RedHat Linux and Debian in the |
9 |
earlier days of these distributions (Debian 3.0 and RH 6.0). I have also |
10 |
worked on and continue to work on the Speakup screen reader driver in |
11 |
the linux kernel. |
12 |
|
13 |
My thoughts for the 2013-14 council term: |
14 |
|
15 |
These are basically the same ideas I have followed during my last term |
16 |
on the council. |
17 |
|
18 |
1. The council should stay out of the way of innovation, which comes |
19 |
from the individual developers. |
20 |
|
21 |
2. Developers also have a responsibility to maintain packages in a way |
22 |
that is in line with the gentoo philosophy, which includes things like |
23 |
following upstream recommendations unless we have a technical reason not |
24 |
to, making sure patches we do apply can be sent upstream (or |
25 |
documenting why we need them), and giving users reasonable control over |
26 |
packages. |
27 |
|
28 |
3. When the council is asked to make a decision, there are several |
29 |
things it should consider. |
30 |
|
31 |
- The council should make sure it understands the issues involved |
32 |
before voting. |
33 |
|
34 |
- The council should not take an extremely long time to make a |
35 |
decision. We are not going to be able to please everyone in Gentoo |
36 |
all the time, and we are not going to be able to please everyone on |
37 |
the council. |
38 |
|
39 |
- the council should consider how much extra work it puts on developers |
40 |
and how much its decisions will cause Gentoo to diverge from upstream |
41 |
recommendations. I feel that the council should exercise caution when |
42 |
asking developers to do custom work which diverges from upstream |
43 |
recommendations. |
44 |
|
45 |
4. I believe we can learn from the past, and improve upon it. Continuing |
46 |
to do things like we have in the past is not a bad thing in itself. |
47 |
However, using what we have done in the past to block change can be a |
48 |
bad thing. I understand that people are used to doing things a certain |
49 |
way. However, that alone is not justification for continuing to do things |
50 |
the same way in the future. |
51 |
if we need to make a change, we should make sure that |
52 |
change is backward compatible with what we have, or if this is not |
53 |
possible, provide the smoothest possible route forward for our users. |
54 |
|
55 |
If anyone has any questions for me about any of these points, feel free |
56 |
to ask. |
57 |
|
58 |
William |