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] Is there any way I can help with pull requests?
Date: Sat, 13 Oct 2018 14:20:18 -0400	[thread overview]
Message-ID: <CAGfcS_m==Xu0xiZ7ZcPq3h5R2RDE4QwQbU6BEQchv39_tP2+BQ@mail.gmail.com> (raw)
In-Reply-To: <20181013135941.73da0a08@symphony.aura-online.co.uk>

On Sat, Oct 13, 2018 at 8:59 AM James Le Cuirot <chewi@gentoo.org> wrote:
>
> On Sat, 13 Oct 2018 13:28:02 +0200
> Ralph Seichter <gentoo@seichter.de> wrote:
>
> > Is there any way I could help the Gentoo team? Any vacancies that need
> > to be filled, or work that needs to be done?
>
> Following what I said above, we need more actual bona fide developers
> who have done the quizzes, understand the issues, can most important
> can take responsibility for their own contributions.
>
> There is the proxy maintainers project, where we can accept
> contributions with a little less scrutiny, but I personally feel that
> these contributors really should just become developers. It doesn't
> matter if you're only interested in one or two packages, any help is
> very welcome.
>

I have to imagine that while waiting to become a dev (or not), it
would still be useful if contributors would like to skim pull requests
and find ways to contribute to them.

If a dev has pointed out an issue with a pull request, consider
offering a patch to fix the issue.

If a pull request hasn't been looked at, consider looking at it and
offering patches to resolve any issues you see.

Sure, ultimately a dev still has to review/commit, but I imagine any
help with triage will just make their life easier, which means they'll
be able to get more commits into the actual tree.

And of course all the skills you would use to clean up pull requests
are for the most part the same ones you'll need to become a dev.
Also, reading a bunch of dev comments about quality issues with pull
requests will make you aware of the kinds of QA issues people
routinely run into, and you'll be less likely to create the same
problems.

In my experience the best way to get accepted as a committer in just
about any kind of FOSS project is to basically do just this.  Sooner
or later you'll be noticed and short-listed.  You'll also rub
shoulders with people who are likely to become mentors, and since
recruiter availability is limited they're going to be bound to focus
on applicants who are active already.

-- 
Rich


  reply	other threads:[~2018-10-13 18:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-13 11:28 [gentoo-dev] Is there any way I can help with pull requests? Ralph Seichter
2018-10-13 12:57 ` Thomas Deutschmann
2018-10-13 13:33   ` Ralph Seichter
2018-10-13 16:37   ` Ralph Seichter
2018-10-13 12:59 ` James Le Cuirot
2018-10-13 18:20   ` Rich Freeman [this message]
2018-10-13 18:32   ` Mikle Kolyada
2018-10-20  0:33     ` Michael Orlitzky
2018-10-20  8:05       ` Mikle Kolyada
2018-10-20 15:02         ` Michael Orlitzky
2018-10-13 13:11 ` Corentin “Nado” Pazdera
2018-10-14 18:17   ` Andreas K. Huettel
2018-10-15  8:30   ` Corentin “Nado” Pazdera
2018-10-13 13:31 ` Tomas Mozes
2018-10-14  9:27   ` Jonas Stein
2018-10-13 18:00 ` Michał Górny
2018-10-13 18:18   ` Ralph Seichter
2018-10-16 18:25     ` Virgil Dupras
2018-10-16 18:36       ` Bernd Waibel
2018-10-16 19:14       ` Ralph Seichter
2018-10-16 20:15         ` Rich Freeman

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_m==Xu0xiZ7ZcPq3h5R2RDE4QwQbU6BEQchv39_tP2+BQ@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