public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Cc: devmanual <devmanual@gentoo.org>
Subject: Re: [gentoo-dev] The demotivating process of contributing to devmanual
Date: Tue, 15 Oct 2019 14:10:18 -0700	[thread overview]
Message-ID: <CAAr7Pr-ty0xZWxnX2RDHsQ8Sk-g0YfO4G-PtpUq18LXJ8uciJg@mail.gmail.com> (raw)
In-Reply-To: <fc1c33a537b742ea0e79a5cb6551ddb2cce0381f.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2287 bytes --]

On Tue, Oct 15, 2019 at 1:59 PM Michał Górny <mgorny@gentoo.org> wrote:

> On Tue, 2019-10-15 at 16:47 -0400, Mike Gilbert wrote:
> > On Tue, Oct 15, 2019 at 4:35 PM Michał Górny <mgorny@gentoo.org> wrote:
> > > Hello, everyone.
> > >
> > > I'd like to highlight a major problem with devmanual.  For a basic
> > > policy & developer documentation thingie, it's quality is so-so at
> best.
> > > A lot of stuff is missing, lots of things are outdated or even
> > > incorrect.  Not many people are contributing, and those who try quickly
> > > resign.
> >
> > Maybe you should join the project? Especially if you are making major
> > contributions.
>
> Are you suggesting that I join the project and start committing without
> review, or disregarding review?  I have serious doubts on joining
> the project if I am repeatedly proven to be doing things wrong --
> whether the issues were serious or not.
>
> >
> > > Most of my pull requests were apparently approved, so they might be
> > > finally merged some day.
> >
> > I believe all devs have push access to that repo, so you could just
> > push the changes yourself if there are no reasonable objections.
>
> I never realized that.
>
> >
> > Minor mistakes happen, and can be corrected after the fact.
> >
>

One tactic here is to just timebound the reviews. 2 weeks between posting a
PR and getting a review is too long IMHO. Post a PR and say you will merge
it in 72 hours or something. If it's wrong, it can be fixed after the fact
as floppym notes.

If I'm at work and someone has sent me a patch and the patch is good but
there are some minor spelling / grammar fixes they can make I will
basically reply pointing out the problems (so they can fix them) but I also
tell them to merge once the fixes are applied. This means they don't need
to wait for me to "review" the spelling fixes. Obviously there is both
trust (in that I assume they did what I asked) and tooling (we have a tool
where I write comments like "you spelled foobare wrong here, should be
'foobar'" and they have to click "RESOLVE" on each item; you can't submit a
PR with 'unresolved' items open) so there is some pressure to "do the right
thing."

-A


>
> --
> Best regards,
> Michał Górny
>
>

[-- Attachment #2: Type: text/html, Size: 3029 bytes --]

  reply	other threads:[~2019-10-15 21:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 20:35 [gentoo-dev] The demotivating process of contributing to devmanual Michał Górny
2019-10-15 20:47 ` Mike Gilbert
2019-10-15 20:59   ` Michał Górny
2019-10-15 21:10     ` Alec Warner [this message]
2019-10-15 21:22     ` Mike Gilbert
2019-10-16 18:00     ` Ulrich Mueller
2019-10-15 21:20 ` Gokturk Yuksek
2019-10-22 20:33   ` Michał Górny
2019-10-24 16:44     ` Gokturk Yuksek
2019-10-24 17:05       ` Michał Górny
2019-10-18  4:37 ` desultory
2019-10-18  5:53   ` Matt Turner
2019-10-19  3:00     ` desultory

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=CAAr7Pr-ty0xZWxnX2RDHsQ8Sk-g0YfO4G-PtpUq18LXJ8uciJg@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=devmanual@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