I'd like to get mattjf onboard to work on crypto stuff for hardened and eventually lead the crypto subproject Reproducible: Always Steps to Reproduce: 1. 2. 3.
A few small things. The summary should read 'New dev: realname (nick)' or something to that effect.. This makes them easier to read. Also, we'll need his realname and where he's from, and he needs to be cc'd on this bug. Please read http://www.gentoo.org/proj/en/recruiters This will tell you what we need in recruiters bugs.
Correction to my url: http://www.gentoo.org/proj/en/devrel/recruiters
Pardon me, but is this mattjf the same mattjf who had joined gentoo about a year or so ago?
well over a year ago, about the same time i joined (a little after or before, can't remember) so it would have been almost 2 years now (right? )
is this an issue? can we get this ball rolling?
method, he needs to take the current ebuild quiz, and send it and his keys to recruiters. He also needs to wait out the 2 week eval period that all new devs need to do. Also, if he is a returning dev, then that needs to be looked at as well. I'll take this one once he is ready.
what needs to be looked at wrt him being a returning dev?
I seem to recall that previously when we tried this he became totally inactive and was eventually removed. Is my memory correct? What guarantee do we have that this will not occur again?
This did happen, but honestly > 90% of our devs are idle so until those are taken care of this is a non-issue. What guarantee do you have that anyone will not go inactive? This isn't a fair question. Further, he's joining for a specific purpose now, and will be mentored by me to lead a subproject.
What I'd like to know is why he disappeared. If he comes back, will he be active? method, what will you do in terms of that subproject if he comes back and disappears again? I think that put like this, theese questions are fair. We have had a couple of devs who have joined and then disappeared, and those devs were removed. Knowing that this person was removed for inactivity, I think it's only fair that we find out why he disappeared, and try to ensure that it doesn't happen again, or if it does, we know why. As for your comments about inactive devs, that's for another place, but not this bug...
The reason I disappeared was due to a couple reasons. The first reason is my joining as a gentoo developer prior to ever actually using gentoo. I am friends with mjc (through kernel development work and #kernelnewbies). After speaking to him one evening, he suggested I become a gentoo developer. I spoke to seemant I believe, and after a few short conversations, I was a developer. I quickly installed gentoo on various machines. Learning to use gentoo and at the same time learning to be a gentoo developer normally would not be a very daunting task, if it were not for the second reason. At various times during the year, work get's very busy. I don't know how much Method has told you, but I am a cryptographer for the US Government, specifically the National Institute of Standards and Technology. I usually have plenty of free time to participate in outside activities, but sometimes during the year, things get very busy. If I had already been a gentoo user, or had already known "how to be a developer", and if the Hardened project had already been started at the time of my joining, it wouldn't have been a big deal. I would have been able to handle both. But, learning both things as well as work proved to be too big of a task, and obviously I could not give up my job. My profession more than qualifies me to handle running a crypto project. I hope my past does not have an impact on your decision. As a side note, Method and pebenito live close by me, and I see them on the weekends. If I disappear, they will be able to find me :). -Matt
Method what's going on with this one? We have no quiz or keys from him as of yet. I want to get him set up and taken care of before I leave in 12 days. so let's get his quiz etc going....
matt has been very busy with his job, people breaking hashes apparently causes all sorts of commotion at NIST, I'll let you know when he's ready to start.
I'm going to close this for now till he's ready. Note: this is not a rejection, but if he's not ready right now, there's no reason to leave the bug open. When he's ready, and is going to stay active and be responsive, then we can take him through the process.
