2009/3/10 Doug Goldstein <car...@gentoo.org>: > So really an effective solution might be for the recruiters/retirement staff > to change a user's shell with a script that spits out a message that says > something to the effect of: > > "You have been inactive for a while. Please contact recruiters to re-enable > your account. This was done as a security measure." > > Obviously a little friendlier would be better but everyone gets the gist. > That'll prevent them from logging into infra boxes and from being able to do > a commit. >
First of all there's been a lot of returning devs from whom I heard no word of complaint about the procedure. Bonsaikitten is one of them if this argument really requires an example. Now, if someone can't, has no time or is unwilling to redo his quiz... what makes you think this person will make a good developer later on? What will ensure quality of his contributions? After months or (in most cases) years of not being a developer it's very likely the person is out of touch with most current things in Gentoo and a conversation with a recruiter may be really good learning experience. I heard multiple times from recruiters that this is procedure is necessary for returning developers. If you ask them, I'm sure they will confirm those devs often need such refreshing and also are appreciating the time put into it from the recruiting team. Finally, what you are proposing (which I read as infra suspending their access automatically instead of me or other undertaker contacting the person first) far harsher and putting off than pretty soft (and many say too soft) procedures we have now. I personally would prefer to talk to such a person before suspending them anything happens. Please also remember that if we suspend access automatically and it's suspended for some time, it will require jumping through hoops upon returning just like one has to jump through them when being recruited back. I don't think QA will allow us to just give access back without prior checking if the person is current with everything a developer should know. And if they did allow that, I wouldn't consider this a good thing. Kind regards, Lukasz Damentko
