1 |
On 23 April 2013 01:13, Michał Górny <mgorny@g.o> wrote: |
2 |
|
3 |
> On Mon, 22 Apr 2013 19:43:22 +0800 |
4 |
> Ben de Groot <yngwin@g.o> wrote: |
5 |
> |
6 |
> > On 21 April 2013 22:38, Chí-Thanh Christopher Nguyễn < |
7 |
> chithanh@g.o>wrote: |
8 |
> > |
9 |
> > > Denis Dupeyron schrieb: |
10 |
> > > > I'm hoping this kind of immature and abrasive behaviours will not |
11 |
> > > > propagate (notice the plural here). Yes, when you see a package being |
12 |
> > > > actively maintained by somebody else you should absolutely not touch |
13 |
> > > > it without talking to that person or team first. |
14 |
> > > |
15 |
> > > I fail to see any wrong behavior here. A bug report was created and a |
16 |
> > > review |
17 |
> > > of the changes was requested. The first reaction came after several |
18 |
> weeks |
19 |
> > > after the bug filing, and the first objection almost two months after |
20 |
> the |
21 |
> > > change was applied. |
22 |
> > > https://bugs.gentoo.org/show_bug.cgi?id=455074 |
23 |
> > > |
24 |
> > |
25 |
> > You are missing an important part of the story. |
26 |
> > See https://bugs.gentoo.org/show_bug.cgi?id=455070 where we discuss |
27 |
> > the same issue for freetype. (Yes I should have been explicit for |
28 |
> fontconfig |
29 |
> > too, my bad.) |
30 |
> > |
31 |
> > I initially reacted within hours, saying that his proposal was in my eyes |
32 |
> > not ready yet. I assumed I was clear enough in my refusal, but |
33 |
> > apparently Michał didn't understand it that way. He then contacted |
34 |
> > the herd a few weeks later, when I was on holiday, and got Luca's |
35 |
> permission |
36 |
> > to commit, not taking into account he hadn't touched those packages in |
37 |
> > many years. |
38 |
> |
39 |
> Just to be clear -- I misunderstood you indeed. |
40 |
|
41 |
|
42 |
I know, and it's water under the bridge. We're people and we make mistakes |
43 |
sometimes. Let's move on. |
44 |
|
45 |
|
46 |
> I thought you mean that |
47 |
> you would agree if the idea is discussed and the discussion results in |
48 |
> a general agreement on proceeding with the solution. |
49 |
|
50 |
|
51 |
That and ample testing. I think it has been going all a bit too quick, with |
52 |
the eclass(es) in flux, and so on. I'm still not convinced it's mature |
53 |
enough |
54 |
at this point, which is why I believe this should still be masked. |
55 |
|
56 |
As to the discussion, I see only a few people speaking up, but obviously |
57 |
you cannot be blamed for the silent majority. |
58 |
|
59 |
But it's starting to look more and more like I'm the only one objecting |
60 |
at this point. So maybe I should stop being cautious (or even cranky) |
61 |
and let you guys go ahead and do your work. I do need someone to |
62 |
co-maintain freetype and fontconfig then, as I am personally still not |
63 |
happy with these changes and the maintenance burden they create. |
64 |
|
65 |
|
66 |
> > After I found out, I was a bit pissed off about it, but I was too busy |
67 |
> with |
68 |
> > work to deal with it (and thought it wise to cool down a bit before |
69 |
> taking |
70 |
> > action). I then saw bug reports about the freetype multilib ebuild |
71 |
> revision |
72 |
> > flooding in, and was satisfied after it got masked. |
73 |
> |
74 |
> Those bugs weren't relevant to the final version of the ebuild which |
75 |
> you have masked. The only actual bug left open was the one which I |
76 |
> forgot to close after fixing it instantly after it was opened. |
77 |
> |
78 |
> So please don't say that I don't take responsibility for my changes. |
79 |
|
80 |
|
81 |
I'm not saying that at all. You respond quickly. I can only commend you |
82 |
on that. |
83 |
|
84 |
But I do have doubts about long term maintainance. I know you are |
85 |
more than willing to do your part, but it's simply beyond any one |
86 |
person to (co-)maintain half the tree. |
87 |
|
88 |
-- |
89 |
Cheers, |
90 |
|
91 |
Ben | yngwin |
92 |
Gentoo developer |
93 |
Gentoo Qt project lead, Gentoo Wiki admin |