1 |
On Sunday 08 November 2009 20:27:23 Mark Loeser wrote: |
2 |
> Patrick Lauer <patrick@g.o> said: |
3 |
> > If you feel you have too much time you could search on bugzilla for |
4 |
> > "patch" and start fixing those bugs. "Bump" is also a funny search. |
5 |
> |
6 |
> If you are just bumping random packages and applying patches when you |
7 |
> have no idea how the package works, we have a problem on our hands. |
8 |
> Please don't do that, you are only making more work for others. Perhaps |
9 |
> some of the things that are not maintained should go away. |
10 |
|
11 |
Like Perl? I like your plan already. |
12 |
|
13 |
> > Once you've done that for 3 months we can renegotiate cosmetic bugs and |
14 |
> > QA. |
15 |
> |
16 |
> Renegotiate QA? Do not commit anything to the tree that doesn't comply |
17 |
> to QA standards. Its really that simple. Don't be lazy and do things |
18 |
> the right way, or don't do them at all. |
19 |
|
20 |
That is an interesting opinion. But I doubt we're in a position to demand such |
21 |
things - I did point at a few minor issues in my last email, none of which you |
22 |
responded to in any way. So I guess you prefer things being unmaintained and |
23 |
rotting away so our users have the shittiest user experience possible instead |
24 |
of people trying to make things better. |
25 |
|
26 |
Now if you really were interested in QA you might want to do some things - |
27 |
like help bugwranglers. With the current amount of people available (not |
28 |
enough) and the influx of bugs (100-200 a day) we have a latency of worst case |
29 |
a few days until a bugwrangler looks at it. (Average case is much better). |
30 |
That is time the maintainers are not informed of a bug, which means we delay |
31 |
fixing it. Sucks from a QA point of view. |
32 |
|
33 |
Things like that would be good to have, but instead y'all spend lots of time |
34 |
discussing on mailinglists and not helping there. (Ok, we're all volunteers, |
35 |
we all have limited time, etc. etc.) So I find it a bit hard to care about |
36 |
your academic discussion of how to handle things when I haven't heard any idea |
37 |
of a solution to the problems I mentioned earlier. Head-in-the-sand is not |
38 |
going to work. |
39 |
|
40 |
And again, start at the basics. You can't build a tower without a solid |
41 |
foundation. "Does it compile" is more important than "does it respect as- |
42 |
needed" or "is indentation beautiful", so prioritize a bit and focus on |
43 |
getting the big problems resolved. |
44 |
|
45 |
Take care, |
46 |
|
47 |
Patrick |