I'll think about it. Right now, there's talk of rewriting some big things at work this summer, and that will have to be my main priority. I'll certainly be reviewing anything going into the Velocity codebase and participating in design discussions as i'm able, but i'm not sure i should commit much time beyond that and the occasional patch. If that alone counts for being a mentor, then i suppose i've no reason to say no. Committing even an hour a week for anything beyond that this summer feels risky given the possibilities in the non-OSS part of my job.
Or things may continue to be slow at work for a while and the rewrites pushed back to fall. I won't know for a few months which way they'll go. On 3/23/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
Any Velocity committers want to be a Google Summer of Code mentor? http://wiki.apache.org/general/SummerOfCodeMentor This article has much more detail. http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors As far as I can tell, main responsibility is to offer feedback/advice to a GSOC student about their summer project. It's recommended this be in public and on the dev list. So it's probably stuff you'd be doing anyway. (except you get a free T-shirt). It's recommended that every student have two mentors. So if the student application for the Velocity GSOC project gets accepted we'll need one more. (I've already signed up). It probably makes sense to sign up now rather than later. WILL -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
