Jun 06 2019
Jun 06

One of the chartered responsibilities of the Drupal Community Working Group (CWG) is to work to develop and support community initiatives that promote the health of the Drupal community and help to prevent conflict and burnout. One of the ways that we do this is by organizing workshops designed to provide community leaders with the knowledge, tools, and resources they need to help keep our community a friendly and welcoming place.

Following feedback from last year’s Teamwork and Leadership workshop at DrupalCon Nashville, we decided to narrow the focus and audience for our next workshop. One of the things we’ve observed over the last year in the Drupal community is that many of the issues we’ve seen have had to do with communication breakdowns between various individuals and groups. Following internal discussion in late 2018, we decided that one way to begin addressing this issue was by bringing together leaders in the community representing different groups and interests for a workshop focused on communication skills at DrupalCon Seattle.

In early 2019, we interviewed a number of potential facilitators suggested by Drupal Association board chair Adam Goodman and selected Megan Bernard, a professor of communication studies who specializes in promoting meaningful and inclusive learning and collaboration. Based on Prof. Bernard’s recommendation, we decided to spread this year’s workshop out over two days (April 10-11) in a dedicated meeting room provided by the Drupal Association, who generously covered all fees and expenses.

After finalizing the logistics, we then reached out to those who had attended last year’s workshop, as well as additional community members involved with community governance, camp organizing, core and contrib maintainers, the Drupal Security Team, Drupal Diversity & Inclusion, and the Drupal Association. The workshop facilitator suggested that we keep the size of the workshop to around 20 people, focusing on individuals who are well-connected in the community in hopes that they can help distribute the lessons learned in the workshop. 17 people attended some or all of the first day of the workshop, and 18 attended some or all of the second. In total, community members from 10 different countries spread across 4 different continents were represented.

Day one of the workshop included introductions, a discussion of needs, assets, and challenges faced by various groups within the Drupal community, and a discussion of shared context and perspective. We talked about different ways that other online communities help communicate context about their users, such as identifying the primary language, pronouns, and location in comment threads. During our discussion, Neil Drumm pointed out there was already an active issue led by justafish and others to allow users to display this kind of information, and one of the first action items we agreed on was helping it get implemented on Drupal.org as quickly as possible.

Another topic of discussion centered around creating pre-written template responses that maintainers and/or other privileged users could use in issue threads to “nudge” users in the right direction and realign communication when conversations start trending away from our community standards. We discussed badges and other ways to promote positive communication in our issues threads and other community spaces. In addition, we also talked about better ways to on-board new members into the project and foster an ongoing sense of community. One insight was that small cohorts of 6-8 people are far more effective than 1:1 mentoring at building community engagement.

In our second day, we dug more deeply into the concepts of emotional intelligence, de-escalation practices, and different forms of conflict. One of our exercises was a case study challenge, where different groups were tasked with finding different ways to resolve typical kinds of conflicts often seen in Drupal and other open source communities.

We also spent time talking about different ways to apply some of the things we had learned to our own community, and next steps. We agreed as a group to focus on three main areas:

  1. Setting context in issue queues. This work had already been mostly completed in https://www.drupal.org/node/2961229 so it was really just a matter of working with DA staff to get it implemented on Drupal.org.

  2. Nudges. A group of us decided to do more research into pre-written templates to use in issue queues, forums, and Slack to gently steer things back in the right direction when conversations were starting to go in a negative direction.

  3. Improving Drupal.org user on-boarding and cohorts. In addition to better identifying new users on the site, we agreed to look into various ways to help community members join small cohorts, organized by industry, technology, geography, or other criteria. We felt it was important that this be an opportunity that’s open to existing community members as well as new ones.

The folks assigned to each area agreed to find a time to meet in the coming weeks and to involve other interested community members as well. The CWG also identified several opportunities to improve and streamline its internal processes and communication practices.

By developing and communicating best practices that can be shared across the community, the hope is that we can help build structures for self-guided conflict resolution among community members and support more effective communication overall.

Apr 25 2019
Apr 25

Earlier this month at DrupalCon Seattle, the Drupal Community Working Group (CWG) announced plans to begin the process of reviewing the Drupal Code of Conduct. The Drupal Code of Conduct, which is maintained and upheld by the CWG, governs interactions between community members. It is distinct from the DrupalCon Code of Conduct, which governs interactions at DrupalCon and other in-person events and is maintained and enforced by Drupal Association staff.

The current Drupal Code of Conduct was adopted in 2010 and last revised in 2014. Over the last two years, the CWG has received consistent feedback from the community that the Drupal Code of Conduct should be updated so that it is clearer and more actionable:

  • A set of recommendations for improving the Code of Conduct was shared as one of the high-level findings from the community discussions facilitated by Whitney Hess in April and May 2017.

  • 63% of respondents to a community governance survey held in July 2017 said that updating our codes of conduct should be prioritized as part of the process of overhauling community governance.

  • Improving the community code of conduct so that it is clearer and more actionable was also one of the key takeaways of the community governance discussions that occurred in the fall of 2017.

Over the last year, the CWG has been working on implementing changes to its charter to make the group more accountable to the community-at-large and provide a sustainable foundation for future growth. Now that those changes are complete, the CWG is now able to shift focus to the process of reviewing and improving the Drupal Code of Conduct.

To that end, we have set up a survey at https://forms.gle/rhKHorXXnp3wPQn2A for community members to share their thoughts, both about the current Code of Conduct and the next steps in the process. The results of this survey will help the CWG determine how, when, and who is involved in reviewing and updating the Code of Conduct.

We will be accepting responses through May 31, 2019, and we encourage as many community members to participate as possible.

Nov 21 2018
Nov 21

The Drupal Community Working Group is happy to announce the addition of Alex Burrows (aburrows). Based in Surrey, United Kingdom, Alex has been contributing to the Drupal project and community for more than a decade. He is one of the lead organizers of Drupalcamp London, and a frequent speaker at other Drupal events. Alex also serves as a volunteer police constable in his local community.

The CWG would also like to announce that both Josef Dabernig (dasjo) and Manjit Singh (Manjit.Singh) have agreed to serve as Subject Matter Experts (SMEs) to the CWG. SMEs are not full members of the group, but can be called upon on an as-needed basis for issues that might require specific knowledge or expertise. SMEs are subject to the same Code of Ethics as full members of the CWG.

Adam Hill and Emma Karayannis are also officially stepping down as members of the CWG. We would like to thank both Adam and Emma for their invaluable contributions to the group and for their ongoing contributions to the Drupal community.

The CWG continues to seek new members and SMEs as it seeks to increase the diversity of its membership. It is our hope that by expanding our membership, the CWG will be able to better serve the community in a more proactive manner. If you think you or someone you know might be a good fit for the CWG and are interested in learning more, please reach out to us via email at [email protected].

In other news, the CWG recently proposed a set of changes to its charter to address feedback and concerns raised by the community over the last year and a half. We are accepting feedback from the community through November 23 before finalizing the proposal.

The CWG is responsible for promoting and upholding the Drupal Code of Conduct and maintaining a friendly and welcoming community for the Drupal project. To learn more about the group and what we’ve been up to over the last year, check out our recently-published annual report.

Nov 21 2018
Nov 21

The Drupal Community Working Group is happy to announce the addition of Alex Burrows (aburrows). Based in Surrey, United Kingdom, Alex has been contributing to the Drupal project and community for more than a decade. He is one of the lead organizers of Drupalcamp London, and a frequent speaker at other Drupal events. Alex also serves as a volunteer police constable in his local community.

The CWG would also like to announce that both Josef Dabernig (dasjo) and Manjit Singh (Manjit.Singh) have agreed to serve as Subject Matter Experts (SMEs) to the CWG. SMEs are not full members of the group, but can be called upon on an as-needed basis for issues that might require specific knowledge or expertise. SMEs are subject to the same Code of Ethics as full members of the CWG.

Adam Hill and Emma Karayannis are also officially stepping down as members of the CWG. We would like to thank both Adam and Emma for their invaluable contributions to the group and for their ongoing contributions to the Drupal community.

The CWG continues to seek new members and SMEs as it seeks to increase the diversity of its membership. It is our hope that by expanding our membership, the CWG will be able to better serve the community in a more proactive manner. If you think you or someone you know might be a good fit for the CWG and are interested in learning more, please reach out to us via email at [email protected].

In other news, the CWG recently proposed a set of changes to its charter to address feedback and concerns raised by the community over the last year and a half. We are accepting feedback from the community through November 23 before finalizing the proposal.

The CWG is responsible for promoting and upholding the Drupal Code of Conduct and maintaining a friendly and welcoming community for the Drupal project. To learn more about the group and what we’ve been up to over the last year, check out our recently-published annual report.

Sep 15 2018
Sep 15

Who Are We?

The Drupal Community Working Group (CWG) is responsible for promoting and upholding the Drupal Code of Conduct and maintaining a friendly and welcoming community for the Drupal project.

The CWG is an independent group chartered directly by Dries Buytaert in his capacity as project lead. The original members of the CWG were appointed by Dries in March of 2013. Since then, new CWG members have been selected by the group from the Drupal community, and then approved by Dries. The CWG is made up entirely of community volunteers, and does not currently have any funding, staff, legal representation, or outside resources.

The CWG’s current active membership is:

  • George DeMet (United States): Joined CWG in March 2013, chair since March, 2016.
  • Michael Anello (United States): Joined CWG in December 2015.
  • Jordana Fung (Suriname): Joined CWG in May 2017.

Rachel Lawson (United Kingdom) was a member of the CWG from May through December 2017, when she started a new position as the Drupal Association’s Community Liaison.

Emma Karayiannis (United Kingdom) and Adam Hill (United Kingdom) have informed the CWG of their intention to formally step down from the CWG once replacements can be found for them; we are currently engaged in a search process to identify new members to fill their positions.

The CWG is also building a network of volunteer subject matter experts who we can reach out to for advice in situations that require specific expertise; e.g., cultural, legal, or mental health issues.

What Do We Do?

The CWG is tasked with maintaining a friendly and welcoming contributor community for the Drupal project. In addition to maintaining and upholding the Drupal Code of Conduct and working with other responsible entities within the Drupal ecosystem to ensure its enforcement, the CWG also helps community members resolve conflicts through an established process, acting as a point of escalation, mediation, and/or final arbitration for the Drupal community in case of intractable conflicts. We also provide resources, consultation and advice to community members upon request.

Other activities the CWG has engaged in in the past year include:

  • Sharing experiences and best practices with representatives from other open source projects, both in a one-on-one setting and at various open source community events.
  • Recognizing community leadership through the Aaron Winborn Award, which is presented annually to an individual who demonstrates personal integrity, kindness, and above-and-beyond commitment to the Drupal community.
  • Helping to ensure the community’s voice is represented in the governance process. While the CWG’s charter does not allow it to make community-wide governance decisions, the CWG did work with other interested members of the community to help organize and facilitate a series of community governance meetings in the fall of 2017 following the results of a survey conducted by the Drupal Association. Results and takeaways from these meetings were also shared with the community-at-large.
  • Organizing a Teamwork and Leadership Workshop at DrupalCon Nashville to explore teamwork, leadership, and followership in the context of the Drupal community. Our goal was to expand the base of people who can step into leadership positions in the Drupal community, and to help those who may already be in those positions be more effective. Takeaways from this event were also shared with the community-at-large.
  • With input from the community, drafting and adopting a Code of Ethics for CWG members that clearly defines expectations for members around subjects such as confidentiality and conflicts of interest.

Incident Reports

The CWG receives incident reports from Drupal community members via its incident report form or via email.

  • In 2017, the CWG received 43 official incident reports submitted.
  • From January 1 through September 14, 2018, the CWG has received 33 official incident reports.

In addition, we regularly receive informal reports from community members, which are not included in the totals above. With informal reports, we often encourage the community member to file an official report as well to establish a written record of the incident and to ensure that they have as much agency as possible over how the issue is addressed.

The types of issues that the CWG has received in the last year include:

  • Community members being disrespectful and rude in issue queues.
  • Technical disagreements and frustrations that turn into personal attacks.
  • Abusive language and harassment in Drupal Slack and IRC.
  • Appeals of bans made by Drupal Slack moderators.
  • Inappropriate language and content at community events.
  • Harassment and trolling of community members on social media .
  • Physical harassment of community members (both in and outside of community spaces).
  • Ongoing issues involving specific community members with established patterns of behavior that are disruptive to others.
  • Drupal trademark questions and issues (these are referred to Dries Buytaert, who is responsible for enforcing the Drupal trademark and logo policy).

The CWG also chose not to act on several reports it felt were being made in bad faith and/or in an attempt to harass or intimidate other community members. As per its charter, the CWG also does not respond to requests to take specific punitive action against members of the community. Our goal is to help people understand and take responsibility for the impact that their words and actions have on others.

The CWG relies primarily on its established conflict resolution process to address incident reports. Depending on the situation, this may involve one or more CWG members providing mediation between the parties in conflict or suggesting ways that they can resolve the issue themselves. For matters that may take an unusually long time to resolve, we provide all involved parties with regular status reports so they know that their issue is still being worked on.

In cases of a clear Code of Conduct violation, the CWG will take immediate steps as necessary to ensure the safety of others in the community up to and including recommending permanent or temporary bans from various Drupal community spaces, such as Slack, IRC, Drupal.org, or DrupalCon and other Drupal events.

Other outcomes may include:

  • Discussion of the issue with involved parties to try to find a mutually acceptable and beneficial outcome.
  • Asking one or more of the involved parties to apologize and/or take other actions to address the consequences of their behavior.
  • Discussion of the issue with the involved parties, after which someone may choose to leave the community voluntarily.
  • Asking someone to leave the community if they are not willing or able to address the consequences of their behavior.
  • Recommending bans from various community spaces, including virtual spaces

In some cases, we may receive an after-the-fact report about a situation that has already been resolved, or where the person making the report has asked for no action to be taken. In those cases, we review the incident, decide whether further action is necessary, and keep it on file for reference in case something similar happens in the future.

While the CWG has in the past directly acted as code of conduct enforcement contacts for DrupalCon (which is run by the Drupal Association and has its own code of conduct distinct from that of the community), as of November 2017 those duties have been assumed by DrupalCon staff. The CWG and DrupalCon staff continue to coordinate with each other to ensure that reports are handled by the appropriate responsible body.

Sharing With the Community

The CWG publishes anonymized versions of its weekly minutes that are shared with the community via our public Google Drive folder. These minutes are also promoted via the CWG’s Twitter account @drupalcommunity.

In addition to the public minutes, the CWG also occasionally issues public statements regarding issues of importance to the broader community and beyond:

The CWG also maintains a public issue queue on Drupal.org. Following a series of community discussions in the spring of 2017, the CWG filed a series of issues in this queue to clarify points of confusion and address outstanding concerns about its role in the community.

The CWG also presents sessions at DrupalCon, as well as other camps and events. Sessions presented at DrupalCon in the last year include:

In addition, CWG members have also organized, spoken, and/or participated in Q&A sessions about the CWG at the following events:

  • MidCamp (Chicago, IL)
  • DrupalCamp Asheville (Asheville, NC)
  • Twin Cities DrupalCamp (Minneapolis, MN)
  • DrupalCamp Colorado (Denver, CO)
  • FOSS Backstage (Munich, Germany)
  • Community Leadership Summit (Portland, OR)
  • Edinburgh Drupal User Group (Edinburgh, Scotland)
  • Open Source North East (Newcastle upon Tyne, England)
  • All Things Open (Raleigh, NC) - Upcoming

The CWG is also exploring ways it can make itself available more often to the community via real-time virtual channels such as Slack, Google Meet, or Zoom.

New Challenges

Online Harassment

The number of incidents that the CWG handles relating to online harassment, particularly on social media, has increased significantly in the last couple of years. Because this harassment is often perpetrated by individuals or groups of people posting from behind anonymous accounts, it is sometimes difficult for the CWG to positively identify those responsible and hold them accountable for their actions. This is compounded by the apparent lack of interest from leading social media companies in taking action against abusive accounts or addressing harassment that occurs on their platforms in any effective or meaningful way.

The Drupal community’s switch from IRC to Slack for much of its real-time communication has also provided another vector for harassment, particularly targeting people who participate in communities of interest that focus on topics such as diversity, inclusion, and women in Drupal. While it is possible to ban individual Slack accounts, it is fairly easy for perpetrators to create new ones, and because they are not always tied to Drupal.org IDs, it is sometimes difficult to identify who is responsible for them.

Sexual Harassment and Abuse

Following reports last year relating to sexual harassment in the Drupal community, the CWG understands that there are likely additional incidents that have occurred in the past that have gone unaddressed because we are unaware of them. While our code of conduct is clear that we do not tolerate abuse or harassment in our community, we also know that people don’t always feel safe reporting incidents or discussing their concerns openly. As a consequence, nothing is done about them, which undermines the effectiveness of our code of conduct and in turn leads to fewer reports and more incidents that go unaddressed.

It is our opinion as a group that open source communities across the board need better mechanisms and procedures for handling reports of sexual abuse, harassment, and/or assault. We also need to keep better records of incidents that have occurred, so that we can more quickly identify patterns of conduct and abuse, and better ways to recognize and address incidents across projects so that people who have engaged in harassment and abuse in one community aren’t able to repeat that behavior in another community.

Staffing and Resources

We need to ensure that the CWG is adequately staffed to assist with the increasing number of incident reports we receive each year. While several members have pursued relevant professional development and training opportunities at their own expense, the CWG currently has no direct access to funds or resources to pursue them as a group. As a volunteer community group chartered by the project lead, the CWG also currently operates without the benefit of legal protection or insurance coverage.

Initiatives for 2018/2019

Governance Changes

While the CWG is not allowed to make changes to its own charter, in early 2017 we explored a number of potential changes that we had intended to propose to Dries to help make our group more effective and better positioned to proactively address the needs of the Drupal community.

That work was put on hold following a series of community discussions that occurred in the spring of 2017.  Those conversations surfaced questions, suggestions, and concerns about the accountability, escalation points, and overall role of the CWG, many of which we documented and addressed in our public issue queue. While we were able to address many of the issues that were raised, some can only be addressed with changes to the CWG’s charter.

We fully support and appreciate the ongoing work of the Governance Task Force to update and reform Drupal community governance. While we understand that additional changes may occur pending the outcome of the overall governance reform process, we also feel that there are some changes related to the CWG that need to be made as soon as possible. These proposed changes are currently under review both internally as well as with Dries and other involved stakeholders, and will be shared with the community for review and comment prior to adoption.

Updating the Community’s Code of Conduct

The current Drupal community code of conduct was published in 2010 and is based on the Ubuntu code of conduct.  As per its charter, the CWG is responsible for “maintain[ing] the Conflict Resolution Process (CRP) and related documentation, including the Drupal Code of Conduct”. The CWG has made several changes to the code of conduct over the years, the most significant of which was the addition of the conflict resolution policy in 2014, much of which was inspired by work done within the Django community.

While Drupal was one of the first open source projects to adopt a code of conduct, many others have done so since, and there are a variety of models and best practices for open source community codes of conduct. Based on feedback that we have received over the past year, the CWG is working on an initiative to review and update Drupal’s community code of conduct with input and involvement from both the community-at-large as well as outside experts with code of conduct experience from other projects. Our goal is to introduce this initiative before the end of 2018.

Dealing with Banned Individuals

Some local event organizers have asked the CWG for better tools to ensure that they weren’t inadvertently providing a platform to people who have been banned from speaking at or attending other events due to code of conduct violations.  While the number of people who have been banned from attending DrupalCon and other Drupal events is very small, a comprehensive list of the identities of those individuals is currently known only to the CWG and the Drupal Association.

While the CWG does not generally publish the names of individuals who have been asked not to attend Drupal events, we do reserve the right to publish their names and the reasons for their ban if they do not abide by it.  While we believe that this is effective at deterring individuals from attending events they have been banned from, we also understand that it does not always provide other attendees and/or conference organizers with the tools they need to ensure a safe environment at their events.

Members of the CWG have discussed this issue with their counterparts in other communities, and it does not appear that there are consistently established best practices for handling these kinds of situations, particularly in communities as decentralized as Drupal. With the input of the community, we would like to establish clear and consistent guidelines for local event organizers.  

Community Workshops and Training

In 2016, the CWG conducted a survey and interviews of Drupal core contributors to identify sources of frustration during the Drupal 8 development cycle. One of our recommendations was for the project to focus more on developing skills like creative problem solving, conflict resolution, effective advocacy, and visioning in order to broaden understanding of Drupal’s community, its assets and its challenges.

Following the success of the teamwork and leadership workshop that the CWG led in collaboration with the Drupal Association at DrupalCon Nashville in 2018, the CWG is exploring opportunities for additional workshops and training at DrupalCon Seattle and other events.

Summary

Over the past few years, the Drupal project and community has grown rapidly, bringing a series of new and evolving challenges. Not only has the project grown progressively more complex with each major release, but the time between releases has increased and more is being asked of the developer community by customers and end-users.

We believe this is a significant contributing factor in the increase in the number of documented incidents of negative conflict, which left unaddressed may result in a decline in contributor productivity and morale. The work of the Community Working Group seeks not only to mitigate the impact of negative conflict, but also to provide the community with the tools and resources it needs to make the Drupal project a safer, more welcoming, and inclusive place.

Sep 15 2018
Sep 15

Who Are We?

The Drupal Community Working Group (CWG) is responsible for promoting and upholding the Drupal Code of Conduct and maintaining a friendly and welcoming community for the Drupal project.

The CWG is an independent group chartered directly by Dries Buytaert in his capacity as project lead. The original members of the CWG were appointed by Dries in March of 2013. Since then, new CWG members have been selected by the group from the Drupal community, and then approved by Dries. The CWG is made up entirely of community volunteers, and does not currently have any funding, staff, legal representation, or outside resources.

The CWG’s current active membership is:

  • George DeMet (United States): Joined CWG in March 2013, chair since March, 2016.
  • Michael Anello (United States): Joined CWG in December 2015.
  • Jordana Fung (Suriname): Joined CWG in May 2017.

Rachel Lawson (United Kingdom) was a member of the CWG from May through December 2017, when she started a new position as the Drupal Association’s Community Liaison.

Emma Karayiannis (United Kingdom) and Adam Hill (United Kingdom) have informed the CWG of their intention to formally step down from the CWG once replacements can be found for them; we are currently engaged in a search process to identify new members to fill their positions.

The CWG is also building a network of volunteer subject matter experts who we can reach out to for advice in situations that require specific expertise; e.g., cultural, legal, or mental health issues.

What Do We Do?

The CWG is tasked with maintaining a friendly and welcoming contributor community for the Drupal project. In addition to maintaining and upholding the Drupal Code of Conduct and working with other responsible entities within the Drupal ecosystem to ensure its enforcement, the CWG also helps community members resolve conflicts through an established process, acting as a point of escalation, mediation, and/or final arbitration for the Drupal community in case of intractable conflicts. We also provide resources, consultation and advice to community members upon request.

Other activities the CWG has engaged in in the past year include:

  • Sharing experiences and best practices with representatives from other open source projects, both in a one-on-one setting and at various open source community events.
  • Recognizing community leadership through the Aaron Winborn Award, which is presented annually to an individual who demonstrates personal integrity, kindness, and above-and-beyond commitment to the Drupal community.
  • Helping to ensure the community’s voice is represented in the governance process. While the CWG’s charter does not allow it to make community-wide governance decisions, the CWG did work with other interested members of the community to help organize and facilitate a series of community governance meetings in the fall of 2017 following the results of a survey conducted by the Drupal Association. Results and takeaways from these meetings were also shared with the community-at-large.
  • Organizing a Teamwork and Leadership Workshop at DrupalCon Nashville to explore teamwork, leadership, and followership in the context of the Drupal community. Our goal was to expand the base of people who can step into leadership positions in the Drupal community, and to help those who may already be in those positions be more effective. Takeaways from this event were also shared with the community-at-large.
  • With input from the community, drafting and adopting a Code of Ethics for CWG members that clearly defines expectations for members around subjects such as confidentiality and conflicts of interest.

Incident Reports

The CWG receives incident reports from Drupal community members via its incident report form or via email.

  • In 2017, the CWG received 43 official incident reports submitted.
  • From January 1 through September 14, 2018, the CWG has received 33 official incident reports.

In addition, we regularly receive informal reports from community members, which are not included in the totals above. With informal reports, we often encourage the community member to file an official report as well to establish a written record of the incident and to ensure that they have as much agency as possible over how the issue is addressed.

The types of issues that the CWG has received in the last year include:

  • Community members being disrespectful and rude in issue queues.
  • Technical disagreements and frustrations that turn into personal attacks.
  • Abusive language and harassment in Drupal Slack and IRC.
  • Appeals of bans made by Drupal Slack moderators.
  • Inappropriate language and content at community events.
  • Harassment and trolling of community members on social media .
  • Physical harassment of community members (both in and outside of community spaces).
  • Ongoing issues involving specific community members with established patterns of behavior that are disruptive to others.
  • Drupal trademark questions and issues (these are referred to Dries Buytaert, who is responsible for enforcing the Drupal trademark and logo policy).

The CWG also chose not to act on several reports it felt were being made in bad faith and/or in an attempt to harass or intimidate other community members. As per its charter, the CWG also does not respond to requests to take specific punitive action against members of the community. Our goal is to help people understand and take responsibility for the impact that their words and actions have on others.

The CWG relies primarily on its established conflict resolution process to address incident reports. Depending on the situation, this may involve one or more CWG members providing mediation between the parties in conflict or suggesting ways that they can resolve the issue themselves. For matters that may take an unusually long time to resolve, we provide all involved parties with regular status reports so they know that their issue is still being worked on.

In cases of a clear Code of Conduct violation, the CWG will take immediate steps as necessary to ensure the safety of others in the community up to and including recommending permanent or temporary bans from various Drupal community spaces, such as Slack, IRC, Drupal.org, or DrupalCon and other Drupal events.

Other outcomes may include:

  • Discussion of the issue with involved parties to try to find a mutually acceptable and beneficial outcome.
  • Asking one or more of the involved parties to apologize and/or take other actions to address the consequences of their behavior.
  • Discussion of the issue with the involved parties, after which someone may choose to leave the community voluntarily.
  • Asking someone to leave the community if they are not willing or able to address the consequences of their behavior.
  • Recommending bans from various community spaces, including virtual spaces

In some cases, we may receive an after-the-fact report about a situation that has already been resolved, or where the person making the report has asked for no action to be taken. In those cases, we review the incident, decide whether further action is necessary, and keep it on file for reference in case something similar happens in the future.

While the CWG has in the past directly acted as code of conduct enforcement contacts for DrupalCon (which is run by the Drupal Association and has its own code of conduct distinct from that of the community), as of November 2017 those duties have been assumed by DrupalCon staff. The CWG and DrupalCon staff continue to coordinate with each other to ensure that reports are handled by the appropriate responsible body.

Sharing With the Community

The CWG publishes anonymized versions of its weekly minutes that are shared with the community via our public Google Drive folder. These minutes are also promoted via the CWG’s Twitter account @drupalcommunity.

In addition to the public minutes, the CWG also occasionally issues public statements regarding issues of importance to the broader community and beyond:

The CWG also maintains a public issue queue on Drupal.org. Following a series of community discussions in the spring of 2017, the CWG filed a series of issues in this queue to clarify points of confusion and address outstanding concerns about its role in the community.

The CWG also presents sessions at DrupalCon, as well as other camps and events. Sessions presented at DrupalCon in the last year include:

In addition, CWG members have also organized, spoken, and/or participated in Q&A sessions about the CWG at the following events:

  • MidCamp (Chicago, IL)
  • DrupalCamp Asheville (Asheville, NC)
  • Twin Cities DrupalCamp (Minneapolis, MN)
  • DrupalCamp Colorado (Denver, CO)
  • FOSS Backstage (Munich, Germany)
  • Community Leadership Summit (Portland, OR)
  • Edinburgh Drupal User Group (Edinburgh, Scotland)
  • Open Source North East (Newcastle upon Tyne, England)
  • All Things Open (Raleigh, NC) - Upcoming

The CWG is also exploring ways it can make itself available more often to the community via real-time virtual channels such as Slack, Google Meet, or Zoom.

New Challenges

Online Harassment

The number of incidents that the CWG handles relating to online harassment, particularly on social media, has increased significantly in the last couple of years. Because this harassment is often perpetrated by individuals or groups of people posting from behind anonymous accounts, it is sometimes difficult for the CWG to positively identify those responsible and hold them accountable for their actions. This is compounded by the apparent lack of interest from leading social media companies in taking action against abusive accounts or addressing harassment that occurs on their platforms in any effective or meaningful way.

The Drupal community’s switch from IRC to Slack for much of its real-time communication has also provided another vector for harassment, particularly targeting people who participate in communities of interest that focus on topics such as diversity, inclusion, and women in Drupal. While it is possible to ban individual Slack accounts, it is fairly easy for perpetrators to create new ones, and because they are not always tied to Drupal.org IDs, it is sometimes difficult to identify who is responsible for them.

Sexual Harassment and Abuse

Following reports last year relating to sexual harassment in the Drupal community, the CWG understands that there are likely additional incidents that have occurred in the past that have gone unaddressed because we are unaware of them. While our code of conduct is clear that we do not tolerate abuse or harassment in our community, we also know that people don’t always feel safe reporting incidents or discussing their concerns openly. As a consequence, nothing is done about them, which undermines the effectiveness of our code of conduct and in turn leads to fewer reports and more incidents that go unaddressed.

It is our opinion as a group that open source communities across the board need better mechanisms and procedures for handling reports of sexual abuse, harassment, and/or assault. We also need to keep better records of incidents that have occurred, so that we can more quickly identify patterns of conduct and abuse, and better ways to recognize and address incidents across projects so that people who have engaged in harassment and abuse in one community aren’t able to repeat that behavior in another community.

Staffing and Resources

We need to ensure that the CWG is adequately staffed to assist with the increasing number of incident reports we receive each year. While several members have pursued relevant professional development and training opportunities at their own expense, the CWG currently has no direct access to funds or resources to pursue them as a group. As a volunteer community group chartered by the project lead, the CWG also currently operates without the benefit of legal protection or insurance coverage.

Initiatives for 2018/2019

Governance Changes

While the CWG is not allowed to make changes to its own charter, in early 2017 we explored a number of potential changes that we had intended to propose to Dries to help make our group more effective and better positioned to proactively address the needs of the Drupal community.

That work was put on hold following a series of community discussions that occurred in the spring of 2017.  Those conversations surfaced questions, suggestions, and concerns about the accountability, escalation points, and overall role of the CWG, many of which we documented and addressed in our public issue queue. While we were able to address many of the issues that were raised, some can only be addressed with changes to the CWG’s charter.

We fully support and appreciate the ongoing work of the Governance Task Force to update and reform Drupal community governance. While we understand that additional changes may occur pending the outcome of the overall governance reform process, we also feel that there are some changes related to the CWG that need to be made as soon as possible. These proposed changes are currently under review both internally as well as with Dries and other involved stakeholders, and will be shared with the community for review and comment prior to adoption.

Updating the Community’s Code of Conduct

The current Drupal community code of conduct was published in 2010 and is based on the Ubuntu code of conduct.  As per its charter, the CWG is responsible for “maintain[ing] the Conflict Resolution Process (CRP) and related documentation, including the Drupal Code of Conduct”. The CWG has made several changes to the code of conduct over the years, the most significant of which was the addition of the conflict resolution policy in 2014, much of which was inspired by work done within the Django community.

While Drupal was one of the first open source projects to adopt a code of conduct, many others have done so since, and there are a variety of models and best practices for open source community codes of conduct. Based on feedback that we have received over the past year, the CWG is working on an initiative to review and update Drupal’s community code of conduct with input and involvement from both the community-at-large as well as outside experts with code of conduct experience from other projects. Our goal is to introduce this initiative before the end of 2018.

Dealing with Banned Individuals

Some local event organizers have asked the CWG for better tools to ensure that they weren’t inadvertently providing a platform to people who have been banned from speaking at or attending other events due to code of conduct violations.  While the number of people who have been banned from attending DrupalCon and other Drupal events is very small, a comprehensive list of the identities of those individuals is currently known only to the CWG and the Drupal Association.

While the CWG does not generally publish the names of individuals who have been asked not to attend Drupal events, we do reserve the right to publish their names and the reasons for their ban if they do not abide by it.  While we believe that this is effective at deterring individuals from attending events they have been banned from, we also understand that it does not always provide other attendees and/or conference organizers with the tools they need to ensure a safe environment at their events.

Members of the CWG have discussed this issue with their counterparts in other communities, and it does not appear that there are consistently established best practices for handling these kinds of situations, particularly in communities as decentralized as Drupal. With the input of the community, we would like to establish clear and consistent guidelines for local event organizers.  

Community Workshops and Training

In 2016, the CWG conducted a survey and interviews of Drupal core contributors to identify sources of frustration during the Drupal 8 development cycle. One of our recommendations was for the project to focus more on developing skills like creative problem solving, conflict resolution, effective advocacy, and visioning in order to broaden understanding of Drupal’s community, its assets and its challenges.

Following the success of the teamwork and leadership workshop that the CWG led in collaboration with the Drupal Association at DrupalCon Nashville in 2018, the CWG is exploring opportunities for additional workshops and training at DrupalCon Seattle and other events.

Summary

Over the past few years, the Drupal project and community has grown rapidly, bringing a series of new and evolving challenges. Not only has the project grown progressively more complex with each major release, but the time between releases has increased and more is being asked of the developer community by customers and end-users.

We believe this is a significant contributing factor in the increase in the number of documented incidents of negative conflict, which left unaddressed may result in a decline in contributor productivity and morale. The work of the Community Working Group seeks not only to mitigate the impact of negative conflict, but also to provide the community with the tools and resources it needs to make the Drupal project a safer, more welcoming, and inclusive place.

Mar 17 2018
Mar 17

The Drupal Community Working Group, in partnership with the Drupal Association, is very excited to offer a special workshop at DrupalCon Nashville designed to explore leadership, followership, and teamwork as it applies to various roles in our community.

One of the most remarkable things about open source projects like Drupal is that they enable people from all over to come together and collaborate with others toward shared goals. In order to be successful, open source projects need to continually work toward building positive, supportive communities that enable everyone to be at their best. If you are someone who has, or is ready for a position of responsibility within Drupal (e.g., camp and group organizers, initiative leads, sprint mentors, module maintainers, etc.), we encourage you to attend.

This free event will be facilitated by incoming Drupal Association board chair Adam Goodman, who is also the head of Northwestern University’s Center for Leadership, and works as an executive coach and advisor to senior executives and boards of directors at dozens of companies and organizations around the world. A number of other community members, including Donna Benjamin, Shyamala Rajaram, Gábor Hojtsy, Mike Anello, George DeMet, Tiffany Farriss, and Jordana Fung will also be helping to co-facilitate.

The Teamwork and Leadership Workshop will feature a large group exercise about common assumptions and myths regarding teamwork and leadership, discussion of some best practices for effective leadership and teamwork today, and small group sessions where people can link those concepts with their own experiences within the Drupal community.

The workshop will be held from 2-5pm on Tuesday, April 10, and you can register now at: https://goo.gl/forms/7SWzVS4qhHqbiRrW2. Space is limited, so don’t delay.

We hope to see you there!

Mar 17 2018
Mar 17

The Drupal Community Working Group, in partnership with the Drupal Association, is very excited to offer a special workshop at DrupalCon Nashville designed to explore leadership, followership, and teamwork as it applies to various roles in our community.

One of the most remarkable things about open source projects like Drupal is that they enable people from all over to come together and collaborate with others toward shared goals. In order to be successful, open source projects need to continually work toward building positive, supportive communities that enable everyone to be at their best. If you are someone who has, or is ready for a position of responsibility within Drupal (e.g., camp and group organizers, initiative leads, sprint mentors, module maintainers, etc.), we encourage you to attend.

This free event will be facilitated by incoming Drupal Association board chair Adam Goodman, who is also the head of Northwestern University’s Center for Leadership, and works as an executive coach and advisor to senior executives and boards of directors at dozens of companies and organizations around the world. A number of other community members, including Donna Benjamin, Shyamala Rajaram, Gábor Hojtsy, Mike Anello, George DeMet, Tiffany Farriss, and Jordana Fung will also be helping to co-facilitate.

The Teamwork and Leadership Workshop will feature a large group exercise about common assumptions and myths regarding teamwork and leadership, discussion of some best practices for effective leadership and teamwork today, and small group sessions where people can link those concepts with their own experiences within the Drupal community.

The workshop will be held from 2-5pm on Tuesday, April 10, and you can register now at: https://goo.gl/forms/7SWzVS4qhHqbiRrW2. Space is limited, so don’t delay.

We hope to see you there!

Nov 29 2017
Nov 29

Introduction

As part of ongoing efforts to improve Drupal’s community governance, the Drupal Community Working Group (CWG) was tasked by the Drupal Association and Dries Buytaert with defining next steps in the process. The CWG solicited volunteers from the Drupal community interested in governance, creating a group of community members to strategize how to involve as many people as possible. This new group then decided to hold public meetings to get feedback on next steps from the community.

The group facilitated a series of meetings in an effort to solicit feedback from a broad range of community members. Meetings were held in Slack, were offered at different times to support differences in timezones, and were facilitated by community members from different regions of the world, including North America, Latin America, and South Asia. The group tried to create a space for as many different people to share their voice as possible (for example, one meeting was held specifically to hear from community members who identify as women).

As noted within this blog post, the goal of these meetings was to solicit actionable feedback from the community and provide results back to project leadership (Dries Buytaert) and the Drupal Association. We strongly encourage community members to read the full transcripts of the meetings, which we have captured below, and provide additional context beyond this summary.

While we felt it was important to distill the meeting transcripts into summaries, we also made a conscious effort to avoid adding personal bias by misrepresenting or distorting the voice of the community members who participated in this activity. Each facilitator, most with a review and voting of priorities from the meeting attendees, defined a set of takeaways from their meeting. Our group has subsequently added our perspective to an executive summary, in which we identify patterns and priorities community members raised. The key takeaways and executive summary are found in subsequent sections.

Our group held a total of 13 meetings, with a total of 102 attendees, representing 56 unique participants (many attendees participated in multiple meetings). Efforts were made to encourage participation from the global community, but we did not request participant demographics to share in this post (which, in hindsight, would have been helpful).

We encourage community members to review the key takeaways and our executive summary below with an independent and critical eye. We also encourage community members to share their perspectives as we continue on this important journey of evolving our community governance.

Executive Summary

The following points are grouped thematically, not by priority, though the members of this group agree that creation of a values statement is the highest priority:

  • A community values statement is needed before making governance changes. This statement should come directly from leadership.
  • Governance should evolve over time to remain sustainable. Consider a group of community members to regularly evaluate our policies, procedures, and governance structure.
  • The Drupal Association, project leadership, and the community need to define the community, its membership, and its boundaries; at the very least for better communication and understanding of intentions and expectations. We need to define the communal roles for users, contributors, and maintainers.
  • The Drupal Association, project leadership, and the community need to clearly define leadership, leadership positions, and the higher standard for those positions.
  • The Drupal Association, project leadership, and the community need to clearly document governance structures, policies, and procedures so that anyone can find and understand them.
  • The Community Working Group and the community need to improve the community code of conduct so that it is clearer and more actionable, particularly with regard to harassment. The Drupal Association should also review the DrupalCon Code of Conduct and its policies for enforcing it. Consider other tools that articulate the responsibilities of community participation like an etiquette guide, and conflict of interest policy.
  • The Community Working Group and the community need to define the areas where community expectations exist (issue queues, camps, Slack, etc.)
  • The Community Working Group and the Drupal Association needs to create  well-defined processes and procedures for when members violate these expectations.
  • Community matters should have escalation points that go to groups, not individuals. Those groups should be representative of our community, but can also include outside experts.
  • The community needs to improve its outreach to smaller local and regional communities around the world in a more structured and consistent way, providing resources that allow them to participate more fully in the global Drupal community with the same communal standards.
  • The Drupal Association, project leadership, and the community should take greater responsibility in setting standards for events that carry the Drupal name.
  • The community should develop a communication strategy around community documentation, dissemination, discoverability, organization, and ease of use for onboarding new community members.
  • The community, project leadership, the Community Working Group, and the Drupal Association) should engage other communities and experts to be informed and identify best practices in governance.

As many of the items discussed in these meetings currently are the responsibility of the Drupal Association and/or project leadership, it is the recommendation of this group that they convene to discuss and process these takeaways, and then provide the community with a clear roadmap for what changes to governance they will take the lead on, and what role the community should play in helping to support those efforts. This roadmap should also be clear about what changes (if any) should be led by the community.

Key Takeaways From Each Meeting

Nikki Stevens / October 2 / Link to full transcript / 11 attendees

  • We need to define what “contributor” means when we talk about “contributor community”
  • We need to figure out where the community is/what its boundaries are.
  • We need a values statement
  • That values statement should include D&I as part of it, not as an addendum.

Adam Bergstein / October 6 / Link to full transcript / 10 attendees

  • It strikes me that having all the information in a single place that is easily digestible would help a lot. I would be tempted to suggest talking with Gabor about his Rocketship thing and if it could be adapted to hold all the info and ongoing issues.
  • It's a personal bugbear of mine that the way we disseminate info across the project is a bit unorganised. Very hard to find anything.
  • I'd love to see drupal.org/community be reworked and owned by a working group
  • What people often seem to devalue is discoverability. Lots of info is out there if you know where to find it. how do you find the things you don’t know exist. Like meetings. Having them all in one place like that would rock.
  • I'm seriously open to having a community communication strategy created and implemented. Just wanted you all to know that. I've asked the team at a minimum to create a blog section on d.o/community so there is one place for community news from groups like CWG.
  • My gut feeling is that we need to surface the current state of governance somewhere in the most clear way possible - then use that as a base to evolve governance to make it clear how a group is “official”.
  • One of my learnings in Vienna is that sometimes, people need the DA or Dries to just name a group so the world knows a group is official and so that group feel empowered. So if this group needs that done, let me know. I don't want to overstep or assume or get in the way … just offering help where I can.
  • I feel that if more people are present here, more perspectives from the community can be heard. Post to general before meeting starts.
  • So, do we need to define Community as wider than DA membership? Does it include businesses etc? Does it include clients? Does it include DA staff? Does it include that Dries guy?
  • Maybe we need to invite people to the meeting? Maybe the WeeklyDrop should have a little announcement about each governance meeting? there's also /r/reddit. Are we reaching out to all our different channels?

David Hernandez / October 7 / Link to full transcript / 8 attendees

  • Define values before governance.
  • Define who we are as a community. What does membership mean?
  • What is the scope of the community?
  • How do you a define groups or individuals that will be involved/appointed?

David Hernandez / October 7/8 / Link to full transcript / 5 attendees

  • Governance needs to evolve over time.
  • What are other orgs doing for evolving governance? We should look beyond open source and/or developer-centric organizations.
  • We should bring it outside help/consultants.
  • There will be some who resent/want to resist input from an outsider/expert while it would lend legitimacy to the process for others. Working with community members is essential.
  • Forming a core group of DA/community/consultant with formal oversight of talks would allay some fears about wasting time talking.

Mike Anello / October 9 / Link to full transcript / 2 attendees

  • There have been discussions in open source communities at the Sustain conference about what makes projects sustainable. These could be good concepts to embrace when evolving our governance structure(s).

George DeMet / October 12 / Link to full transcript / 14 attendees

  • While the community may include anyone who interacts with Drupal in any way, there is a distinction between those who just use Drupal and those who deliberately choose to be a part of it in some way.
  • Understanding the rights and responsibilities that come with being part of the Drupal community is a responsibility that’s shared between various institutions but also relies on how we hold ourselves accountable to each other.
  • Leaders help set expectations by setting and upholding rules in a way that reflects the shared values of the community.
  • Building an inclusive and diverse community requires being able to understand and appreciate those with backgrounds and cultures different from our own.
  • We should support participation by positive people who represent the values of the project. Note: In post-meeting discussion, it was agreed that this point failed to capture an important aspect of the conversation that occurred, which was that we should also not be afraid to reject individuals who persist in engaging in toxic behavior after having received warnings about the negative impact their behavior is having on others.
  • We should avoid a focus on “punishment” for those whose behavior has a negative impact on others, but we need processes and procedures in place to identify and deal with trolls and other bad actors.
  • Governance will need to change and evolve over time as the project and the people involved with it change.

David Hernandez / October 24 / Link to full transcript / 10 attendees

  • CWG needs some path of escalation to a group, not an individual, and that group should be made up of community members.
  • The group of community members should also be qualified to handle these matters. Subject matter experts, experience, etc.
  • The community needs some mechanism by which to know certain problematic community members exist.
  • Camp organizers need a way to vet speakers, volunteers, and attendees.
  • If the DA allows camps to use their financing, the DA should take a greater role ensuring the camps follow a defined standard.
  • There may be value in having a blacklist of known bad actors that is public so the community is aware.
  • Camp organizers should ensure safety at their event, as a requirement, not nice to have.
  • The DA should leverage the licensing of the Drupal trademark to ensure events that use the Drupal name are safe.

Adam Bergstein / October 25 / Link to full transcript / 6 attendees

  • i have seen some etiquette guides that have example interactions.
  • Giving people guidelines on how to give feedback, for example, in the issue queues needs to be right in people’s faces as they are giving that feedback. It helps them do a better job.
  • When you flag someone's post in various ways carefully scripted messages get put up that are designed to encourage positive behavior.
  • We could do more to help onboard new members and provide them with resources to help navigate the community. Other communities have clearer documentation for getting started: https://kubernetes.io/community/ and https://kubernetes.io/docs/tutorials/stateless-application/hello-minikub... I would respectfully suggest a section of d.o really isn't good enough. It needs to be the right messages in the right place throughout our infrastructure.
  • Celebrate success (through recognition system?) when people improve. It's not enough just to tell people off all the time.
  • Who in the community would perform this? it sounds like it would be self-monitored and we would just ask other community members to interact with specific interactions; enhancements to d.o and automation; allow the previous person to mark the reply as "helpful"; My understanding is that would mostly be dev workflow and issue queues.
  • Drupal Association efforts may overlap with governance initiatives. Members should review https://www.drupal.org/drupalorg/roadmap/community-initiatives and https://www.drupal.org/drupalorg/roadmap
  • The worst place on the internet /r/politics puts this above their comment forms "In general, be courteous to others. Attack ideas, not users. Personal insults, shill or troll accusations, hate speech, and other incivility violations can result in a permanent ban." Keep it short and simple.
  • Regarding the issue queue commenting, don't forget the forums. they still exist. So it isn't just an issue commenting concern. gdo too. We should also include other community spaces like Slack, IRC, and in-person events.

Shyamala Rajaram/ October 26 / Link to Full Transcript / 4 attendees

  • The DA or someone helping send experienced contributors to smaller events. Provide grants and scholarships to bring people to more Local events.
  • Importance being placed on local communities and in-person connections.

Fatima Khalid / October 27 / Link to Full Transcript / 7 attendees

  • There’s a fundamental need for a values statement. It’s critical that project leadership put out a strong statement of values. Ideally we’d like to see our values statement include more than one-word descriptors
  • Discussed the equality vs equity comic: `https://images-cdn.9gag.com/photo/ajAerM1_700b_v2.jpg ` We need to define that equity is a value we want to see achieved - this the kind of thing we would like to see in a values statement. We want to see systemic barriers to participation removed. It would help to also define those barriers
  • We want a governance policy:
    • A statement of values (see above)
    • Define the leaders and groups that uphold those values,
    • Define the code of conduct that ensures those values are maintained
    • Define the consequences for not meeting those values through code of conduct violations.
  •  We want a conflict of interest policy
    • Mediation between two parties isn’t always appropriate when there is a big power differential between
    •  individuals or when the issue is problematic actions one person did towards one person or multiple people or actions that affected an entire community.
    • Documentation of who handles what kind of issues
  • We need a model for better communication.
    • We want standards for what people can expect to be communicated, how, and when, because our communication processes are not well-known or well-defined.

Shyamala Rajaram/ October 28 / Link to Full Transcript / 6 attendees

  • Inside out approach (instead of bottom up or top down) and is about looking at what's strong and what works in a community and how to get more of it.
  • Need for Paid  “Community Organiser” roles
  • Toolkits as distributions and collaboration platforms as ways to have connection and sharing of information
  • Common the Drupalers regularly conducting meetups for GTD and code sprints -  starting meetup, code sprints with a slide on Drupal Governance, Code of conduct is a way to create awareness.
  • Recognise that any volunteer tasks are difficult and imperfect. That we need to support volunteers at all times. know that the community cares and we do. More ways to recognize!
  • Look to other processes in similar communities to identify strategies that could work for us" (edited)

Alanna Burke / October 30 / Link to Full Transcript / 6 attendees

  • This was a meeting for women-identified participants only. There were 7 total participants.
  • We need a clear values statement, which should include why this statement is necessary - why not having one is adversely affecting the community and what the purpose is.
  • Instead of worrying about getting the whole community on board, the statement should reflect how things are going forward, full stop.
  • We need a very clear CoC, which should include as much as we possibly can (look at examples like Geek Feminism) (most agreed to this, one did not) to be clear so there is no question what is not allowed and what the consequences will be. Use language like "includes but is not limited to"
  • Implementation details to be worked out later (do you agree to CoC by creating a d.o account? downloading Drupal? etc)
  • It is also important that the CoC not be worded in a way that it can be applied differently to different people. There should be tiered consequences appropriate for the action.
  • We should have some kind of mechanism for changing and improving the governance systems we put in place, so that they don't become stale or malfunction when something comes up. We are a community that practices agile development, so why not extend the process to include our governance? It should be flexible & resilient.
  • Reach out to other communities - what have they dealt with? How? What are gaps and strengths? There must be things that we can learn from other similar communities. Maybe we could start a team to work on this.

Kenny Abarca / November 03, 2017 / Link to Full Transcript / 15 attendees

  • People agreed that Drupal CoC should apply on Drupal Camps and other Drupal events throughout the world.
  • From the above, the conversation went on to discuss the approach and complexity of having it implemented globally and even criteria for defining what a Drupal event is.
  • When organizing Drupal community events, people should be aware that there’s a set of standards that apply and they should commit or at least be aware of them before putting together an event.
  • “Drupal governance should automatically apply to events containing the word Drupal”. Attendees discussed the approach.
  • Involvement of CWG in matters related to Drupal Camps.
  • Attendees discussed Dries ownership of the Drupal trademark and how governance would be applied under those circumstances.
  • Defining guidelines to solve issues at Cons & Camps, who to contact and where to go.
  • There should be some control or moderation over events that get created on groups.drupal.org

Facilitators

Listed alphabetically by Drupal.org username:

Sep 25 2017
Sep 25

These results and analysis were initially presented at the DrupalCon Vienna community summit on September 25, 2017.

Following numerous blog posts, official statements, community discussions, social media interactions, and Slack and IRC conversations over the last few months, there is a clear consensus that it is time for Drupal's community governance to evolve. We need to not only define what governance means to us as a community, but also clarify the roles and responsibilities of those within our community leadership and governance structures. We also need to draw clearer distinctions between the different forms of community, project, and technical governance, and make sure that everyone understands how they interact with and support each other.

Ultimately, this will need to be a collaborative process that involves all stakeholders, including Dries and the Drupal Association (especially where matters of legal and financial responsibility are concerned), but the first step is to create a framework so that the community can participate productively in the process. The question that remains to be answered is what that process will look like.

Results of the Governance Summit Survey

The Drupal Association, with help from Whitney Hess, conducted a Community Governance Summit survey in an effort to gain insight into how the community would like to proceed. 568 people responded to the survey, with most questions receiving between 200-250 responses. The Community Working Group (CWG) was given access to the raw results, which it in turn shared with David Hernandez, Nikki Stevens, and Adam Bergstein, who assisted with the writing of this blog post. We all agreed to keep any personally identifiable information from respondents confidential.

While none of the authors of this blog post were responsible for developing the survey or are trained statisticians, we did our best to analyze the results, which reflected a wide range of opinions and feelings about how the Drupal project and community is governed. While we did not feel the survey results pointed to any clear and actionable next steps, they were consistent with the feedback from the community discussions that were held this spring, which was that the process, in whatever form it takes, needs to be driven by the community.

To that end, we have worked with the Drupal Association to publish the survey data and, most importantly, make this call to action for a truly community-driven process. We are also making a sanitized version of the raw data available for download in OpenDocument format for anyone else to review and perform their own analysis. All comments and other free responses have been removed.

Selected Survey Highlights

  • 62% agreed that a governance summit is needed. Only 8% said definitely “no.”

  • 63% want the summit to be held online, so that members from all regions of our global community could participate.

  • 59% believe the summit should be overseen or facilitated by a professional governance expert, with the majority of write-ins requesting a neutral third-party facilitator not affiliated with the Drupal project or community.

  • Nearly 80% wanted the Drupal Association to provide financial support for the summit, with 36% indicating they would contribute to a crowdfunding campaign to help fund the summit.

  • About ¾ said that clarification of leadership roles and separation of project versus community governance roles should be prioritized at the summit. All of the options listed received the support of more than half of those who provided a response to this question:

    1. Clarification of leadership roles in the Drupal project (76%)

    2. Separation of project vs. community governance roles (73%)

    3. Update codes of conduct (63%)

    4. Overall community management (63%)

    5. More community-elected leadership positions throughout Drupal (60%)

    6. Clarify and update Community Working Group processes and policies (56%)

    7. Create core values statement (53%)

Percentages listed are of those who provided a response to that question, not of the total number of people who responded to the survey.

What’s Next: Getting Involved

Now is the time for people to get involved and drive the next steps in the process. We feel that as an open-source project, the governance of our community should be designed and implemented by members of that community in the most transparent and fair manner possible.

To that end, we feel that the best path forward is to create a volunteer working group that is representative of our global community, and for that group to take the lead in the process of evolving Drupal community governance, rather than any existing group or individual. While the Drupal Association, Community Working Group, and others in the project’s current governance structure are committed to providing whatever support they can to ensure the success of this working group, we feel that the community itself needs to own the process as much as possible.

We, the authors of this blog post, are not the leaders of the process, but as members of the community with interest and experience in various aspects of community governance, we are willing and able to help provide a framework for the group to self-organize and begin work to help improve the governance of our community. We stand ready to participate and help as needed, understanding that while this work will not be quick or easy, it is important and necessary for the long term sustainability of our project and community.

The next step for this is for you to get involved. Here's how to get started:

  • Join the #governance channel on Drupal Slack.

  • Attend a governance meeting in the #governance channel. Once a schedule has been determined we will publicize that information and pin it to the Slack channel. Each of the authors of this post will host at least one meeting and the entire meeting transcript will be made available after the meeting.

    • The goals of these meetings are to connect people who are interested in governance with each other, provide a forum for people to share their thoughts, and empower the community to determine the next steps.

    • We are committed to this being a community-driven process and will be present to facilitate, but not to dictate.

    • If there is interest, we can also host meetings in other forums. (IRC, video chat, etc.)

Other ways to get involved:

  • Write a blog post and share your ideas.

  • We know that people don’t always feel safe sharing their comments and feedback and we don’t yet have a long-term solution for this. In the interim, feel free to directly contact any of the writers of this post, or any member of the Community Working Group to share your thoughts.

We are at a unique inflection point in the history of the Drupal community. We have the opportunity to (once again) provide a shining example to other open source communities demonstrating our forward thinking; not only in technical decisions, but also community ones. Please join us.

Authors (listed alphabetically by Drupal.org username)

Feb 23 2015
Feb 23

In previous posts, we’ve talked about who the Community Working Group (CWG) is and why we’re here, as well some of the work we’ve done around establishing a process for conflict resolution in the Drupal community.

In this post, I’d like to go into more detail about what happens when folks file incident reports with the Community Working Group, and open up the conversation on how we can more effectively address issues that have a larger impact on the Drupal community as a whole.

Currently, the CWG meets once a week over Google Hangout to go through any issues that might have been filed since our last meeting, as well as to discuss ongoing questions and concerns that have been brought to our attention through various channels (reports, individual conversations, etc.) and the overall health of the Drupal community.

As often as possible, we post the minutes of our regular meetings. By necessity, these are somewhat redacted due to the fact that we are often discussing matters of a sensitive nature that have been shared with us in confidence. We also maintain an email list where we discuss ongoing issues and other things that come up in the time between our regular meetings.

When an issue is filed, whether though the Incident Report Form, via e-mail, or in our public issue queue, it goes on the agenda for the next weekly meeting (if the matter is of a serious and immediate nature, CWG members may choose to take immediate action and/or meet outside our normal meeting time). We discuss each item as a group and come to agreement on next steps, then assign someone to follow-up with the individuals in question. If the issue is about something that doesn’t fall within the charter of the CWG, we may refer the matter to another group (e.g., the Technical Working Group or the Licensing Working Group), or reply back to the reporting individual with an explanation.

In cases where there is a dispute between two or more individuals, our general approach is to first gather as much information as possible from all involved parties. In order to ensure that people are able to share their stories with us in an open and honest manner, we do not share any names or other sensitive details outside the group without permission.

Once we have a sufficient level of detail, we meet again as a group to decide how to proceed. Depending on the situation, this may involve one or more CWG members providing mediation between the parties in conflict or suggesting ways that they can resolve the issue themselves. In cases where there is a clear Code of Conduct violation, we will talk directly to the person or persons who engaged in the violation to help them understand the impact of their words and/or actions and to take responsibility for them.

In some cases, we may receive an after-the-fact report about a situation that has already been resolved. In those cases, we review the incident, decide whether further action is necessary, and keep it on file for reference in case something similar happens in the future.

If this sounds long and drawn out, that’s intentional. Unless an issue requires immediate action, our process is designed to enable resolutions that are as thoughtful and permanent as possible. The Community Working Group is not the “Drupal police” and our role is not about deciding “who’s right” and “who’s wrong” in a given situation so much as it is about helping people in our community work together in a mutually respectful way. While many of the items that we tackle are initiated by issues that are reported to us, our process is not exclusively complaint-driven.

The people who volunteer their time serving on the Community Working Group are people with backgrounds in community leadership and conflict resolution who all have been working in the Drupal community for years. We believe that a culture that encourages healthy debate and disagreement is a big part of what gives the Drupal project and community its strength. What we are primarily concerned about are destructive conflicts that violate our shared community values and make the Drupal community a less welcoming place for everyone.

To that end, we’re looking for the community to help us shape our process for addressing systematic patterns of disruptive behaviours that have an impact that goes beyond just those individuals who are directly involved. Please read our proposal and give us your thoughts in the comments section. You can also share your thoughts privately by e-mailing us at drupal-cwg [at] drupal.org.

Thanks!

Jul 07 2014
Jul 07
webchick's picture

An alternative is the drupal-cwg [at] drupal.org email address, as documented on https://www.drupal.org/governance/community-working-group.

We chose to use Google Forms because a wide variety of people about whom conflicts may occur have very high-level access to Drupal.org. A neutral third-party service doesn't have this problem, although I totally get why some have ToS concerns with it.

DamienMcKenna's picture

Could we please have that email address added to the top of the Incident Report form, just to make it obvious for people? Thanks!

kattekrab's picture

I've edited the form and updated the issue.

https://www.drupal.org/node/2299737#comment-8950891

Would be good to get some sanity check eyeballs on it though!

Thanks all!
@gaele - for raising the question
@DamienMcKenna - for the suggestions.
@webchick - for adding to the queue.

jhodgdon's picture

You asked for "sanity check eyballs" on https://www.drupal.org/governance/community-working-group/incident-report

I have a few comments:

a) There is a very large wall of text at the top. Maybe it could be organized into bullets or sections or something? [see below]

b) You might also want to take a look at the descriptions for the Who/What etc. questions. They are a bit repetitive.

c) The "Who" question also has a mix of questions (ending in ?) and ... sort-of questions (ending in .) which turned me off.

d) "Please include links or quoted text if relevant." is under "where". Um... I think that would be under "what"? At least the "quoted text" sounds like a "what" not a "where"? It's kind of confusing what the distinction is.

So... Here's my suggestion for the top. Items in [] are my notes on the edits.

The community working group (CWG) upholds the Drupal Code of Conduct (DCOC). See:
- https://drupal.org/governance/community-working-group
- https://drupal.org/dcoc

[made this a bullet list]

Reporting incidents to the CWG

[header added]

This form can be used to report incidents that may breach the code of conduct, or to report non-code, non-technical issues that can't be resolved between members of the community.

Alternatively, you may email the CWG directly: [email protected]
Please make sure to include as much information as you can by answering the questions in the form in your email. [note: small edit in this sentence]

Incidents to report elsewhere

[added header, and this information came from elsewhere on the page]
IMPORTANT: If you are in any kind of immediate physical danger, please contact your local authorities.

Technical disputes should be raised with the Technical Working Group. Personal disputes that have arisen out of technical issues can be brought to the CWG.

https://drupal.org/governance/technical-working-group

Notes about incident reports

[added header, and the information here elsewhere on the page]
We hope you've tried to resolve issues between yourselves. If that failed, we hope that you reached out to fellow friends and colleagues in the community to help mediate your dispute. This form should only be used when those steps did not lead to resolution.

These incident reports are shared with the immediate members of the Drupal Community Working Group and are kept confidential. In some cases we may decide it necessary to make a public statement. In that case, the identities of all involved will remain confidential unless there are strong reasons, or mutual agreement they should be revealed.

Builder of Drupal sites and modules, and Drupal tutor - http://poplarware.com
Drupal Core maintainer for documentation

kattekrab's picture

Thanks Jennifer - really useful review and patch.

Going to paste this into the issue https://www.drupal.org/node/2299737

Let's see if we can tighten up the wording around those questions too.

Patrícia Jyotsna's picture

Hi, I heard about Drupal is now a growing community and knowing that the mentored sprints was attended by many to listen to tools presentation is such a very successful one. In relevance to this, I am with you to say that we must be aware in keeping our shared principles and values in mind when interacting with others to be able to attain an inspiring event like the Drupal sprints at Amsterdam.

Jul 07 2014
Jul 07
webchick's picture

An alternative is the drupal-cwg [at] drupal.org email address, as documented on https://www.drupal.org/governance/community-working-group.

We chose to use Google Forms because a wide variety of people about whom conflicts may occur have very high-level access to Drupal.org. A neutral third-party service doesn't have this problem, although I totally get why some have ToS concerns with it.

DamienMcKenna's picture

Could we please have that email address added to the top of the Incident Report form, just to make it obvious for people? Thanks!

kattekrab's picture

I've edited the form and updated the issue.

https://www.drupal.org/node/2299737#comment-8950891

Would be good to get some sanity check eyeballs on it though!

Thanks all!
@gaele - for raising the question
@DamienMcKenna - for the suggestions.
@webchick - for adding to the queue.

jhodgdon's picture

You asked for "sanity check eyballs" on https://www.drupal.org/governance/community-working-group/incident-report

I have a few comments:

a) There is a very large wall of text at the top. Maybe it could be organized into bullets or sections or something? [see below]

b) You might also want to take a look at the descriptions for the Who/What etc. questions. They are a bit repetitive.

c) The "Who" question also has a mix of questions (ending in ?) and ... sort-of questions (ending in .) which turned me off.

d) "Please include links or quoted text if relevant." is under "where". Um... I think that would be under "what"? At least the "quoted text" sounds like a "what" not a "where"? It's kind of confusing what the distinction is.

So... Here's my suggestion for the top. Items in [] are my notes on the edits.

The community working group (CWG) upholds the Drupal Code of Conduct (DCOC). See:
- https://drupal.org/governance/community-working-group
- https://drupal.org/dcoc

[made this a bullet list]

Reporting incidents to the CWG

[header added]

This form can be used to report incidents that may breach the code of conduct, or to report non-code, non-technical issues that can't be resolved between members of the community.

Alternatively, you may email the CWG directly: [email protected]
Please make sure to include as much information as you can by answering the questions in the form in your email. [note: small edit in this sentence]

Incidents to report elsewhere

[added header, and this information came from elsewhere on the page]
IMPORTANT: If you are in any kind of immediate physical danger, please contact your local authorities.

Technical disputes should be raised with the Technical Working Group. Personal disputes that have arisen out of technical issues can be brought to the CWG.

https://drupal.org/governance/technical-working-group

Notes about incident reports

[added header, and the information here elsewhere on the page]
We hope you've tried to resolve issues between yourselves. If that failed, we hope that you reached out to fellow friends and colleagues in the community to help mediate your dispute. This form should only be used when those steps did not lead to resolution.

These incident reports are shared with the immediate members of the Drupal Community Working Group and are kept confidential. In some cases we may decide it necessary to make a public statement. In that case, the identities of all involved will remain confidential unless there are strong reasons, or mutual agreement they should be revealed.

Builder of Drupal sites and modules, and Drupal tutor - http://poplarware.com
Drupal Core maintainer for documentation

kattekrab's picture

Thanks Jennifer - really useful review and patch.

Going to paste this into the issue https://www.drupal.org/node/2299737

Let's see if we can tighten up the wording around those questions too.

Patrícia Jyotsna's picture

Hi, I heard about Drupal is now a growing community and knowing that the mentored sprints was attended by many to listen to tools presentation is such a very successful one. In relevance to this, I am with you to say that we must be aware in keeping our shared principles and values in mind when interacting with others to be able to attain an inspiring event like the Drupal sprints at Amsterdam.

Jul 26 2013
Jul 26

The Drupal.org Content Working Group (DCWG) is one of the groups recently chartered by the Drupal Association as part of its ongoing governance initiative for Drupal.org.

The mission of DCWG, as outlined in our charter (https://drupal.org/node/2001502), is, “to make sure that the content on Drupal.org websites is compelling, well-curated, and relevant for all of its various target audiences and supports a content marketing strategy that serves site visitors and generates revenue to make Drupal.org sustainable.”

From a practical standpoint, this means that DCWG in collaboration with the community and the Drupal Association will develop, manage, and maintain the overall content strategy for Drupal.org and its associated sites, define policies to support that strategy, and oversee the look-and-feel and voice of the website.

The group meets monthly and provides regular reports on its activities to both the Drupal Association board and the community at large. The notes and minutes from our meetings are posted at https://drupal.org/node/2001514

The current members of DCWG are:

For the remainder of 2013, the group’s initial focus will be:

  • Identify the primary audiences for Drupal.org and their content needs
  • Develop a landing page concept to aggregate and link to content specific to each audience
  • Help define some of the policies that govern content and users on Drupal.org.

As we move forward into 2014, DCWG will work on developing a comprehensive and long-term content strategy, design system, and information architecture for Drupal.org. This will be a large project, and will undoubtedly involve greater community participation.

Please don’t hesitate to let us know if you have any questions or comments. In addition to contacting us directly, you can also flag issues for us in the Drupal.org content issue queue (https://drupal.org/project/issues/content) and some of us are occasionally available on IRC in #drupalorg.

Jun 04 2012
Jun 04

Here's the revised draft of the DrupalCon Code of Conduct based on community feedback and input to the original draft. Please offer your comments, questions, and suggestions below.

In order to ensure that everyone has the opportunity to provide feedback, we'll be leaving comments open through at least 12pm (noon) Central US Time on June 11. If no significant changes are required, the finalized draft could be presented to the Drupal Association as early as June 12, but if we need to make additional changes, then the timeline will be extended as necessary to ensure that as many people as possible can participate in the process and that all voices are heard.

In addition to all of the folks who have helped with the development of the code so far and everyone who participated in the discussion online, I also want to publicly thank a few individuals who provided information and context that was particularly helpful in the development of this version of the draft: MortenDK, Paul Johnson, Jeff Eaton, Donna Benjamin, and Tiffany Farriss.

I understand that we're dealing with some difficult issues that have a very personal impact on many people; I would ask those of you participating in the discussion to please continue to keep an open mind and consider the perspectives and experiences of others. As always, if you have any comments, questions, or perspectives that you'd like to share privately, please feel free to reach out to me directly or on Twitter (@gdemet).

Thanks!

DrupalCon brings together people from around the world who use, develop, design, and support the Drupal platform. Many attendees at DrupalCon are newcomers evaluating both our platform and our community.

The Drupal Code of Conduct (http://drupal.org/dcoc) outlines our shared ideals and values. This document expresses how we hope to make these ideals real at our conferences and other events. Our goal is to ensure that all participants can freely and openly share ideas in a friendly, safe, and welcoming environment that encourages and inspires mutual respect and collaboration.

Come for the software, stay for the community.

Drupal would simply not exist without its community. We want all attendees at DrupalCon to have an awesome experience, both in and out of formal conference sessions.

The purpose of this document is not to restrict the diversity of ideas and expression in the Drupal community; rather, it's to raise awareness of the potential for actions that could alienate valuable members — and potential members — of the community.

Be considerate.

DrupalCon is an international event that attracts diverse people from a wide variety of ethnic, cultural, and religious backgrounds. We acknowledge that cross-cultural communication can often be complicated and encourage everyone to consider both the impact of their actions on those with different backgrounds and experiences and the honest intentions of those who may have unknowingly caused offense.

Be welcoming.

One of the greatest strengths of the Drupal community is our inclusiveness. Making all attendees feel welcome and included at DrupalCon is everyone’s job, including exhibitors and sponsors. If you are sponsoring DrupalCon and have questions or concerns about working with our community, please reach out to Sales & Business Development Director Megan Sanicki [contact info]

Be respectful.

Sponsors, volunteers, speakers, attendees, and other participants should strive to treat all people with dignity and respect, regardless of their culture, religion, physical appearance, disability, race, ethnicity, gender, or sexual orientation.

Be collaborative.

If and when misunderstandings occur, we encourage people to work things out between themselves whenever possible. People are encouraged to take responsibility for their words and actions and listen to constructively-presented criticism with an open mind, courtesy, and respect.

When we disagree, we consult others.

If people are unable to work out issues between themselves, they are encouraged to seek the advice of a mutually trusted third party or a designated community volunteer [contact info] to help mediate.

When we need it, we ask for help.

We do not tolerate harassment of conference participants in any form. If you feel threatened or violated as a result of intimidating, harassing, abusive, discriminatory, derogatory or demeaning conduct, please immediately notify a conference staff member. Likewise, please immediately notify a staff member if you notice that someone else is being subjected to such behavior.

If the matter is especially urgent, please call/contact any of these individuals:
[DrupalCon Staff Member]
[DrupalCon Staff Member]
[DrupalCon Staff Member]
[Community volunteer]

The DrupalCon team wants everyone to feel safe for the duration of the conference. If necessary, conference staff are empowered to take appropriate actions that may include, but are not limited to, warnings, expulsion from the conference without refund, and referrals to venue security or local law enforcement.

We’re all in this together

Thanks for making DrupalCon awesome for everyone!

The DrupalCon Code of Conduct is licensed under a Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by-sa/3.0/) and is available for others to use and adapt for their own events.

Jul 15 2011
Jul 15

If you have been around the Drupal community for any length of time you have probably heard of the Drupal Association. What you may not be aware of is the myriad ways in which the Association helps foster and support the growth of Drupal, both as a software project and a community

The Association funds the ongoing support and maintenance of Drupal.org, the website that’s home to the Drupal project and community. It also helps organize and support Drupal events around the world. In the United States, the Drupal Association partners with DrupalCon, Inc., a non-profit that organizes the annual North American DrupalCon and provides fiscal agency and insurance for DrupalCamps and other local events.

The Association also funds and supports other projects that are too large for community volunteers to handle on their own, but essential to the growth of Drupal. Recent examples include the Drupal.org redesign and migration to the Git version control system.

Finally, the Association protects the Drupal project and community through legal work and advocacy, and helps promote it through marketing and promotion efforts. Although the Association is dedicated to protecting Drupal’s source code, it does not play any role in the development or direction of the software itself.

The Association has grown tremendously since its humble beginnings only four years ago. Originally created to help raise funds to support the Drupal.org site infrastructure, the Drupal Association today is a large international organization that boasts hundreds of members from around the globe.

The Association is run by a General Assembly of 34 Permanent Members who are responsible for electing a board from among its membership. The current board consists of nine members led by President Dries Buytaert, the founding developer of the Drupal project. The General Assembly is also responsible for adding new Permanent Members to its ranks on an annual basis. While only members of the board vote on resolutions, the entire General Assembly takes part in the debate and monitors all board activities. The board is responsible for everything from approving spending decisions to deciding the location of the next DrupalCon.

Within the last year, the Association also added several full-time paid staff members to help out with its ever-increasing responsibilities. Executive Director Jacob Redding is responsible for the execution of all Association initiatives. Events Manager Neil Kent oversees the logistics of DrupalCon and other events. Sponsor Wrangler Megan Sanicki works with companies and organizations to help provide revenue for the Association. The Association also employs several part time staff members who assist with office management and marketing.

In 2010, the Association focused on several key initiatives. These included the completion of the Drupal.org redesign project, continuing to build a sustainable model for DrupalCons, improving internal processes and decision-making, hiring permanent staff members, and improving the technical infrastructure of Drupal.org. At DrupalCon Chicago, the Association’s General Assembly will meet to discuss its priorities for 2011.

Ensuring the success of DrupalCon is one of the Association’s biggest ongoing commitments to the community. Over the last five years, DrupalCon has grown from a small informal event that brought together a few dozen Drupal developers to a semi-annual international conference that attracts thousands of attendees. Each one of these semi-annual events requires thousands of hours of work as well as coordination with conference organizers and regional teams, vendors, sponsors, speakers, and venue personnel, just to name a few. In recent years, the Association has dedicated itself to making DrupalCon a more sustainable event as it looks toward expansion into areas of the world other than Europe and North America.

Much of the work that the Association does happens behind the scenes, but the results benefit the entire Drupal community. As Drupal continues to grow and evolve, the Association will grow and evolve right alongside it, continuing to help both the community and the project to flourish.

Apr 19 2010
Apr 19

The DrupalCon European organizing group and the Danish Drupal Community is pleased to invite everyone to register for DrupalCon Copenhagen, which will be held at the world-famous Bella Center August 23rd to 27th, 2010.

For the next three days (through April 21st), you can take advantage of the special DrupalCon to DrupalCon price for 249€ including lunches and snacks! Register now to guarantee your place at the premier event of the Drupal community. DrupalCon Copenhagen will feature three full days of sessions from the best and brightest in the Drupal community. The session days will be bookended by code sprints and professional Drupal training sessions.

Copenhagen is a world-class city full of wonderful cuisine and culture. We have arranged for special pricing at hotels and hostels and of course there will be plenty of parties!

The price for early-bird tickets will go up to 279€ on Thursday, April 22nd. All tickets are subject to Danish VAT.

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web