1 |
On Sunday 26 February 2006 16:58, Ciaran McCreesh wrote: |
2 |
> On Sun, 26 Feb 2006 17:22:17 -0500 Mark Loeser <halcy0n@g.o> |
3 |
> |
4 |
> wrote: |
5 |
> | Yes, Gentoo is supposed to be fun, but we also have a responsibility |
6 |
> | to our users to ensure we are providing them with the best possible |
7 |
> | distro we can. |
8 |
> |
9 |
> What, you mean the tree isn't someone's personal playground? |
10 |
|
11 |
I do not know what he did refer to, however the following quote from |
12 |
ChrisWhite's blog does come to mind: |
13 |
[snip] |
14 |
"Well, I was told by ciaranm to "stop treating the tree like your toy" or |
15 |
something to that effect. Now, I'm going to respond to this with "Yes, it is |
16 |
my toy". Before you all go phsyco and what not, let's take a look at what |
17 |
Gentoo really is." |
18 |
[/snip] |
19 |
|
20 |
Following this is a rather sad rationalization as to why it is a toy. |
21 |
|
22 |
http://www.securesystem.info/tiki-view_blog_post.php?blogId=3&postId=111 |
23 |
|
24 |
> |
25 |
> | * The QA team may also offer to fix obvious typos and similar minor |
26 |
> | issues, and silence from the package maintainers can be taken as |
27 |
> | agreement in such situations. |
28 |
> |
29 |
> Should probably clarify that one. It's in there because there are some |
30 |
> situations where we find obvious typos (e.g. 'souce' instead of |
31 |
> 'source' in DEPEND) and file a bug to alert the maintainer. If the |
32 |
> maintainer fixes it within a few days, there's no problem, but if not |
33 |
> there's no point in letting the bug sit there -- someone from QA should |
34 |
> be able to fix it themselves. |
35 |
> |
36 |
> Equally, we don't want to just fix stuff without telling people that |
37 |
> they made a mistake, because then they're more likely to do it again. |
38 |
> |
39 |
> | * The QA team will maintain a list of current "QA Standards". The |
40 |
> | list is not meant by any means to be a comprehensive document, but |
41 |
> | rather a dynamic document that will be updated as new problems are |
42 |
> | discovered. |
43 |
> |
44 |
> Hrm, do we want to include the thing about the QA standards providing |
45 |
> rationale and explanations rather than hard rules here? |