From: Mike Gilbert <floppym@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 16:47:33 -0400 [thread overview]
Message-ID: <CAJ0EP40hW2knr+CdSbc2sLQTd6Dz7J_YYiAJR0RFROr0gJqQSg@mail.gmail.com> (raw)
In-Reply-To: <7db69bdd30aeaf350f9c70c28abf9d890656d55c.camel@gentoo.org>
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.
> 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.
Minor mistakes happen, and can be corrected after the fact.
next prev parent reply other threads:[~2019-10-15 20:47 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 [this message]
2019-10-15 20:59 ` Michał Górny
2019-10-15 21:10 ` Alec Warner
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=CAJ0EP40hW2knr+CdSbc2sLQTd6Dz7J_YYiAJR0RFROr0gJqQSg@mail.gmail.com \
--to=floppym@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