1 |
rane 08/06/18 19:15:04 |
2 |
|
3 |
Added: dev-zero.txt |
4 |
Log: |
5 |
added hkBst and ulm as nominees, moved wolf31o2 to declined section and added dev-zero's manifesto |
6 |
|
7 |
Revision Changes Path |
8 |
1.1 xml/htdocs/proj/en/council/voting-logs/nominees/2008/dev-zero.txt |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/council/voting-logs/nominees/2008/dev-zero.txt?rev=1.1&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/council/voting-logs/nominees/2008/dev-zero.txt?rev=1.1&content-type=text/plain |
12 |
|
13 |
Index: dev-zero.txt |
14 |
=================================================================== |
15 |
Background |
16 |
========== |
17 |
|
18 |
In September 2006 I became a developer after writing a lot of ebuilds in |
19 |
the Gentoo Sunrise project and helping with the postgresql ebuilds. |
20 |
Currently I'm responsible for packages in the herds samba, cpp, python, |
21 |
sysadmin and postgresql. Furthermore I'm a member of the gentoo python |
22 |
project and a glep-editor. |
23 |
|
24 |
Besides my Gentoo development work I also organize the Gentoo booth at the |
25 |
OpenExpo in Switzerland twice a year. |
26 |
|
27 |
Questions. |
28 |
========== |
29 |
|
30 |
1) What you will do? |
31 |
|
32 |
First I'll try to clean up our structure and write down clearly what we have, |
33 |
who's responsible for what and how the workflows are. You might also consider |
34 |
the GLEPs I've written as an example for what I'm trying to achive. |
35 |
|
36 |
2) Why you will do it |
37 |
|
38 |
Because I think we can't grow in a sane way anymore without having at least |
39 |
general policies written down. I don't want to over-regularize Gentoo but I |
40 |
got the impression in the last few months that we loose a lot of time |
41 |
discussing the same questions over and over again and that we're blocked by |
42 |
non-existent or -- even worse -- seemingly existing policies like GLEP 39. |
43 |
|
44 |
3) How you will do it? |
45 |
|
46 |
To keep it open and fair I'll probably do a lot of things via GLEPs. |
47 |
But even if I do believe that many things should be written down I think that we |
48 |
should never stop talking about issues. Policies are not meant to be written |
49 |
in stone, they're alive and should be revised from time to time (and we should |
50 |
not first need a catastrophe for that to happen). So I think it's not the |
51 |
council's sole responsability to generate improvements (the council is rather |
52 |
the legislature) but it's the people (users and developers alike) who should |
53 |
come up with improvements. |
54 |
|
55 |
4) What is the timescale for doing it? |
56 |
|
57 |
A half year until we get the organizational problems resolved. Another half |
58 |
year to speed up development again. |
59 |
|
60 |
5) What experience do you have with this or a similar role? |
61 |
|
62 |
While studying I currently work as a CIO in small company (~30 |
63 |
people). In highschool I was president of the students organization for |
64 |
1.5 years. |
65 |
|
66 |
6) Why do you think you are qualified? |
67 |
|
68 |
I'm dedicated and consequent. I have know-how as a leader (see above) but I |
69 |
also consider myself a good team player. |
70 |
|
71 |
7) How you plan to balance a council role with your current Gentoo role? |
72 |
|
73 |
Council decisions have absolute priority. Once the decision has been made the |
74 |
council members have to represent the decision as their own even if they don't |
75 |
like it. |
76 |
|
77 |
8) How much time can you dedicate to the council role |
78 |
|
79 |
What is needed. In case it takes more I'll first put my pet projects on hold. |
80 |
|
81 |
|
82 |
|
83 |
|
84 |
|
85 |
-- |
86 |
gentoo-commits@l.g.o mailing list |