Title: DEIB | WordPress.org Project

---

#  Tag Archives: DEIB

 [  ](https://profiles.wordpress.org/coachbirgit/) [Birgit Olzem](https://profiles.wordpress.org/coachbirgit/)
2:20 pm _on_ May 31, 2024     
Tags: [DEI ( 2 )](https://make.wordpress.org/project/tag/dei/),
DEIB, [discussion ( 8 )](https://make.wordpress.org/project/tag/discussion/), [handbook ( 4 )](https://make.wordpress.org/project/tag/handbook/),
[WPDiversity ( 3 )](https://make.wordpress.org/project/tag/wpdiversity/)   

# 󠀁[WordPress Project Contributor Handbook v2](https://make.wordpress.org/project/2024/05/31/wordpress-project-contributor-handbook-v2/)󠁿

In March 2021, Josepha introduced the [proposal of a WordPress Project Contributor Handbook](https://make.wordpress.org/updates/2021/03/16/proposal-a-wordpress-project-contributor-handbook/).
This handbook was intended to be an overarching resource and place for policies,
best practices, guides and other foundational content related to open-source and
the global WordPress project.

_Imagine it as a comprehensive map that will guide every contributor through our
beloved WordPress landscape._

As the founder and spearhead of the [DEIB (Diversity, Equity, Inclusion, and Belonging) working group](https://make.wordpress.org/project/2023/07/13/proposal-for-establishing-a-make-diversity-equity-inclusion-and-belonging-deib-team-within-the-wordpress-community/),
I’m excited to update you on an **exciting development**: we’ve committed ourselves
to a revamp of the Contributor Handbook into the next iteration. This handbook –
like every other handbook – is a living document and needs to grow alongside the
project and its community. 

## The Value of a Unified Guide

The new Contributor Handbook aims to be the quintessential resource for everyone
in our community. It will provide a bird’s-eye view of where to find key information
and how different aspects of our community interconnect. From community engagement
rules to technical guidelines, this handbook will cover it all, making your journey
as a WordPress contributor clearer and more structured.

## Scope

The Contributor Handbook currently includes pages on AccessibilityAccessibility 
Accessibility (commonly shortened to a11y) refers to the design of products, devices,
services, or environments for people with disabilities. The concept of accessible
design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning
compatibility with a person’s assistive technology (for example, computer screen
readers). (https://en.wikipedia.org/wiki/Accessibility), Privacy Policy, a DEI Statement,
the Community Code of Conduct, and Incident Response Team. Pages or parts of documentation
that require legal consideration, like the Privacy Policy, will not be included 
in the scope of this work. Wherever required, the intention is to collaborate with
teams that are most familiar with the page, for example, the Community Code of Conduct
with the Incident Response Team. 

## Collaboration Across Teams

Enhancing the handbook is a collaborative effort involving several key teams:

 * **Community Team**: Focusing on integrating community interaction norms and event
   guidelines.
 * **Documentation Team**: Ensuring that the handbook is comprehensive and easy 
   to navigate.
 * **Project Leadership**: Offering strategic guidance to align the handbook with
   broader WordPress objectives.

This cross-team collaboration ensures that the handbook serves as a holistic guide
to the WordPress ecosystem, tailored to meet the needs of all contributors, new 
and seasoned alike.

## Progress and Acknowledgments

Thank you to [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) and [@angelasjin](https://profiles.wordpress.org/angelasjin/)
for the first iteration of the Contributor Handbook, and for suggestions provided
by [@jeffpaul](https://profiles.wordpress.org/jeffpaul/), [@tobifjellner](https://profiles.wordpress.org/tobifjellner/),
[@dd32](https://profiles.wordpress.org/dd32/), [@juliacanzani](https://profiles.wordpress.org/juliacanzani/),
[@poena](https://profiles.wordpress.org/poena/), [@sereedmedia](https://profiles.wordpress.org/sereedmedia/),
[@joedolson](https://profiles.wordpress.org/joedolson/), [@ryelle](https://profiles.wordpress.org/ryelle/).

Also thanks to [@milana_cap](https://profiles.wordpress.org/milana_cap/), [@j9magayanes](https://github.com/j9magayanes),
[@TantienHime](https://profiles.wordpress.org/tantienhime/), and [@CoachBirgit](https://profiles.wordpress.org/coachbirgit/)
for their foundational work moving the needle forward at the CloudFest Hackathon.
Their efforts led to the creation of a GitHubGitHub GitHub is a website that offers
online implementation of git repositories that can easily be shared, copied and 
modified by other developers. Public repositories are free to host, private repositories
require a paid subscription. GitHub introduced the concept of the ‘pull request’
where code changes done in branches by contributors can be reviewed and discussed
before being merged by the repository owner. [https://github.com/](https://github.com/)
repository, which is now officially part of the WordPress organization, thanks to
[@dd32](https://profiles.wordpress.org/dd32/) and [@leogopal](https://profiles.wordpress.org/leogopal/).
This repository is the new home for our ongoing development and collaboration on
the handbook.

## Call to Action: We Need Your Voice!

Your involvement is crucial as we refine and enhance the handbook:

 * **Review and Feedback**: Dive into the [Contributor Handbook GitHub repository](https://github.com/WordPress/contributor-handbook/)
   to explore the drafts and contribute your suggestions.
 * **Join the Discussion**: Comment below to discuss how the handbook can better
   serve as your go-to resource.

## Conclusion

Our goal is to not just create a handbook, but to foster a living document that 
evolves with our community. Your involvement will help mold it into a dynamic resource
that reflects the needs and knowledge of all WordPress contributors. Together, let’s
build a resource that not only guides, but also inspires and unites us in our shared
mission.

### Next Steps

 * Keep an eye on this blog and our GitHub repositories [WordPress/DEIB-Issue-Tracker](https://github.com/WordPress/contributor-handbook/)
   and [Contributor-Handbook](https://github.com/WordPress/contributor-handbook)
   for updates and draft reviews.
 * Join the conversation in our upcoming DEIB working group meetings every other
   week Friday in [#DEIB-working-group](https://wordpress.slack.com/archives/C05ND1KPW0Y),
   where we’ll discuss the handbook’s progress and gather more feedback.

We’re committed to making the Contributor Handbook a fundamental tool for everyone
in our community. Let’s work together to create a resource that not only informs,
but also empowers.

_Props to [@angelasjin](https://profiles.wordpress.org/angelasjin/) for reviewing
and contributing to this announcement post_

[#DEIB](https://make.wordpress.org/project/tag/deib/) [#DEI](https://make.wordpress.org/project/tag/dei/)
[#discussion](https://make.wordpress.org/project/tag/discussion/) [#handbook](https://make.wordpress.org/project/tag/handbook/)
[#WPDiversity](https://make.wordpress.org/project/tag/wpdiversity/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2024%2F05%2F31%2Fwordpress-project-contributor-handbook-v2%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/coachbirgit/) [Birgit Olzem](https://profiles.wordpress.org/coachbirgit/)
8:08 am _on_ July 13, 2023     
Tags: [5ftF ( 13 )](https://make.wordpress.org/project/tag/5ftf/),
DEIB, [WPDiversity ( 3 )](https://make.wordpress.org/project/tag/wpdiversity/)  

# 󠀁[Proposal for Establishing a Make Diversity, Equity, Inclusion, and Belonging (“DEIB”) Team within the WordPress Community](https://make.wordpress.org/project/2023/07/13/proposal-for-establishing-a-make-diversity-equity-inclusion-and-belonging-deib-team-within-the-wordpress-community/)󠁿

TL;DR: This proposal suggests establishing a Make Diversity, Equity, Inclusion, 
and Belonging (“DEIB”) team within the WordPress community to enhance and support
the existing DEIB initiatives. Building upon the tireless work of fellow community
members, this new team would provide a more structured and coordinated approach 
towards ensuring that all community members feel valued, included, and able to contribute
to their full potential within the safety of our code of conduct.

This team aims to be a **shared resource to all other Make WordPress teams**. The
team’s roles and responsibilities include broadening representation, cultivating
an inclusive culture, promoting equitable opportunities, facilitating collaboration,
and continuous assessment and improvement. The team will work towards clear objectives
and tangible outcomes, such as increased representation, improved inclusivity, and
increased access to opportunities.

**Update**
As we work towards establishing an official DEIB team, a new channel 
on Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
serves as a collaborative space for all members of the working group. Whether you’re
here to contribute to the ongoing efforts or simply to observe and learn, we’re 
glad to have you with us.

Please join [#deib-working-group](https://wordpress.slack.com/archives/C05ND1KPW0Y)
and collaborate on GitHubGitHub GitHub is a website that offers online implementation
of git repositories that can easily be shared, copied and modified by other developers.
Public repositories are free to host, private repositories require a paid subscription.
GitHub introduced the concept of the ‘pull request’ where code changes done in branches
by contributors can be reviewed and discussed before being merged by the repository
owner. [https://github.com/](https://github.com/) [DEIB Project Tracker](https://github.com/orgs/WordPress/projects/131)

---

## The Why

As an active contributing member of the WordPress community for over a decade, I
have witnessed the need for a more structured approach to diversity, equity, inclusion,
and belonging (DEIB) within our community. Although my background doesn’t include
formal academic training in DEIB, my extensive firsthand experiences and keen observations
have shaped my deep understanding in this area. I have faced setbacks, and seen 
fellow community members experience discrimination and ignorance. These experiences
have motivated me to develop this proposal.

While several teams within the community promote diversity, equity, inclusion, and
belonging (DEIB), there is a need for a more structured and coordinated approach
to these efforts in support of the whole project. **A formal DEIB team would provide
this structure, enhancing the existing initiatives and filling gaps where needed.**

This formal proposal has evolved from an initial public idea exploration, which 
can be found in this [blog post on my personal site](https://coachbirgit.com/proposal-wordpress-deib-committee/).
For a more in-depth exploration of this rationale, please refer to our whitepaper,“
[Proposal for Establishing a Formal Diversity, Equity, Inclusion, and Belonging (DEIB) Team](https://docs.google.com/document/d/1Hu8pWjPaeIde18YxykKWs_VN0qx1oqYHr2H1Cm62qZ4/edit#heading=h.svwbqksijc6w)“.

> **Acknowledgements:**
> Before delving into the proposal, it is important to acknowledge
> and thank all the community members who have dedicated their time and skills to
> raise awareness and educate about DEIB. Their tireless work has laid a strong 
> foundation for the generations and iterations to come within the WordPress community.
> Thank you!

### The How: Proposed Role and Responsibilities

The Make DEIB team could become a shared resource to other Make teams, and could
include the following roles and responsibilities:

 1. **Broaden Representation**: The DEIB team would work to ensure that all members
    of the WordPress community, regardless of their background, have a voice and feel
    included. This could involve outreach to underrepresented groups, efforts to make
    the community more welcoming and inclusive, and initiatives to promote diversity
    in leadership roles.
 2. **Cultivate an Inclusive Culture**: The DEIB team would work to create a culture
    where everyone feels valued and included. This could involve training and education
    on DEIB issues, efforts to promote respectful and inclusive communication, and 
    initiatives to celebrate the diversity of the WordPress community.
 3. **Promote Equitable Opportunities**: The DEIB team would work to ensure that opportunities
    within the WordPress community are accessible to all. This could involve efforts
    to make training and education opportunities more inclusive, initiatives to promote
    equitable access to resources, and work to ensure that all community members have
    the opportunity to contribute and participate.
 4. **Facilitate Collaboration**: The DEIB team would work closely with other teams
    within the WordPress community to coordinate DEIB efforts. This could involve sharing
    resources, collaborating on initiatives, and promoting DEIB across the community.
 5. **Continuous Assessment and Improvement**: The DEIB team would implement regular
    assessments of DEIB initiatives and make necessary improvements. This could involve
    collecting and analyzing data on DEIB efforts, seeking feedback from the community,
    and making changes based on this feedback.

For a more detailed discussion of these roles and responsibilities, please check
out the white paper for the proposed Make Diversity, Equity, Inclusion, and Belonging(“
DEIB”) Team by clicking the button below:

[Read the whitepaper for the proposed Make “DEIB” Team](https://docs.google.com/document/d/1Hu8pWjPaeIde18YxykKWs_VN0qx1oqYHr2H1Cm62qZ4/edit)

---

## Enhancing and Supporting Existing DEIB Initiatives

The DEIB team would work closely with other Make WordPress teams, working groups,
and initiatives that touch on DEIB topics, and leverage existing work to support
the WordPress open sourceOpen Source Open Source denotes software for which the 
original source code is made freely available and may be redistributed and modified.
Open Source **must be** delivered via a licensing model, see GPL. project.

### Objectives and Tangible Outcomes:

The DEIB team would have clear objectives and tangible outcomes, particularly regarding
the identified gaps and overlaps. These could include:

 1. **Increased Representation**: Measurable increase in the representation of underrepresented
    groups within the WordPress community, particularly in leadership roles.
 2. **Improved Inclusivity**: Measurable improvements in the inclusivity of the WordPress
    community, as indicated by community surveys or other feedback.
 3. **Increased Access to Opportunities**: Measurable increase in the accessibilityAccessibility
    Accessibility (commonly shortened to a11y) refers to the design of products, devices,
    services, or environments for people with disabilities. The concept of accessible
    design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning
    compatibility with a person’s assistive technology (for example, computer screen
    readers). (https://en.wikipedia.org/wiki/Accessibility) of opportunities within
    the WordPress community, such as training and education opportunities.
 4. **Effective Collaboration**: Evidence of effective collaboration with other teams
    within the WordPress community, such as shared initiatives or resources.
 5. **Continuous Improvement**: Regular assessments of DEIB initiatives and evidence
    of improvements based on these assessments.

---

### Mid-Term Strategy for the DEIB Team:

Over the next 3-5 years, the DEIB team will focus on several key strategic initiatives
to achieve its mission and vision:

 1. **Develop DEIB Guidelines**: We will develop comprehensive DEIB guidelines for 
    the WordPress community. These guidelines will provide clear expectations and best
    practices for promoting diversity, equity, inclusion, and belonging within the 
    community.
 2. **Implement DEIB Training**: We will implement and enhance existing DEIB training
    for all members of the WordPress community. This training will educate community
    members about the importance of DEIB and provide them with the tools and knowledge
    they need to promote these principles in their work and interactions.
 3. **Establish DEIB Metrics**: We will establish clear metrics for measuring the success
    of our DEIB efforts. These metrics will help us track our progress, identify areas
    for improvement, and ensure that we are effectively promote DEIB within the community.
 4. **Promote Diverse Leadership**: We will launch initiatives to promote diverse leadership
    within the WordPress community. This could include mentorship programs, leadership
    training for underrepresented groups, and efforts to ensure diverse representation
    in decision-making processes.
 5. **Enhance Community Engagement**: We will enhance community engagement by creating
    opportunities for all community members to contribute to DEIB efforts. This could
    include community forums, DEIB working groups, and opportunities for feedback and
    input on DEIB initiatives.
 6. **Collaborate with Existing Teams**: We will work closely with existing teams within
    the WordPress project to coordinate and enhance DEIB efforts. This will help to
    ensure that DEIB is integrated into all aspects and that our efforts are aligned
    and complementary.

By focusing on these initiatives, the DEIB team can help to ensure that the WordPress
community is a place where everyone feels valued, included, and able to contribute
to their full potential.

[Please refer to the whitepaper](https://docs.google.com/document/u/0/d/1Hu8pWjPaeIde18YxykKWs_VN0qx1oqYHr2H1Cm62qZ4/edit)
for a more comprehensive understanding of these objectives and tangible outcomes.

---

## Your turn: share your thoughts!

By establishing a formal DEIB team, the WordPress community can enhance its commitment
to diversity, equity, inclusion, and belonging, ensuring that all community members
feel valued, included, and able to contribute to their full potential within the
safety of our [community code of conduct.](https://make.wordpress.org/handbook/community-code-of-conduct/)

I invite all community members to provide feedback, thoughts, and suggestions on
this proposal. Your input is invaluable as we work together towards a more inclusive
and diverse WordPress community. Together, we can achieve more.** Please leave your
thoughts and feedback as a comment on the proposal below. **

Proposal from: Birgit Olzem ([@coachbirgit](https://profiles.wordpress.org/coachbirgit/))

_Reviewed and supported by (in no particular order): _[_@martatorre_](https://profiles.wordpress.org/martatorre/)_,_
[_@jillbinder_](https://profiles.wordpress.org/jillbinder/)_ _[_@courane01_](https://profiles.wordpress.org/courane01/)_,_
[_@angelasjin_](https://profiles.wordpress.org/angelasjin/)_ [@harishanker](https://profiles.wordpress.org/harishanker/)_
[_@bph_](https://profiles.wordpress.org/bph/) [_@francina_](https://profiles.wordpress.org/francina/)
[_@annebovelett_](https://profiles.wordpress.org/annebovelett/) [_@kau-boy_](https://profiles.wordpress.org/kau-boy/)
[_@devinmaeztri_](https://profiles.wordpress.org/devinmaeztri/) [_@evelina87_](https://profiles.wordpress.org/evelina87/)

[#5ftf](https://make.wordpress.org/project/tag/5ftf/), [#deib](https://make.wordpress.org/project/tag/deib/),
[#wpdiversity](https://make.wordpress.org/project/tag/wpdiversity/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fproject%2F2023%2F07%2F13%2Fproposal-for-establishing-a-make-diversity-equity-inclusion-and-belonging-deib-team-within-the-wordpress-community%2F%23respond&locale=en_US)