public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC pre-GLEP] Gentoo Git Workflow
Date: Sat, 9 Sep 2017 05:29:52 -0400	[thread overview]
Message-ID: <CAGfcS_nrFQbM9LxBvApuWRsfbxTTmFd5Z=r6SqK4TH9XHb-BNw@mail.gmail.com> (raw)
In-Reply-To: <1504943241.15912.8.camel@gentoo.org>

On Sat, Sep 9, 2017 at 3:47 AM, Michał Górny <mgorny@gentoo.org> 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


  reply	other threads:[~2017-09-09  9:29 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25  8:05 [gentoo-dev] [RFC pre-GLEP] Gentoo Git Workflow Michał Górny
2017-07-25  8:23 ` Nicolas Bock
2017-07-25  8:49 ` Dirkjan Ochtman
2017-07-25 10:59 ` Tobias Klausmann
2017-07-25 11:49   ` Michał Górny
2017-07-25 11:25 ` Michael Orlitzky
2017-07-25 11:52   ` Michał Górny
2017-07-25 12:26     ` Michael Orlitzky
2017-07-25 13:23       ` Michał Górny
2017-07-25 16:12         ` Michael Orlitzky
2017-07-25 20:29           ` Mike Gilbert
2017-07-25 20:31             ` Michael Orlitzky
2017-07-25 20:55               ` Michał Górny
2017-07-25 22:26             ` Rich Freeman
2017-07-25 22:30               ` Michał Górny
2017-07-25 22:46                 ` Rich Freeman
2017-07-25 22:50                   ` Michał Górny
2017-07-25 13:26     ` Rich Freeman
2017-07-25 13:48       ` Michał Górny
2017-07-26  9:21         ` Ulrich Mueller
2017-07-26 17:04           ` Kristian Fiskerstrand
2017-07-26 17:20             ` Rich Freeman
2017-07-26 17:32               ` Kristian Fiskerstrand
2017-07-27  9:54               ` Kristian Fiskerstrand
2017-07-26 17:00   ` Kristian Fiskerstrand
2017-07-25 11:50 ` Jonas Stein
2017-07-25 12:28 ` [gentoo-dev] " Michael Palimaka
2017-07-25 13:36   ` Michał Górny
2017-07-26 17:05   ` Kristian Fiskerstrand
2017-07-26 22:20     ` Sam Jorna
2017-07-27  6:08     ` Daniel Campbell
2017-07-27 13:48     ` Michał Górny
2017-07-25 12:54 ` [gentoo-dev] " Joshua Kinard
2017-07-25 13:43   ` Michał Górny
2017-07-26 13:41 ` Brian Evans
2017-07-26 17:17 ` Kristian Fiskerstrand
2017-07-27 13:52   ` Michał Górny
2017-07-27 13:54     ` Kristian Fiskerstrand
2017-07-27 13:58       ` Michał Górny
2017-07-27 14:08         ` Kristian Fiskerstrand
2017-07-27 14:11           ` Michał Górny
2017-07-27 14:25             ` Kristian Fiskerstrand
2017-07-27 22:00 ` [gentoo-dev] " Duncan
2017-07-27 22:37 ` Duncan
2017-07-27 23:12 ` Duncan
2017-07-27 23:38 ` Duncan
2017-07-28  0:15 ` Duncan
2017-07-28 10:38 ` [gentoo-dev] " Andreas K. Huettel
2017-09-08 21:19 ` Rich Freeman
2017-09-09  0:00   ` Kristian Fiskerstrand
2017-09-09  7:47   ` Michał Górny
2017-09-09  9:29     ` Rich Freeman [this message]
2017-09-10  7:39     ` Daniel Campbell
2017-09-10  9:34       ` Michał Górny
2017-09-10 22:13         ` Daniel Campbell
2017-09-11  3:09           ` Dean Stephens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGfcS_nrFQbM9LxBvApuWRsfbxTTmFd5Z=r6SqK4TH9XHb-BNw@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox