public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: repo/gentoo.git, or how committing is challenging
Date: Tue, 22 Dec 2015 14:31:55 +0100	[thread overview]
Message-ID: <567950CB.4070307@gentoo.org> (raw)
In-Reply-To: <CAGfcS_np=GPmfiHO=F7PCQa9O_AOAUXjRhSVwQcN6SV4uNj0PA@mail.gmail.com>



On 12/22/2015 02:14 PM, Rich Freeman wrote:
> On Tue, Dec 22, 2015 at 7:53 AM, Patrick Lauer <patrick@gentoo.org> wrote:
>> I'd replace gkeys-gen with a ~10-line shell script ... if I had some
>> motivation to dig through some old experiments of mine where I managed
>> to set all parameters for pgp from CLI. Which is all that gkeys-gen
>> would do!
> Sounds great.
>
>> I guess we fundamentally disagree - if you do shoddy work, it is shoddy.
>> I won't praise you for it.
> Nobody is looking for your praise.
>
>> That's my time, spent to work around deficiencies I shouldn't even see -
>> if other people had done their job. And that's just frustrating if it
>> happens again and again, and instead of doing something interesting I
>> spend most of my time just being janitor and cleaning up stuff.
> I hope you're not the one looking for praise.  I can't imagine that
> your pep talk has done a great deal to motivate people to spend time
> improving the Gentoo Keys experience.
Well, it's abandoned anyway (bugs open for >1 year means there's
literally no one working on it, for a year)
Like the git 'migration' it's half-finished work with little thought
about workflow or user experience, "Change is Progress"

If we didn't have it at all I would not have had to file bugs, spend
time being very confused, etc. So all in all it has negative value in
its current state. And it wastes the time of everyone who tries to use
it, which is a few man-weeks of work ground away with inefficiency and
carelessness. Imagine how much progress we could have had if someone had
spent one afternoon on writing coherent docs!

>
> Do you want to see this fixed?
> Are you willing to do the fixing yourself?
I don't have infinite time, and wasting a day documenting things that
should have been documented a year ago is not a good way of spending time.

>
> If the answer to the first question is yes, and the second is no, then
> you've just volunteered for the job of either community motivator, or
> frustrated user.  The goal then is to make people care more about
> going out of their way to fix things than going out of their way to
> find ways to make you even more frustrated.  Which do you think is
> going to be more emotionally satisfying to those who read this thread?
>
Things working.

So, the trick is not to have user-visible breakage.

Now you know the great trick too and can apply it to your daily life.


  reply	other threads:[~2015-12-22 13:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 17:36 [gentoo-dev] repo/gentoo.git, or how committing is challenging Patrick Lauer
2015-12-13 17:38 ` Patrick Lauer
2015-12-13 18:50   ` Andrew Savchenko
2015-12-13 19:05     ` Patrick Lauer
2015-12-13 19:20 ` Andrew Savchenko
2015-12-13 21:30   ` Mike Gilbert
2015-12-13 21:53     ` Andrew Savchenko
2015-12-14  3:00   ` Brian Dolbec
2015-12-14  6:23     ` Daniel Campbell
2015-12-14 11:12     ` Patrick Lauer
2015-12-14 17:52       ` Mike Gilbert
2015-12-15  0:31       ` Peter Stuge
2015-12-21  3:21     ` [gentoo-dev] " Ryan Hill
2015-12-21 18:59       ` Peter Stuge
2015-12-22  0:45         ` Rich Freeman
2015-12-22  9:41       ` Patrick Lauer
2015-12-22 12:08         ` Rich Freeman
2015-12-22 12:53           ` Patrick Lauer
2015-12-22 13:14             ` Rich Freeman
2015-12-22 13:31               ` Patrick Lauer [this message]
2015-12-22 14:04                 ` Rich Freeman
2015-12-22 18:21                   ` Patrick Lauer
2015-12-22 23:55             ` Peter Stuge

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=567950CB.4070307@gentoo.org \
    --to=patrick@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