On Mon, Nov 2, 2015 at 1:24 AM, Patrick Lauer <patr...@gentoo.org> wrote:
>
> On 11/02/2015 02:56 AM, Rich Freeman wrote:
>> On Sun, Nov 1, 2015 at 8:22 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>>>  I know if I were still on rsync (or webrsync), I'd be raising hell about 
>>> the lack of
>>> changelogs well before now
>> Perhaps rather than raising hell you'd do better to raise money to
>> hire an infra team to fix the bug or something.
> Hire?
> I'm still willing to fix things, if I were given access. And I would
> presume that I'm not the only one.

Well, if somebody who has a good history of working with teams and is
generally well-liked wants to step up and volunteer for the job, they
could probably ping the council for endorsement.

>
> But since I don't have access, and can only affect things by motivating
> or upsetting people,

I think you'll find that the former works better than the latter with
volunteers.  Upsetting people generally tends to result in everybody
walking out in a huff and leaving users high and dry, so you're not
really doing anybody any favors with the attitude.

>>
>> I get the frustration, but we only have a few people who have the
>> necessary access to fix the problem.
> So fix that.

Proposals are welcome.

>
> But one of the conditions for tolerating the git migration was that we
> have no regressions.

I certainly never put that condition on it.  I think we were already
trying too hard to make things perfect vs accept the change and work
out some of the details later.  Changelogs being down for a few months
isn't a big deal IMO, especially since the data is all available in
git anyway.

If I didn't think git was ready to go I'd have voted to stop it, and
the Council probably could have done this.  Sometimes you just have to
embrace a change and deal with the fallout around minor issues like
this.  It isn't like Gentoo ground to a halt for a week.

> (And as a consequence, why doesn't it then get fixed in a reasonable time?)

I don't know, why don't you ask the responsible person's manager to
document this on their annual performance review?

> But at least now we get some good information what is broken how, and
> maybe someone can fix it. And then I won't have to be the stone in
> people's shoe anymore ;)

You don't have to be that now.

I get it, you don't like the state of affairs.  Join the club - I
think we're all in it already.  IMO part of the reason we're
struggling is that Gentoo was structured to work the way it does back
when we had at least 3x as much activity in some of the key projects.
The model doesn't scale down well, especially around key roles like
Infra where the design isn't open enough for others to effectively
contribute patches.

-- 
Rich

Reply via email to