1 |
Hi! |
2 |
|
3 |
I'm not a dev (just someone donating 10GB of traffic per day from |
4 |
his private server to Gentoo), but that's exactly why I think I |
5 |
need to chime in. |
6 |
|
7 |
On Mon, 31 Jul 2006, foser wrote: |
8 |
> 1. Stale ebuilds are often stale for a reason, there is |
9 |
> obviously not enough interest to add and maintain them. Not |
10 |
> just on the developer side, but also on the user side. If |
11 |
> someone really cared enough he/she would go trough the process |
12 |
> of becoming a dev. |
13 |
|
14 |
You're kidding, right? I for one simply can't spare the time to |
15 |
become involved as a dev. Now before you're starting to say that |
16 |
I'm a freeloader and I should just deal with what's there, a few |
17 |
remarks: |
18 |
|
19 |
- I *do* contribute. My private rsync-server has served over a terabyte |
20 |
of data since I've been running it for Gentoo (somewehre in |
21 |
2002? Years ago, in any case) |
22 |
- I do contribute to other F/OSS projects. Do I have to |
23 |
contribute to any project where I'd like to see a change? Isn't |
24 |
a enhancement reuqest a kind of contribution (as long as it's |
25 |
beyond "this sucks, change it!") |
26 |
|
27 |
> Then what is a solution to these ebuilds ? I for one would like |
28 |
> to see them go upstream, like rpm's and deb's . That would make |
29 |
> it clear that these ebuilds are not Gentoo approved, but would |
30 |
> provide a starting point for the user who would want to use |
31 |
> such a package. I think that was always the main idea when |
32 |
> overlays got introduced to portage. Sunrise just lowers the |
33 |
> step to get these often mediocre ebuilds, people can get them |
34 |
> right now, just not as easy. |
35 |
|
36 |
It's about user experience. I'm not saying any and all M-W |
37 |
ebuilds should get into the tree, but I have a strong feeling |
38 |
that *more* should go in - in unison with stale stuff being |
39 |
removed. But the latter is another project: treecleaners (at |
40 |
least from what I've read). |
41 |
|
42 |
I think Gentoo has a sort-of Debianesque problem: the tree is |
43 |
ever growing which results in growing pains (Debian has other |
44 |
pains but the problem is growth, still). I don't know any other |
45 |
remedy than to keep the tree lean - but not only by being wary of |
46 |
too many new ebuilds. Old ones have to go, too. |
47 |
|
48 |
As a result, a question: how many Gentoo users need to voice |
49 |
interest in an ebuild/package to make it "wortwhile"? |
50 |
|
51 |
I initially provided an ebuild for a package I maintain. I also |
52 |
provide a new ebuild for every new version. For this, proxy |
53 |
maintainership is the thing to do, IMO. |
54 |
|
55 |
> 3. Although I agree Sunrise may lower the step to becoming a |
56 |
> dev, I doubt it will have a serious positive impact on our |
57 |
> developer base and as such there is no reason to support |
58 |
> Sunrise officially. I think the people attracted to Sunrise |
59 |
> development are the ones that fall in the category 'want to be |
60 |
> there, but don't really have the time/skills'. Those people |
61 |
> will not evolve to real developers; they either will stick it |
62 |
> out in Sunrise for a short while or keep to a very small subset |
63 |
> of it. |
64 |
|
65 |
What about those that are able to put together a dead simple |
66 |
ebuild and just want it submitted and *not* rot in Bugzilla? |
67 |
|
68 |
I can understand that some people go for sunrise because some of |
69 |
their ebuild submissions just went stale and then started to rot |
70 |
in bgo. |
71 |
|
72 |
As for official vs. non-official: I don't care either which way. |
73 |
I think it's mostly about truth in advertising: If it's treated |
74 |
by the majority as being official, it's official. As for URLs: |
75 |
how do you think phishing works? People (mostly) don't look too |
76 |
closely at URLs. The layout/logos etc of a page are an entirely |
77 |
different matter. Just my EUR0.02 |
78 |
|
79 |
> My prediction is that Sunrise will see a high turnover of |
80 |
> 'developers', either because they are there for one specific |
81 |
> package (probably fresh and included in the main tree when |
82 |
> mature) or find out they lack the time to really invest in |
83 |
> learning the full extent of ebuilding. Also 'junior' devs on |
84 |
> Sunrise might not take that extra step towards devhood because |
85 |
> they got the influence they want, as such we might lose out on |
86 |
> devs that never develop beyond Sunrise contributors. |
87 |
|
88 |
Well, I think having more candidates will not only result in more |
89 |
"rejects" but also in more acceptable devs. As for the entry |
90 |
step: maybe it's too high now and with Sunrise one could find out |
91 |
where the sweet spot for it lies? |
92 |
|
93 |
Also: do you really want to have junior devs that are only in it |
94 |
for the influence? |
95 |
|
96 |
> As a developer I would not really think of Sunrise developers |
97 |
> any different than someone coming 'fresh' to Gentoo developing. |
98 |
> I would still require them to work on real bugs for a good |
99 |
> while to see their intentions/devotion over time before I would |
100 |
> even consider submitting them for real developership. In that |
101 |
> sense Sunrise would only lengthen the time a wannabe dev has to |
102 |
> spend in the no-mans land between active user and official |
103 |
> developer. |
104 |
|
105 |
So? Then Sunrise is a training ground. I don't see harm in that. |
106 |
|
107 |
> In conclusion these 3 points come together here : being a dev |
108 |
> is not about adding new ebuilds to the tree, it is about |
109 |
> maintaining what is already there. Dealing with bugs and users. |
110 |
> That aspect of Sunrise is not at all tackled in its goals. What |
111 |
> are the longterm prospects of ebuilds in the Sunrise tree ? |
112 |
> That is what QA is about, providing a stable base to work on. |
113 |
> I do not think that devs who mainly add ebuilds and new |
114 |
> packages to the tree are good devs, the real job is maintenance |
115 |
> and bughandling. In that sense Sunrise might be giving the |
116 |
> wrong impression to wannabe devs. |
117 |
|
118 |
Being a dev is three things I'd say: create, maintain, remove. |
119 |
Some may lean more to any of the three (we're humans, after all). |
120 |
The major part of the "workforce" should do maintenance, though. |
121 |
This is independent of portage, btw, most other projects would |
122 |
fall into the three-fold as well. |
123 |
|
124 |
As for the ebuilds in Sunrise: Think of it as an ebuild checker |
125 |
which is at least theoretically more capable than any automated |
126 |
system: There are humans involved that are willing to check it. |
127 |
|
128 |
People who use Sunrise as an overlay and then come whining to bgo |
129 |
about their failed ebuild can be told. |
130 |
|
131 |
Idea: should it be more obvious in emerge --info and ebuild |
132 |
failure that an overlay is involved? If it's obvious enough, I |
133 |
don't see a problem. Also, a command that lists all installed |
134 |
packages that come from an overlay might be useful (maybe even a |
135 |
sa part of --info). |
136 |
|
137 |
> * The rise of project Sunrise |
138 |
> |
139 |
> Now for the second big point concerning Sunrise : how it came into |
140 |
> being. |
141 |
|
142 |
On this, I can hardly comment because I know very little of the |
143 |
lifecycle of Gentoo projects. Also: if an idea is good, it may be |
144 |
stained a bit if it's put through with the wrong measures. That |
145 |
doesn't make it a *bad* idea out of the blue, though. |
146 |
|
147 |
> * The implications of sunrise |
148 |
> |
149 |
> What will Sunrise mean to the general developer ? |
150 |
> |
151 |
> Again here I can share my experiences with a similar project, the |
152 |
> infamous BMG was created with similar goals and turned out to be a |
153 |
> serious nightmare for the gnome team. At a certain point in time every |
154 |
> bug we got had to be double checked for possible overlay problems. |
155 |
|
156 |
This might be alleviated with the more prominent warning display |
157 |
in --info as I noted above. |
158 |
|
159 |
> I cannot count the times I had to spend hours on an |
160 |
> unexplainable problem to find out in the end that it was caused |
161 |
> by BMG ebuilds. This is incredibly destructive for my mood, not |
162 |
> to mention the time wasted which could've been spent on real |
163 |
> problems. |
164 |
|
165 |
I do understand this. There's little more frustrating than |
166 |
trying to fix one's own stuff and after hours of running into |
167 |
walls finding out that the problem was caused in some completely |
168 |
different part of the world. |
169 |
|
170 |
> The other side of the medal is that there are false-positives |
171 |
> where you think it's BMG, but it really isn't and I can tell |
172 |
> you that is not a nice experience for the user and dev alike. |
173 |
> BMG was mainly gnome oriented, so a lot of devs may never have |
174 |
> noticed such problems, but they surely existed for the gnome |
175 |
> team. Another exponent of the BMG tree were the infamous |
176 |
> love-sources which also caused inexplicable problems left and |
177 |
> right, which may ring a bell with much more devs. |
178 |
|
179 |
Again: if you can be sure of the overlay-status of packages, this |
180 |
might be less of a nightmare. |
181 |
|
182 |
> This is can be really demotivating, which is probably the worst |
183 |
> thing about it. |
184 |
|
185 |
That I agree on: if it's a motivation killer, it should be bound |
186 |
to a rock and dumped in a lake. I just think that it can be |
187 |
improved enough to not be such a dev nightmare. |
188 |
|
189 |
But then, I'm just a user and a server admin. |
190 |
|
191 |
Regards, |
192 |
Tobias |
193 |
-- |
194 |
You don't need eyes to see, you need vision. |
195 |
-- |
196 |
gentoo-dev@g.o mailing list |