Github recently added new community tools which lints projects for their own open-source community recommendations, one of which is to "add a CODE_OF_CONDUCT file in your repository".

Proposed resolution

Add a core/CODE_OF_CONDUCT.txt to Drupal's repository, with the contents of Drupal's code of conduct.

I suggest putting it in whichever folder holds MAINTAINERS.txt (i.e.: another piece of documentation you'd probably want to read if you wanted to interact with the Drupal community). In Drupal 8, MAINTAINERS.txt is in the core sub-directory; in Drupal 7 MAINTAINERS.txt is in the root folder.

I suggest we make it a .txt (as opposed to a markdown document / .md) to be consistent with other documentation in that directory.

I suggest we use the text from (as opposed to the DrupalCon Code of Conduct) because someone contributing would have to do so through anyway (i.e.: not necessarily DrupalCon).

Remaining tasks

  1. Write a patch
  2. Review and feedback
  3. RTBC and feedback
  4. Commit
  5. Discuss how to backport to 7.x

User interface changes


API changes


Data model changes


Members fund testing for the Drupal project. Drupal Association Learn more


mparker17 created an issue. See original summary.

mparker17’s picture

Assigned: mparker17 » Unassigned
Issue summary: View changes
Status: Active » Needs review
5.87 KB

Here's a patch for the 8.4.x branch. Reviews welcome!

aburke626’s picture

I think this is great - one suggestion - should we add a link to the existing CoC in the text, in case it changes before this can be updated/people want to find it/etc?

mparker17’s picture

@aburke626, great idea! Here's an updated patch.

gdd’s picture

Given that this is already required for contributing, it makes sense to codify it in the codebase as well. +1

aburke626’s picture

This looks great! Thanks for taking this on.

aburke626’s picture

Status: Needs review » Reviewed & tested by the community
davidhernandez’s picture

Issue tags: +Project governance

This sounds like something that would need to go through project governance (ie. Dries' approval) so tagging.

cilefen’s picture

Can we not simply link to the CoC URL in order to reduce the maintenance burden (i.e. "forgetting to update") the file in code?

ultimike’s picture

We (the CWG) discussed this at our meeting today and have some thoughts/action items (for us):

  • We think having the text, not just a link, in the codebase is a good idea.
  • Once this is committed, we'll add some language to to mention that the CoC text is included as part of Drupal core (this will also help us to remember to keep it up-to-date in both places).
  • We will volunteer to ensure it stays up-to-date in code (with patches) as necessary.

Thanks for making this happen!


David_Rothstein’s picture

Status: Reviewed & tested by the community » Needs review
Issue tags: +needs backport to D7

Nice idea, but:

  1. I hate to bring this up, but are there licensing issues with including this text directly? Content on is under a Create Commons license which as far as I know is not compatible with the GPL. So would it be necessary to get all the authors to agree to relicense it under the GPL?
  2. Even if people remember to patch core when the Code of Conduct changes, that doesn't change the fact that outdated versions will still be included in older releases. So at an absolute minimum, I think the text here would need to make clear that isn't just where you go to find "more information", it's where you go to find the current up-to-date version.
  3. There is nothing in here that explains who the Code of Conduct is for or where it applies. That is of course more of a flaw with the Code of Conduct itself, but where it's relevant here is that just because someone has a copy of the Drupal software and is using it doesn't mean this "code of conduct" is relevant to them in any way.

To address all three of those points, I agree with @cilefen's idea of simply having this file link to the Code of Conduct on -- but also suggest that there be a brief introductory paragraph before the link that explains what the Code of Conduct actually is.

mgifford’s picture

1) Nothing says that the DA can't dual license that baby David. :)

2) So "For more information, please see" to "To see the latest version always see"

3) Like the idea of an intro paragraph. Maybe something like:

"Drupal is community driven software. The community is:
- online on (and affiliated groups);
- in forums like;
- in communities like Minneapolis, London & Sydney that host Drupal community events; and
- at DrupalCon.

It is only through efforts of thousands of people around the world that the software for Drupal gets developed, improved and implemented. Because community is at the core of Drupal, we want to include the Code of Conduct in the repository."

Not sure the Code of Conduct changes all that often. Really, in my experience it's harder to get changes to the content on than it is to get them in Core. Let's include the text so it is there for folks to grep into.

David_Rothstein’s picture

I like that suggested intro paragraph.

1) Nothing says that the DA can't dual license that baby David. :)

I don't think the DA is the copyright holder, though. Like I said above, I think it would be up to all the individual people who authored it (which includes the Ubuntu folks). I assume most would be willing if asked though.

davidhernandez’s picture

I think it makes sense to be explicit about who it applies to in the file; specifically that it does not apply to users of the software.

gdemet’s picture

The licensing question is a good one. While I'm sure we would have no problem getting those involved in the authorship of the existing Drupal CoC to agree to dual-license, much of the original language is based on the Ubuntu Code of Conduct, which does not appear to be available under a GPL-compatible license.

We could either reach out to the folks at Ubuntu to see if they'd be willing to dual-license for us, or we could just include a file with the intro text and a link to the page on The advantage of the latter approach is that it would always point to the definitive version of the CoC.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.