layout | title | redirect_to | permalink |
---|---|---|---|
page |
Initiatives & Get Involved |
/get-involved/ |
The Drupal Diversity Working Group (DDWG) is currently working on the following projects:
-
Organizer Packet A resource for organizers to help them organize and support diverse and inclusive events
-
Infrastructural improvements to the DDWG website & online presence
- Organized BOF (Birds of a Feather) sessions at Drupalcon Baltimore that embraced and represented the interests and identities of Drupal community members.
- Ran a #WeAreDrupal photo booth during DrupalCon Baltimore.
We welcome all types of contributors - programmers, content managers, project support staff, and more. However you identify as a contributor and as part of the Drupal community, there is a place for you to get involved here.
-
Come into the #diversity-inclusion room in the Drupal Slack and say hello! (You can get an automatic invite at http://drupalslack.herokuapp.com if you need one.) If Slack doesn't work for you, you can reach out to us on twitter @drupaldiversity
-
Join us for a meeting. We meet in #diversity-inclusion every Thursday at 9am PST / 17:00pm UTC (The Time Zone Converter is handy for this). You can see our calendar of meetings and sprints below.
-
If there is an issue open in any of our github repositories, it's available to be worked on. We love to see people in the issue queues, and welcome people jumping in wherever they feel comfortable. We try to label issues so that newcomers can quickly find tasks that match their interests. We borrowed this idea from Girl Develop It's issue queue.
You can see our calendar for
- Ical
- HTML
- Google: for google calendar users, you can "Add another calendar" and provide this address [email protected]
As we advocate for the Drupal community to be diverse and inclusive, we are aware that as a working group, we must also work to be inclusive, respectful and diverse. We've adopted the contributor code of conduct created by Contributor Convenant.
(You can review the discussion that lead to this decision here)