| 1 |
On Sun, Jun 28, 2020 at 02:43:16PM +0300, Joonas Niilola wrote: |
| 2 |
> This is the yearly repeating question: How do you view the current |
| 3 |
> recruitment status in Gentoo? |
| 4 |
> |
| 5 |
> In your opinion... |
| 6 |
> - are we getting enough new devs on board? |
| 7 |
|
| 8 |
No, I do not believe we are seeing enough recruits come on board. Given |
| 9 |
the unique year that is 2020, we are obviously seeing an even lower |
| 10 |
amount of recruits. |
| 11 |
|
| 12 |
While I do not believe we are seeing enough recruits, I do not have a |
| 13 |
good reasoning as to why. Quizzes to much of a barrier? Easier to simply |
| 14 |
push items through p-m? Not even interest in Gentoo overall? |
| 15 |
|
| 16 |
Just a few thoughts... |
| 17 |
|
| 18 |
> - does the current recruitment system work? |
| 19 |
|
| 20 |
I believe it does and to attest to zlogene's comments, it really matters |
| 21 |
on the quality of the mentor and the recruit. There are, of course, a |
| 22 |
few individuals who say the quizzes are not an effective method and have |
| 23 |
"held out" because of this. Ultimately, I think spending the time to do |
| 24 |
it is worth while and regardless of an individuals background... you |
| 25 |
will learn something. Whether from the quiz directly or from your |
| 26 |
mentor and recruiter. |
| 27 |
|
| 28 |
> - can the current devbase handle "everything" (we have a lot of |
| 29 |
> low-manned projects)? If not, how could council aid in? |
| 30 |
|
| 31 |
Absolutely not! This is not to imply that our devs are not capable, but |
| 32 |
the amount of devs to ebuilds is not an effective ratio... this is |
| 33 |
magnified by the fact that we all (mostly) volunteer our time here. |
| 34 |
|
| 35 |
> - why do we have hundreds of contributors who'll never become devs? (is |
| 36 |
> there a problem in "marketing", or is the recruitment process too hard, |
| 37 |
> or something else?) |
| 38 |
|
| 39 |
See above for my thoughts. |
| 40 |
|
| 41 |
> - should council stay away from this topic, and leave every decision to |
| 42 |
> recruiters? (If I remember correctly, recruiters project were dropped to |
| 43 |
> 1 person because they had internal issues deciding how to handle future |
| 44 |
> recruitment). I'm also asking this because I have a suggestion to renew |
| 45 |
> recruitment process a bit. Should I post my suggestion to -core for |
| 46 |
> every dev to see, -project for everyone to see, or contact recruiters |
| 47 |
> who can silently approve/disapprove/modify my suggestion, without anyone |
| 48 |
> else knowing what I suggested? |
| 49 |
> |
| 50 |
|
| 51 |
I have had this same discussion with the recruiters and through the |
| 52 |
insight of zlogene I began to understand it more. Once a recruit is |
| 53 |
properly prepped and quizzes are done the process is pretty seamless... |
| 54 |
if the mentor and recruit fail in this phase then it will cause |
| 55 |
slowdowns. I have seen recruits submit their quizzes and within a week |
| 56 |
or two are onboarded by the recruiters. Further, I have seen quite the |
| 57 |
opposite. It works. |
| 58 |
|
| 59 |
-- |
| 60 |
Cheers, |
| 61 |
Aaron |
Archives