1 |
Daniel Drake wrote: |
2 |
|
3 |
> We have a large expense on both sides when adding a developer to the |
4 |
> project. I personally have lost developer candidates, undoubtedly more |
5 |
> technically experienced than myself, who simply did not have the time |
6 |
> to go through a month-long recruitment process which involved studying |
7 |
> various documents not even relevant to the small area they would be |
8 |
> contributing to. On the other side, it's a fair expense to add a |
9 |
> developer to the project due to all of the |
10 |
> quizzing/assessing/account-creating/access-elevation/... |
11 |
|
12 |
Technical ability isn't the only requirement for gentoo devs. They also |
13 |
must be motivated individuals and these high barriers you are talking |
14 |
about test this quality of the candidates. |
15 |
If they quit just because recruitment process is long, what makes you |
16 |
think they will stay active long enough to actually worth adding them to |
17 |
dev corpus? |
18 |
|
19 |
> |
20 |
> Additionally, a significant percentage of developers who have joined |
21 |
> recently have gone AWOL after a few months. That hurts us, given the |
22 |
> expense we went through recruiting and adding them, and the time |
23 |
> needed to reverse that and retire them. |
24 |
|
25 |
Yes, it is hard to find the right people. Yes, a big percentage of |
26 |
recruiting team's time will be lost on useless additions/removals. But |
27 |
the only solution is scaling the recruiting team to gentoo needs. |
28 |
IMO recruiting team is too small to cope with the current size of the |
29 |
project. |