public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Campbell <zlg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Recruiting process (Re: [gentoo-dev] base-system needs developers who care)
Date: Thu, 25 Aug 2016 02:59:28 -0700	[thread overview]
Message-ID: <fdd79f49-f0b1-206b-3e9d-12525e732196@gentoo.org> (raw)
In-Reply-To: <CAGDaZ_ockWF+VX00_UQpqLUoCaQveZ1VGWDz6s32eAsHjuU-nA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1835 bytes --]

On 08/24/2016 08:24 PM, Raymond Jennings wrote:
> This...kinda touches on a side issue.  I've been a bit waylaid by RL
> issues during my quest to become a developer myself, and both of my
> prospective mentors had to step aside for the same reason before the
> process could finish.
> 
> I'm a little slow on the quizzes and some recent changes in gentoo
> invalidated some of my answers, so part of it is my fault for falling
> behind.
> 
> But I was kinda wondering, is there anything that can be done to beef up
> the manpower?  Is there any need to?

(snipped HTML quote; stick to plaintext please)

The situation you described isn't that uncommon in Gentoo. We're a bit
smaller than we used to be, but I've also noticed that more people are
being brought on than they were when I first started using Gentoo in
2012 and even near the time I was accepted as a developer.

Being a recruiter and/or mentor is no small task. You need to be
extremely comfortable talking about the nitty gritty of ebuilds and a
strong grasp of the PMS would be even better. Absorbing that information
takes time, and I wonder if despite the new blood we've been getting,
some knowledge isn't being passed down as well as it maybe should be.

Given that so much needs to be learned and a lot of trust goes into
developers, it's no surprise that we tend to take our time accepting
people. That said, I chalk it up to a manpower problem. As far as I know
the recruiting and proxy-maint teams are dedicated, but small. They do
an awesome job (that I am not cut out for) so they deserve a lot of
respect. But it does indeed seem that scheduling and workloads are not
in sync.
-- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2016-08-25  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25  3:24 Recruiting process (Re: [gentoo-dev] base-system needs developers who care) Raymond Jennings
2016-08-25  9:59 ` Daniel Campbell [this message]
2016-08-25 11:05   ` Kristian Fiskerstrand

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=fdd79f49-f0b1-206b-3e9d-12525e732196@gentoo.org \
    --to=zlg@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