Add new comment

No, you don’t have to be a developer to contribute to Drupal Sprints

Cross-posted with permission from Genuine Interactive

Ways to Contribute to 2014 Global Drupal 8 Sprint Weekend

There’s a Drupal Sprint taking place at Genuine in a couple of weeks and you automatically think, “Oh, it’s a developers event.” Think again because that’s a Sprint myth that needs to go away, especially when more contributors are needed to help with pushing Drupal 8 beyond writing code!

A successful Drupal Sprint needs people who can test patches, write documentation, document help issues, design usability features, and more. In preparation for the 2014 Global Drupal 8 Sprint at Genuine on Saturday, Jan. 25, we’ve included three roles that can make the biggest impact.

Issue Writers/Summarizers

The Drupal community uses the issue queue to track any bugs, tasks, improvements, and feature requests for all Drupal projects, including Drupal 8. Contributors can create issues as they come across them, but eventually, some issues become cluttered and the main issue at hand is lost.

That’s where issue writers/summarizers come into play. They help programmers quickly and easily identify the problem, which helps the Sprint move more smoothly. Tips on how to make a good issue report can be found here.

Testers / Reviewers

Do you have a knack for breaking things or an eye for detail? Testers play an important role in the Drupal community and this role is open to everyone and anyone, since it requires no programming skills.

Testers and reviewers use Drupal to test the patches that are submitted to solve an issue. After testing, reviewers respond to the issue to let the programmer know if their patch worked and solved the issue, or if it did not.

To learn more about the issue queue, check out “How to Use the Issue Queue.”

And, of course, Programmers/Developers

Programmers write the code needed to improve existing projects and patch the open issues. Contributors will need to know how to program and have a basic understanding of Drupal. All programmer levels are welcome as there will be session leaders who can help.

Sprints are a great opportunity for novice developers to learn more about Drupal and to receive mentoring from more experienced Drupalists.

The 2014 Global Drupal 8 Sprint will allow all participants to learn more about Drupal 8.

Ready to Sprint?

Now that we’ve explained some of the roles needed, what should all participants do to prepare?

  • Read any documentation posted ahead of the sprint.
  • Participate in any discussions ahead of the sprint.
  • Read up on relevant issues in the issue queue.
  • Prepare the tools and resources they will need to participate.

And, don’t forget to RSVP by Monday, Jan. 20 to use your skills to contribute at the 2014 Global Drupal 8 Sprint Weekend on Saturday, Jan. 25 from 10 a.m. – 5 p.m. at Genuine in Boston.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.