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] Re: repo/gentoo.git, or how committing is challenging
Date: Tue, 22 Dec 2015 07:08:43 -0500	[thread overview]
Message-ID: <CAGfcS_nRBGG3-fohU2KhoesLX9F_ERCuWzSGacWeYUjBb-1uZw@mail.gmail.com> (raw)
In-Reply-To: <56791ACB.3000903@gentoo.org>

On Tue, Dec 22, 2015 at 4:41 AM, Patrick Lauer <patrick@gentoo.org> wrote:
> Wiki says:
>
> "In this guide we are going to show you how to create a GLEP 63
> <https://wiki.gentoo.org/wiki/GLEP:63> based OpenPGP Key using
> app-crypt/gkeys-gen
> <https://packages.gentoo.org/packages/app-crypt/gkeys-gen> tool which is
> the official way of managing OpenPGP keys in the Gentoo Infrastructure."
>
> So either the documentation is wrong, or we're supposed to use a broken
> tool.

The GLEP is certainly official.  I think the tool was intended to be,
but the whole point of a "standard GLEP" is that you have to meet the
standard, not use a particular implementation.  gkeys isn't even the
reference implementation.

>
> Or just point people at a random email, because that's about as good as
> documentation.

Thank you for writing up a guide/outline.

You appear to hate mediawiki, but you do realize that you could
probably copy/paste that email into the box and call it half-done,
right?  Somebody else can always come along and improve it, and that
is kind of the whole point of a wiki, and of FOSS in general.

>
> Please, stop wasting people's time, if you write code or documentation
> write it once properly, don't release untested things and claim they are
> an official tool, and don't ignore complaints (because they mean, as a
> first approximation, that you screwed up and need to fix stuff)
>

Gentoo devs and volunteers are more than welcome to ignore complaints.
I'll take half-implemented code over no code any day of the week.
Maybe somebody isn't good at writing documentation, and we benefit
from getting their contributions all the same which somebody can later
follow-up on (perhaps somebody who is better at writing documentation
than code).  You're going to make more progress with evolutionary
steps.

BTW, bugs aren't complaints, and I don't really consider "complaints"
nearly as useful.  If you want to point out an error by all means do
so.  You can do it without implying that somebody somehow owed you
something better. They don't.

-- 
Rich


  reply	other threads:[~2015-12-22 12:08 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 [this message]
2015-12-22 12:53           ` Patrick Lauer
2015-12-22 13:14             ` Rich Freeman
2015-12-22 13:31               ` Patrick Lauer
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=CAGfcS_nRBGG3-fohU2KhoesLX9F_ERCuWzSGacWeYUjBb-1uZw@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