As discussed in 2017-2018 report → , our community faces a challenge in figuring out how to best handle individuals that have been banned from various Drupal community events and spaces:
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.
At the current time, the CWG does not have a policy in place for dealing with banned individuals on an ongoing basis. In fact, at the current time, there is no single document maintained by the CWG that acts as a "banned list". We have been handling situations involving banned individuals on a case-by-case basis, but we feel a clear, fair, and published policy for our community is the right thing to do moving forward.
Over the past year, CWG members have had informal conversations with Drupal community members, representatives from other open-source communities, and others in an effort to solicit suggestions on how to best proceed. To date, no clear solution has presented itself. The goal of posting this issue is to share our thoughts on this issue to date and to get input from the community-at-large.
We, as a community, need to balance several factors including:
We believe that with any solution, the sensitive nature of a "banned individuals" list will likely require a number of processes around it:
Figuring out how manage access to the list is particularly tricky. Some thoughts:
Over the past year, the Community Working Group members have wrestled with just about everything associated with this topic. We are fully aware that the path to a solution is difficult at best, but we strongly feel that the helping to protect the safety of our community members requires us to explore every available option.
We, as a community, once again have the opportunity to be a leader among open-source projects in being proactive with a difficult situation. We are aware that this can be an uncomfortable and hard topic, and while we have been discussing it internally for a significant amount of time, we feel that it is important to gain as much perspective as possible before proposing any new policies or procedures. We look forward to the discussion!
Those who are not comfortable sharing their thoughts in a public forum are welcome to email us at drupal-cwg@drupal.org.
Closed: works as designed
Policies
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Closing out this old issue. To summarize, the CWG does not maintain a list of individuals who have been banned from events, instead situations involving banned individuals are handled on a case-by-case basis. If you are an event organizer and are concerned that someone who is scheduled to attend or speak at your event might be doing so in violation of a ban, you are welcome to reach out to the CWG for guidance.