Re: [gentoo-project] Should returning developers be handled before first timers?

[Lukasz Damentko]

I think recruiters should be free to pick any order of processing
recruitments they consider the best for themselves and the work they
are doing, the recruits and the project as a whole.

If there's a developer waiting in the queue who hasn't lost his
kung-fu, process him first so he can start contributing right away
rather than wait for you to get through trainees who take longer to
train and examine. If there are new devs lined up for understaffed
projects, process those first to help those projects recover. So on.

Any artificial rule that encourages recruiters to process people in
the same order they are reporting for duty I'd consider problematic
for the recruitment process and in the long term harmful for Gentoo.

Imagine you are obliged to process bugs in the packages in the same
order they are filed without being able to prioritize. So whatever big
fixes you need to make have to wait until you get through everything
filed prior to them delaying important fix for less important ones.
You are able to fix bugs in your ebuilds in any order you please, why
shouldn't recruiters be allowed the same?

My suggestion is: let recruiters decide on their own who should be
processed when on case by case basis. If they feel like bumping
someone and have good reasons to do so, they should be allowed to. If
they feel someone (regardless if it's a returning or a new dev) can
wait a bit longer until other more needed or skilled candidate is
processed. I trust recruiters and their judgement in this matter and I
wouldn't want to limit them with any policies in this matter.

Kind regards,

Łukasz Damentko