A sprint is a get-together for focused work on a project. Sprints are an important part of Drupal's growth, and are also a great opportunity to get involved, because others are on hand to help you contribute. There are many days for sprinting scheduled, so come and collaborate in person with other Drupal community members!
Who Should Come?
Everyone! If you are interested in contributing to Drupal core or contributed projects, this is your chance. You don't need to be a developer to contribute; we need project managers, bug reporters, QA testers, people to help write documentation, etc... If you ARE a developer, but not sure where to get started, we have mentors to show you the ropes.
If you feel new and would love helping hands, the best day to start is the Sunday sprint day. This is the biggest sprint day with many people sprinting and different opportunities based on experience level. For a guided introduction to the tools and processes we use to collaborate, get there first thing in the morning at 10am for a first time contributor workshop.
If you know the tools but still could use help picking issues and going through the process, we will have an experienced contributors there to help newer contributors.
Just bring a laptop.
Lunch will be provided.
Do I Need To Register To Attend?
When Are The Sprints?
- Thursday sprints will take place in Room 220, with room for 80 people
- Sprinting during sessions Friday and Saturday will take place in Room 120AB, starting after the keynote
- Sunday sprints will take place in Room 314A and 314B, with room for 60 people in each room
What Topics Will We Focus On?
Very excited to offer 3 areas of focus:
- Lead: Adam Bergstein
- Contributors verify the current status of the major issues, make sure they are up to date, and close issues that are no longer relevant.
- Core committers and subsystem maintainers collaborate to assess the verified issues.
- All people wanting to work on Core should read xjm's excellent article on the subject: http://xjmdrupal.org/blog/triage-majors-at-camps
- Leads: Joe Shindelar and Blake Hall
- Ensuring there are documentation pages in the new core module’s guide for Drupal 8 for each core module, and that the links to those modules in Drupal’s help text are valid. There are a handful of these pages that need to be created. This task requires minimal experience contributing to Drupal, and can potentially be done even without a local installation setup. https://www.drupal.org/node/2824046
- Learn about the new documentation guides on Drupal.org, how they work, and how you can use them. Then sign up to be a maintainer for a guide that doesn’t currently have a maintainer and help to make sure that summaries and titles are useful, and pages are in an appropriate order after the recent migration. https://www.drupal.org/node/2682083
- Drupal’s coding standards recently changed, and we now use short style array syntax. <code></code>, instead of <code>array()</code>. There is a lot of code in the handbook, and in the Examples for Developers project that needs updating. Great way to practice writing your first patch. https://www.drupal.org/node/2857772
- Prefer to write code? We’ve got a few issues in mind that we could use some help with that require first updating some of the tools we use for documentation, and code reviews, on Drupal.org which we're happy to point people at and try to make progress on.
- Lead: Matt Glaman
- Reach 20 payment gateways (14 currently, before Drupal Dev Days has finished.)
- Work on Promotions to add more conditions, improve the UI Turn current tests into documentation
- Improve Drupal Commerce 1.x, Ubercart 6.x, and Ubercart 7.x migrations.
- Resources include https://github.com/mglaman/commerce-project-template for a development environment ready to test. And https://github.com/mglaman/commerce-migrate-environment for running migrations.