Drupal Global Contribution Weekend

Vancouver 2023

Welcome

Everybody has something to contribute! Be you starting out or a "Triple Certified Drupal Expert", there are plenty of places to help make Drupal awesome.

Please bring: your enthusiasm and curiosity

Getting Set-up

Please have these steps' setup before the contribution weekend!

1. Create an account on Drupal.org

2. Join the conversation Drupal's Slack workspaces

Add Drupal Slack and Van DUG workspaces.

Join the #contribute Slack channel.

3. Choose your own adventure:

Development Environment

Local: DDEV
  1. Install git

  2. Install DDEV

  3. Create a local Drupal website: Clone Drupal 10 with git: 

    mkdir ~/Sites/d10
cd ~/Sites/d10
git clone https://git.drupalcode.org/project/drupal.git web
ddev config
ddev config --composer-root web
ddev composer require drush/drush
    If you plan on working on core these commands will help ensure that git diff won't add extra files. 
    
echo "vendor\n**/sites/default" >> .git/info/exclude
git update-index --assume-unchanged composer.* composer/**/composer.json
  4. Install Drupal and you're ready to patch!

    From within the project directory

    ddev drush si standard
Cloud: DrupalPod
This is great if you don't want to touch your machine(or can't) yet still want to code. DrupalPod
Existing: DYI

You already have your setup, great! Carry on...

Have a peak at the Drupal requirements to tweak your setup.

There are plenty more local development environments to choose from in the guide: Local server setup.

None
There are plenty of ways to contribute without setting up a development environment, from simplytest.me, editing documentation and helping triage and move issues, to editing files directly in Gitlab on drupal.org.

During the day

Mission: Contributions to help stablize Drupal 9 or 10 core and contributed Modules and Themes

Depending on interest/audience, we will gladly show offer to do a demo/training session. And breakout rooms if need be, for example, to tackle Feeds module issues or Basic theme issues.

or

Take a look at the Contributor tasks. Work with another contributor to find a task.

Finding Tasks

Here is my opinionated way to find tasks to work on at a sprint.
Rule of thumb: I'd suggest the best way is to "Scratch your own itch".

  1. Can you recall a piece of functionality that isn't working the way you'd like or you had an idea to improve it, start there and search the issue queue to see if anybody else had a similar/same idea.
  2. Failing your recall, a low effort way: look at patches that you use for your projects, pick a few of those to see if you can't help them get committed upstream.
  3. You can search the issue queue for a special "Task" tag, They are usually tagged with a "Needs ..." tag, (see all special tags) and you can probably do a number of similar tasks on various issues that Needs something (be warned "Needs Tests" generally take a while, but are usually most helpful to get an issue committed, so high cost/high reward)
  4. Still at a lost or not inspired... look at which "Strategic Initiatives" you'd like to see in core

References

Contributing

Standards

Additional tooling-up

Core

Global Contribution Weekend Event Info