Marketing of Agaric: In open source free software, code rules

Reviewing patches and contributing bugfixes to Drupal core helps Agaric in three ways:

1. It helps Drupal, the software we build our websites with, get better.
2. It helps us become familiar with the code on a deep level, easily.
3. It is a key thing potential clients who 'get' open source will look for.

This note is just to let Kathryn and Veronica know this sort of direct giving back to the community should be built into our schedules.

And to let Gus (and Dan) know the easiest way to leapfrog past me as Agaric's best-known Drupal developer ;-)

(I have done almost none of this in part because dev environments on my computer run inexplicably slowly.)

Take for instance this bug fix that needs review,

http://drupal.org/node/201536

"General patch reviewing tips" on this page has the info needed to test:
http://drupal.org/patch/spotlight

Resolution