Re: [gentoo-dev] [RFC pre-GLEP] Gentoo Git Workflow

[Rich Freeman]

On Sat, Sep 9, 2017 at 3:47 AM, Michał Górny <mgorny@g.o> wrote:
> W dniu pią, 08.09.2017 o godzinie 17∶19 -0400, użytkownik Rich Freeman
> napisał:
>>
>> FYI - if anybody does want to make any comments on the proposed
>> devmanual changes to implement the new tags please comment at:
>>
>> https://github.com/gentoo/devmanual.gentoo.org/pull/72
>>
>
> The footers were discussed to death in this very thread. I've heard your
> opinions. However, as far as I'm concerned (and as I've pointed out) you
> did literally *nothing* to push your ideas forward for 2+ years.
>

So, you read something from my comment that I didn't write, and
ignored the stuff I did write.

In part this is my fault, because I used sarcasm out of frustration,
and that wasn't conducive to communication.

To be clear:

I expressed my opinions earlier in the thread as you pointed out.

I have no expectation that my particular suggestion would be the one
implemented.  If I had felt THAT strongly about the implementation of
this I'd have put it on the Council agenda or something, or at least
would have discussed it in privately with you on IRC or something.
Instead, once I noticed that infra had implemented some of the tag
processing I switched to the format it appeared to be using in my
commits.

I don't expect anybody to wait for 100% consensus before doing
anything around here.  I think I've made that clear in plenty of
posts.  For significant changes there should be discussion on the
lists, and then the implementer should go forward with what they see
as the best implementation based on the feedback received.  If
somebody has a problem with it then it should be their duty to
escalate it and deal with it, not make the maintainer jump through
extra hoops.  Certainly we shouldn't be taking every change to the
Council.

My concern was entirely with the attitude expressed in your comment in
that pull request.  If you had written "I don't think we need to go
back to gentoo-dev for this one because this specific proposal was
part of what was already posted there and none of the feedback really
suggests a major problem with this" it wouldn't have bothered me,
because as the person doing the work I think you should be afforded a
bit more discretion, and this was part of your proposal.

Sometimes posting on -dev elicits opinions we disagree with from
people who haven't done any of the work.  That should neither paralyze
us, nor cause us to scoff at their suggestions.  They're just words.

-- 
Rich