public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Question for 2020 council candidates: Dev recruitment status
Date: Sun, 28 Jun 2020 17:52:20 +0200	[thread overview]
Message-ID: <4d302171b58e2e0c5c62473def23c39a85209e12.camel@gentoo.org> (raw)
In-Reply-To: <32ea0394-4fec-09c3-45e0-74a2396e1403@gentoo.org>

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

On Sun, 2020-06-28 at 14:43 +0300, Joonas Niilola wrote:
> This is the yearly repeating question: How do you view the current
> recruitment status in Gentoo?

I know I'm not being asked but I'd like to leave a short note
to the context.

> In your opinion...
>  - are we getting enough new devs on board?
>  - does the current recruitment system work?
>  - can the current devbase handle "everything" (we have a lot of
> low-manned projects)? If not, how could council aid in?
>  - why do we have hundreds of contributors who'll never become devs? (is
> there a problem in "marketing", or is the recruitment process too hard,
> or something else?)
>  - should council stay away from this topic, and leave every decision to
> recruiters?

I would suggest we leave Council out of recruitment problem, and let
the Triumvirate deal with it.

> (If I remember correctly, recruiters project were dropped to
> 1 person because they had internal issues deciding how to handle future
> recruitment).

For the future, please don't spread rumors like that without confirming
them first.  Some people may assume this to be true and never look into
the next mail correcting this.

>  - 2020 we've had 0, and publically 1 candidate can be found.

Please remember that in middle of covid-19 people have higher priorities
than looking into joining open source projects.  In other words, 'it's
not just us'.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  parent reply	other threads:[~2020-06-28 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 11:43 [gentoo-project] Question for 2020 council candidates: Dev recruitment status Joonas Niilola
2020-06-28 13:11 ` Mikle Kolyada
2020-06-28 13:26   ` Joonas Niilola
2020-06-28 13:45   ` Joonas Niilola
2020-06-28 15:52 ` Michał Górny [this message]
2020-06-28 20:30 ` Aaron Bauman
2020-07-01  7:38   ` Benda Xu
2020-06-28 23:12 ` Andreas K. Huettel

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=4d302171b58e2e0c5c62473def23c39a85209e12.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-project@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