Introduction, doc team request

Hi all,

I'm writing to request membership in the documentation team, and to be assigned the document maintainer role.

I wrote a few tutorials for Drupal as an Americorps VISTA volunteer back around 4.6, when Zack Rosen asked me to contribute some of it back to the Drupal project. I've worked on several Drupal-related projects since then, including a stint as project manager for the Chicago Technology Cooperative working as a consultant. I'm currently the Director of Programs for Grassroots.org.

Grassroots.org is working on a project to offer hosted, configured, and supported Drupal installs for any nonprofit, everywhere in the world, for free. We're ironing out how the provisioning system is going to work. Might go live with this in 3-9 months, depending on funding and who we contract the provisioning / intake systems to.

One of the key components for us is writing a ton of end-user documentation for Drupal. Our target audience is the non-tech, uber-busy volunteer / staff person at a church basement nonprofit that has no time to hunt for config options or figure things out. We're literally starting from a "how to log in" perspective.

This means we will, if we're successful, have created documentation that could bring Drupal within the reach of my granddad. I'd like to see this contributed to the handbooks as a reference for consultants, on-demand providers (CSoD, Bryght, ourselves) and others who deal with low-tech audiences.

If we remove the hosting / configuration part of running a successful Drupal installation, there's no reason Drupal can't become a tool for the non-tech masses :)

Of course, I anticipate contributing docs wherever there's a need (not just at the "how do I log in?" level).

Most of our internal docs will be written by a several staff members under my lead, so I'm planning to have a steady flow of docs flowing back in to the handbook once we're up and running.

Let me know if you need any other background info, and thanks!

Dave.