Helping with Storm

Events happening in the community are now at Drupal community events on www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

This is intended for collaboration: Please edit the roles and add yourself on the list as appropriate.

The great thing about open source is the way that together, a group of people can achieve more than anyone could ever do on their own.

On this page, I've listed a few roles that I think could really help Storm if a few people could sign-up to do them. My idea is that if lots of people could be responsible for a small section, we can get development going a lot more effectively.

You do not have to be a coder to help Storm!

The roles I can think of:

Maintainers:

People with repository access, and who make the final decision on whether patches can be committed.

Testers:

People that run an up to date -dev copy of Storm, and report back bugs:

People that write more automated tests for Storm.

  • Drupal 6 branch: [add your name here].
  • Drupal 7 branch: [add your name here].

People that test patches submitted in the issues queue.

Supporters:

People that respond to support requests in the issues queues.

Documenters:

People that ensure that Storm documentation is present and up to date:

  • Drupal 6 branch: Onopoc, aendrew, [add your name here].
  • Drupal 7 branch: Onopoc, [add your name here].

People that create tutorials or blog posts explaining how to use Storm:

Developers:

People that do some coding to fix bugs and add features.

... Please add more, there are lots of things that can help Storm!