| 1 |
On Sun, Aug 11, 2013 at 2:22 PM, Alon Bar-Lev <alonbl@g.o> wrote: |
| 2 |
> On Mon, Aug 12, 2013 at 2:08 AM, Gilles Dartiguelongue <eva@g.o> wrote: |
| 3 |
>> Le dimanche 11 août 2013 à 22:09 +0300, Alon Bar-Lev a écrit : |
| 4 |
>>> On Sun, Aug 11, 2013 at 9:59 PM, Tom Wijsman <TomWij@g.o> wrote: |
| 5 |
>>> > On Sun, 11 Aug 2013 13:29:16 -0500 |
| 6 |
>>> > William Hubbs <williamh@g.o> wrote: |
| 7 |
>>> > |
| 8 |
>>> >> You may ask why I have offered patches instead of just fixing the |
| 9 |
>>> >> ebuild since I am a team member. That is because even team members |
| 10 |
>>> >> aren't allowed to touch bugs assigned to systemd@g.o [1], |
| 11 |
>>> > |
| 12 |
>>> > Well, if there are conflicts within a team then I can agree that no |
| 13 |
>>> > member is allowed to touch the bug without a collaborative decision; |
| 14 |
>>> > but from what it appears this bug has been handed in a way that one |
| 15 |
>>> > member appears to take all decisions and the other member has nothing |
| 16 |
>>> > to say. In particular, comments 5 and 11 change the state of the bug |
| 17 |
>>> > without giving any reasoning about why that change in state was made; |
| 18 |
>>> > this is unacceptable, it gives us no reason to believe the state change. |
| 19 |
>>> |
| 20 |
>>> This is expected, as it is similar to how systemd/gnome is managed :) |
| 21 |
>> |
| 22 |
>> I hope you are not talking about the Gentoo Gnome team as this would be |
| 23 |
>> very wrong. Every team member is heard on the team. |
| 24 |
> |
| 25 |
> I was talking about the designated upstreams. |
| 26 |
> |
| 27 |
> Regards, |
| 28 |
> Alon |
| 29 |
> |
| 30 |
|
| 31 |
In the future: don't. You've added nothing of substance to this |
| 32 |
thread, except three additional emails. |
Archives