April Meetup

These ideas can be easily built with Drupal's built-in functionality and contrib modules. No code would really need to be written. That's not necessarily a bad thing, but it does affect how we plan and execute the "sprint". I could be wrong, but I suspect that the majority of people in attendance would know how to build sites using Drupal's point-and-click tools (Views, CCK, Imagecache, etc).

This is a lot different from code sprints I have attended elsewhere in the Drupal world (at various DrupalCons and DrupalCamps). At a typical code sprint, the group decides on something to build, fix, or enhance. For example, at the core code sprint in Copenhagen, the goal was to fix bugs in D7 until the number of critical bugs was below a certain number. If we took this approach, could do things such as:
* Create on a new contrib module
* Create a D7 version of a module that already exists for D6.
* Work on a new feature for Drupal core.
* Fix bugs in Drupal core (D7 or D8).
* Write SimpleTests for Drupal core or a popular contrib module.

In almost all of these cases, there is something for people at every skill level to contribute: writing code, writing documentation, doing user-acceptance testing. This could also help people learn how to contribute things back to the Drupal community if they don't know how. It gets people familiar with processes such as:
* Using git to manage code and work as a team
* Creating patches
* Write SimpleTests
* Using the test bot to test patches automatically
* Using issue queues on d.o.
* Writing secure code - we could pick a contrib module and analyze it for security vulnerabilities, then report any we find to the security team.

These topics could easily fill our time over the next couple months if we wanted. Maybe we could focus on one area at each meetup. Some could be combined together... just depends on what people would like.

We're planning on 7:00 PM.