1 |
Hi all, |
2 |
|
3 |
Sorry I have not managed to formulate a manifesto sooner. If you |
4 |
haven't voted yet, please consider whether you think my positions as |
5 |
formulated below make sense. |
6 |
|
7 |
I've been a Gentoo user since about 2004 and developer since for 7 |
8 |
years now (I think?). My home team is the Python project, where I was |
9 |
the elected lead for a couple of years before handing that role over |
10 |
to the very capable Mike G. In my day job, I'm the manager of a C++ |
11 |
development team (jobs available in C++ and Java, BTW!); in my spare |
12 |
time I do a lot of open source work (100 commits in 15 projects in the |
13 |
last month), mainly in Python and more recently in Rust. |
14 |
|
15 |
For me, Gentoo is about being modular, flexible, and therefore in many |
16 |
ways supporting of doing cutting-edge stuff with. In order to improve |
17 |
further, I see two important goals: improve the community, and make |
18 |
sure we don't get stuck with legacy stuff/scaling problems. |
19 |
|
20 |
Improving the community: |
21 |
|
22 |
Personally I feel that many of our discussions devolve into long |
23 |
threads with long emails reiterating the same positions over and over. |
24 |
If you, too, feel that this is an issue, I would like to take a bit |
25 |
more active role in moderating discussions in our community (I'm |
26 |
mainly thinking on gentoo-dev), or empowering others to work on trying |
27 |
to better moderate mailing list threads, for example by making sure |
28 |
summaries are posted along the way to keep things accessible. With a |
29 |
pretty big team, we need to make sure that we keep moving forward, |
30 |
instead of getting bogged down in the status quo. |
31 |
|
32 |
At the same time, some individuals take so much responsible that they |
33 |
can come across quite hostile, even when they act with the best |
34 |
interest of the distribution at heart. In the past, I have reached out |
35 |
to some on an individual basis to make sure they're okay, to discuss |
36 |
how responsibilities can be shared better, and how such outbursts can |
37 |
be avoided. I think it can be useful to zoom out a bit and figure out |
38 |
how things can be managed/improved without placing an undue burden on |
39 |
some individuals that will feel a lot of stress from the |
40 |
responsibility. |
41 |
|
42 |
Finally, recruitment is ever important. Improving our contribution |
43 |
"funnel" (going from being an interested outside observer, to being a |
44 |
user, to filing a bug, to creating a pull request, to becoming a |
45 |
developer) is very important to me to guarantee the long-term health |
46 |
of the distribution. |
47 |
|
48 |
Improving the code/technical stuff: |
49 |
|
50 |
As Gentoo ages and grows, I worry that we're taking longer and longer |
51 |
to move stuff forward. For example, think of stabilizing new Python |
52 |
versions, stabilizing Apache 2.4 (where I took a somewhat active role) |
53 |
or bringing new gcc versions to all of our users. Having a single |
54 |
obscure blocker can sometimes delay the process for everyone else for |
55 |
months, which I think will grow worse over time and become |
56 |
unacceptable. We will need to think about better ways to move forward. |
57 |
|
58 |
Note that I'm largely a user of the stable distribution (on amd64), |
59 |
with targeted unstable packages where I know I can trust and/or track |
60 |
upstream. We will have to figure out ways to leave un(der)maintained |
61 |
packages behind sooner if we are to keep up the pace -- and I think |
62 |
with today's software not keeping up to date is not an option. |
63 |
Security is another part of this puzzle that I think is extremely |
64 |
important. |
65 |
|
66 |
I'm not a bash or PMS wizard -- others are much better for that. |
67 |
Instead, expect me to focus on bigger picture things, but with deep |
68 |
software engineering experience. If this sounds useful/interesting, |
69 |
please consider voting for me. If you have any questions or feedback, |
70 |
please let me know! |
71 |
|
72 |
Thanks, |
73 |
|
74 |
Dirkjan |