1 |
On Tue, 2006-08-01 at 16:05 +0200, Kevin F. Quinn wrote: |
2 |
> > 2. [...] Therefore I do not believe that QA for a tree that is as |
3 |
> > extensive as Sunrise done by a few 'official' developers amounts to |
4 |
> > much real world quality. |
5 |
> |
6 |
> I would expect that over time, the Sunrise developers will learn more |
7 |
> and more how to write quality ebuilds (as hopefully do we all). Since |
8 |
> they'll be working with a diverse set of stuff, they could become better |
9 |
> than most devs at this. Remember that since they have custody of the |
10 |
> stuff in the Sunrise overlay, they will be hit with whatever issues |
11 |
> arise from their work. |
12 |
|
13 |
I expect the developers involved to be able to write quality ebuilds |
14 |
right now, otherwise they shouldn't be developers. However, I don't |
15 |
expect them to write quality ebuilds for everything in the tree, there |
16 |
are a lot of packages that need specific knowledge to make a correct |
17 |
ebuild. That is why we got the herd system, that is why we have a couple |
18 |
of hundred ebuilders who all have their own specific parts of the tree |
19 |
to take care of. |
20 |
|
21 |
> What it does give you is a track record you can look through - in much |
22 |
> the same way you might have watched what someone did on bugzilla or |
23 |
> IRC. Indeed I'd suggest that the history in Sunrise SVN would be |
24 |
> useful to indicate whether someone is learning how to write ebuilds |
25 |
> properly, or just continues to make the same errors. |
26 |
|
27 |
Ebuilding is such a small part of the job I wouldn't seriously take it |
28 |
into account, to me much more important is the bughandling skills of a |
29 |
potential developer. Is he/she able to distill the right information |
30 |
from a report, ask for the right additional info and come to a practical |
31 |
and neat solution ? |
32 |
|
33 |
- Marinus |
34 |
|
35 |
-- |
36 |
gentoo-dev@g.o mailing list |