Changes

My background is in engineering, so I'll often tackle things through technical tools and the people who want to work on them, and use software-based analogies and processes to get things done. I'm a student of education (and learning) as well as business operations - I'm by no means fluent in those two domains yet, but I'm trying hard to become equally comfortable working within and with them. Help and feedback is always incredibly appreciated.

My background is in engineering, so I'll often tackle things through technical tools and the people who want to work on them, and use software-based analogies and processes to get things done. I'm a student of education (and learning) as well as business operations - I'm by no means fluent in those two domains yet, but I'm trying hard to become equally comfortable working within and with them. Help and feedback is always incredibly appreciated.

== Current goals and projects ==

== Projects ==

I tend to set my goals in 6-month cycles mirroring the Sugar release schedule, so these are my goals for the the '''0.86 release cycle (March 1, 2009 - September 1, 2009).''' This list is super-flexible; stuff changes all the time, random cool ideas come up, and so this has deliberately been planned with lots of wiggle room. As things change, I (usually remember to) edit this page to reflect that.

I tend to set my goals in 6-month cycles mirroring the Sugar release schedule. This list is super-flexible; stuff changes all the time, random cool ideas come up, and so this has deliberately been planned with lots of wiggle room. As things change, I (usually remember to) edit this page to reflect that.

I was sidelined with RSI for much of this release cycle (and am still recovering), so priorities have been adjusted accordingly. For this release cycle, I have only one main project, but I'm interested in seeing many others completed (see below, and if you're interested, let me know how I can help you!)

I was sidelined with RSI for much of the previous release cycle (and am still recovering), so priorities have been adjusted accordingly. For this release cycle, I've put all my projects aside under the "potential" category until after the SLOBs election when I'll know how much time I have to work on them (or if I get elected to SLOBs, how I can work on them as part of that role).

* Google Summer of Code 2009 co-coordination with Jameson Quinn, focused on linking each student project with a Sugar deployment for testing and feedback (including starting a SoaS pilot near them, if needed - this is how I'd prefer to do it). By the end of summer, we should have a deployment success story for each of our successfully completed student projects.

'''Please feel free to steal a project if you like it, and let me know how I can help - I don't care who does this stuff so long as it gets done.'''

== Future goals and projects ==

== Future goals and projects ==