Thanks for your question Jeff,

I look at The Director At Large position on the Drupal Association Board as an incredible opportunity to use my very specific skillset as a Project Manager to balance community feedback with measurable progress as a community. Although I have the technical skills of a 3rd shift sitebuilding intern, I have a track record of measuring and driving velocity and productivity, meeting monetary and timeline goals, and coordinating communcation between all parties. I believe that a position on the Drupal Assocation board would allow me to contribute my talents to this community that has provided me with my livelihood, my vocational callig, and my closest friends.

The first step I will take as a member of the board is to address how we are marketing ourselves and how we are engaging the community. Obviously camps and conventions have a wonderful effect on building our community, but there are a lot of unreached Drupalers that could/would be interested in contributing time and effort into furthering Drupal if they were aware of how much opportuinty there is to plug in. I believe that marketing and community building are the first two aspects of Drupal that I would take on first.

Although a large difficult topic to address in a short period of time, I would like to raise several questions about the current best practices and how those fit into the global development eco-system. For isntance; I would like to revisit the Patch based system and see what the implications of changing that to a more modern repository style system would be. I'm interested in asking (potentially dumb) questions and creating definition around areas that define Drupal as unique as well as potentially antiquate it in order to make the reasons behind those decisions more obvious to our community.

Thanks again for your question Jeff, I appreciate your time and encourage further conversation.

Best regards,
Justin Rhodes