1 |
The dev population is quite a strange beast. I never expected to win. |
2 |
Why would you vote for somebody who did not even publish a manifesto? |
3 |
I don't know but I love you for it. My only intention was to help offset |
4 |
dev-zero being able force the will of outside forces upon us. |
5 |
Well that has been accomplished for now (w00t). But I |
6 |
never ever expected to be ranked so high. "/me blushes" So that means you |
7 |
guys/gals expect stuff from me. Well as I never wrote a manifesto but |
8 |
you still voted for me, I guess I should share some of my ideas on what |
9 |
I'd like to see happen over the following year. |
10 |
|
11 |
The devs have a voice one time of the year: when it comes time to vote. |
12 |
But what about the rest of the year? What happens when the person you |
13 |
voted for sucks? You are mostly powerless to do anything other than be |
14 |
really vocal in what seems like a never ending battle. That needs to |
15 |
change. I'm not quite sure how. But I'd like to see the dev body have a |
16 |
year-round voice in the council. Either via quick votes year-round |
17 |
on topics or simply by having discussion in the channel. Devs should have |
18 |
a right to voice their concerns to the council and engage in interactive |
19 |
conversations without being labeled troll. |
20 |
|
21 |
Another one of the things I'd like to see and help reform with the |
22 |
council. First off it spends way too much time on EAPI/PMS. There is no |
23 |
reason to make the council an extension of the portage team. Portage is |
24 |
still the official package manager of Gentoo. Granted it's good to |
25 |
accommodate others to an extent and I've always kept an open mind on other tools. |
26 |
Alternatives are good as there is always the right tool for the task at hand. But |
27 |
the council really should not be getting involved most of the time unless there |
28 |
is a conflict which can't be worked out among the masses and those trying to get |
29 |
portage to adopt new features. If the dev body wants it otherwise then |
30 |
I'd like to turn my vote over to you the devs. Each and every time the |
31 |
council wants/has to vote on an EAPI/PMS feature then I'll happily put my |
32 |
vote in your hands. You fire up that old votify system and use my vote |
33 |
as yours. Note however that zmedico is not in favor of his time being |
34 |
wasted on deciding what PMS/EAPI features are good. He simply likes bugs |
35 |
and solving those. He likes giving us new features and tends to be more in |
36 |
favor of the devs and community figuring out what is best for us. |
37 |
An EAPI review committee could work well also. As long as we could get |
38 |
non bias people in there. |
39 |
|
40 |
The council should be more about community vs technical issues only. |
41 |
We have lots of top level projects within Gentoo which have simply given |
42 |
up on the council as being an outlet to accomplish anything useful. |
43 |
It should be our job to look at the projects in Gentoo. Look at the ones |
44 |
that have a healthy community and encourage and promote them in ways. |
45 |
|
46 |
For example prefix comes to mind. It was a project I did not like at |
47 |
first. I'm not even a user. And there are things I surely don't like |
48 |
about it as is. But there is community support and it's the icing on the |
49 |
cake for some. So I'll back the fsck up and give credit where it's due. |
50 |
This is a perfectly good example of a project/fork that needs to come |
51 |
back home. Perhaps it's time to cherry pick some more stuff/people out |
52 |
of Sunrise? |
53 |
|
54 |
desultory points out any two council members can decide to approve anything, |
55 |
and that decision is considered to be equivalent to a full council vote |
56 |
until the next meeting. I vaguely recall that rule. I'm not sure about you, |
57 |
but I think that is a little to much power to put in the hands of a few. |
58 |
Any dev mind if we dump that power? |
59 |
|
60 |
Meetings will likely go back to one time per month and be +m with +v be |
61 |
handed out per request with open chat pre/post meetings. The reason for |
62 |
this is to keep the meetings on-track. I won't engage in endless |
63 |
discussions. Facts can be presented. They will be reviewed on merit, |
64 |
technical and social. |
65 |
|
66 |
The reason the meetings should go back to monthly is to allow those who |
67 |
are council members in Gentoo to accomplish things other than the |
68 |
council only. We all have personal lives and we all have our respective |
69 |
roles we play outside of the council. Another note on meetings. The time |
70 |
they are held currently don't fit well with my work schedule. |
71 |
|
72 |
I'm not subscribed directly to the gentoo-dev mailing list anymore |
73 |
outside of post-only. And I don't plan to re-subscribe. I do browse |
74 |
the archives regularly however. If there is some topic that should |
75 |
be brought to my attention please point it out to me directly on irc |
76 |
or CC: me. |
77 |
|
78 |
Thank you all and I will try not to let you down. Unless you were one of |
79 |
the ones who wanted to me lose. Then sorry, but I'm going to have fun |
80 |
disappointing you, by doing what is best for Gentoo. |
81 |
|
82 |
If you have any ideas on how you think the council should function or |
83 |
reform itself. Please start a new thread or email those who think will |
84 |
listen to those ideas. I'm open for some real change as long as it's |
85 |
for the the positive. |
86 |
|
87 |
So lets have some damn fun again !@#$ |
88 |
Thanks. |