The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

About me

See my wikipedia page, and my OLPC wikipage.

I'm a student and developer based out of Washington, DC. I've been working with Sugar for 2 years, and Linux in general for 6+ years. Prior to joining Sugar Labs, I worked with OLPC in the Support Gang to handle "donor relations", essentially replying to support tickets as well as gathering user feedback about the OLPC and Sugar experience.


Things I do at Sugar Labs

I help maintain a number of Sugar Labs web services along with Bernie Innocenti such as Gitorious, Infrastructure Team/Resources#Sunjammer, and Google Apps. I am also an administrator and bureaucrat at the Sugar Labs Wiki. I have founder access to the #sugar and #sugar-meeting channels, so if you need assistance with any of those services feel free to ask me.

I try to help out where I can with software development and design. I'm currently working on improving the user experience for the installation and deployment of Sugar on a Stick for both educators and students.


Contact

The fastest way to reach me is via IRC or XMPP. If your query is not urgent, email is preferred. Please see my contact page for more information, including addresses.

If you have a question about something on-wiki, feel free to leave me a note on my talk page.

Oversight Platform

Sugar Labs is currently facilitating a rich and diverse free software ecosystem, one which has the potential to revolutionize education for millions of children worldwide. In order to achieve this end-result, Sugar Labs needs to continue to engage new educators, content creators, and developers, as well as strengthen existing relationships with current contributors.

Plans for 2009 - 2010

  • Encourage increased community involvement to spur wider contributions
  • Establish open communication with a variety of downstream Linux distributions, so people running any recent version of one can quickly deploy Sugar in their environment
  • Focus on improving the reliability of Sugar on a Stick, as well as simplifying its installation
  • Off-load infrastructure to relevant third parties (FSF, MIT Media Labs) to ease maintenance and reduce potential downtime
  • Streamline the Sugar Labs web site so that people can get to the information they need (getting involved, getting sugar, etc) faster and more easily


Personal involvement

Over the past year, in addition to working on improving the end-user experience with Sugar on a Stick, I have been investigating new ways to lower the barrier to entry in Sugar development and content contribution. By leveraging low hanging fruit, one-hour projects, and quick to reward tasks, Sugar Labs can attract and keep a wider variety of contributors.

Through tools such as Canonical's Launchpad, GetSatisfaction, and other sites, Sugar can continue to expand its developer base. Granted, any new infrastructure or separation in procedures can create additional confusion on the user's part. Because of this, we need to consider carefully our choices so as to not have the opposite effect of what we are attempting to achieve.