1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA512 |
3 |
|
4 |
Mart Raudsepp: |
5 |
> On T, 2014-02-25 at 19:10 +0000, hasufell wrote: |
6 |
>> Mart Raudsepp: |
7 |
>>> |
8 |
>>> We wrote this policy in the first place so that everyone can |
9 |
>>> understand why we do things this way and we do not want anyone |
10 |
>>> to mess with it without due explanation and justifications |
11 |
>>> because in the end, we will be the ones (with other gtk based |
12 |
>>> DE) maintaining this mess in tree. |
13 |
>>> |
14 |
>> |
15 |
>> This is just a gnome team policy and not tree policy. A LOT of |
16 |
>> people do things completely different and I did not get much |
17 |
>> support from the gnome team to stop the mess. |
18 |
> |
19 |
> We do not have such an authority, while QA team believes it does, |
20 |
> and I applaud such initiatives of consistency, however I severely |
21 |
> question the process in which this has been undertaken. Driving the |
22 |
> status quo of approaching this to complete opposite in a couple of |
23 |
> weeks without due process to be seen which I would expect from such |
24 |
> a longstanding issue. |
25 |
> |
26 |
>> See https://bugs.gentoo.org/show_bug.cgi?id=420493 |
27 |
>> |
28 |
>> I then complained to QA, because most people started to close |
29 |
>> bugs as RESOLVED WONTFIX without good reason (including QA |
30 |
>> members). |
31 |
>> |
32 |
>> I don't think this can be solved without a more definite answer |
33 |
>> than "we recommend you do it this way", even if you rework your |
34 |
>> team policy. |
35 |
> |
36 |
> We are suggesting to be part of a due process to come up with a |
37 |
> properly discussed, agreed and with all use cases thought about and |
38 |
> considered properly. At this point the conclusion of such a process |
39 |
> would then end up as a QA or Council policy, that the maintainers |
40 |
> of relevant things have been a part of forming as common courtesy |
41 |
> and common sense (the maintainers should know what's going on and |
42 |
> have good input to all sides of the story), and that we would then |
43 |
> supposedly also follow without much of complaining. |
44 |
> |
45 |
> The previous mailing list discussions I found died down after they |
46 |
> received replies from the Gnome team. For the recent discussions, |
47 |
> we have been busy with actually maintaining one of the biggest |
48 |
> desktop environments according to what we can in our limited time, |
49 |
> and have not yet been able to fully digest and summarize all the |
50 |
> issues that have come up in the latest (and previous) rounds of |
51 |
> discussion. On the lack of such volunteering from someone, such as |
52 |
> someone from the Gnome team who are otherwise preoccupied, I would |
53 |
> expected some summarizing and bringing the discussion back on track |
54 |
> by the QA team at that point, not run off to a vote that |
55 |
> contradicts 10+ years of practice and leaves many many things |
56 |
> unanswered, possibly changing the whole decision again soon after |
57 |
> to address concerns as we have the time to (re)bring them up and |
58 |
> insist on getting an answer, as you have tried the past year. |
59 |
> |
60 |
> |
61 |
|
62 |
Ok, I'm fine with that approach, so I revoke my agenda item. Ofc it's |
63 |
not my say if it still ends up there. |
64 |
-----BEGIN PGP SIGNATURE----- |
65 |
|
66 |
iQEcBAEBCgAGBQJTDPbUAAoJEFpvPKfnPDWzcnYH/iHTrYFWSASug/vjXTyLYQ9o |
67 |
TlRfAsU9AXa5qMFi/MSOU3mKBn+cnehm46DQ5MPnzW19/CfMA66uOEFdA9G3X6NF |
68 |
3lTE9EHVbboTddrEvvSMG5lM5oF1Jt7/DDLCwu45mXvtjkYJNxy2wwP/s0ZcXi8z |
69 |
nL+5htut41VCsceo9wOfVDBRtrpRMH2dfwhQv0zrNrnoz3rr1zgTYOuVzAJhntvW |
70 |
CscbqtkZ8rSkjQWD9zI3HuTUjvaHJlAQIe/06EaT6oMYIVEUebPhRem5ic4P0H5F |
71 |
lzBwBMIB2qhlA4hrHogGgy8P6Jvycr8Y48zYNz4g9L3HmoApafgfgKESIOnuV9A= |
72 |
=EJad |
73 |
-----END PGP SIGNATURE----- |