Problem/Motivation
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 https://www.drupal.org/dcoc (as opposed to the DrupalCon Code of Conduct) because someone contributing would have to do so through drupal.org anyway (i.e.: not necessarily DrupalCon).
Remaining tasks
Write a patch- Review and feedback
- RTBC and feedback
- Commit
- Discuss how to backport to 7.x
User interface changes
None.
API changes
None.
Data model changes
None.
Comment | File | Size | Author |
---|---|---|---|
#24 | 2886297-24-add-code_of_conduct-txt.patch | 5.73 KB | impalash |
#21 | 2886297-21-add-code_of_conduct-txt.patch | 5.58 KB | impalash |
#20 | 2886297-20-add-code_of_conduct-txt.patch | 5.47 KB | impalash |
#18 | 2886297-18-add-code_of_conduct-txt.patch | 231.53 KB | impalash |
#4 | 2886297-4-add-code_of_conduct-txt.patch | 5.93 KB | mparker17 |
Comments
Comment #2
mparker17Here's a patch for the
8.4.x
branch. Reviews welcome!Comment #3
aburke626I 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?
Comment #4
mparker17@aburke626, great idea! Here's an updated patch.
Comment #5
gddGiven that this is already required for contributing, it makes sense to codify it in the codebase as well. +1
Comment #6
aburke626This looks great! Thanks for taking this on.
Comment #7
aburke626Comment #8
davidhernandezThis sounds like something that would need to go through project governance (ie. Dries' approval) so tagging.
Comment #9
cilefen CreditAttribution: cilefen commentedCan we not simply link to the CoC URL in order to reduce the maintenance burden (i.e. "forgetting to update") the file in code?
Comment #10
ultimikeWe (the CWG) discussed this at our meeting today and have some thoughts/action items (for us):
Thanks for making this happen!
-mike
Comment #11
David_Rothstein CreditAttribution: David_Rothstein as a volunteer commentedNice idea, but:
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 drupal.org -- but also suggest that there be a brief introductory paragraph before the link that explains what the Code of Conduct actually is.
Comment #12
mgifford1) Nothing says that the DA can't dual license that baby David. :)
2) So "For more information, please see https://www.drupal.org/dcoc" to "To see the latest version always see https://www.drupal.org/dcoc"
3) Like the idea of an intro paragraph. Maybe something like:
"Drupal is community driven software. The community is:
- online on Drupal.org (and affiliated groups);
- in forums like https://drupal.stackexchange.com;
- 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 Drupal.org than it is to get them in Core. Let's include the text so it is there for folks to grep into.
Comment #13
David_Rothstein CreditAttribution: David_Rothstein as a volunteer commentedI like that suggested intro paragraph.
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.
Comment #14
davidhernandezI 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.
Comment #15
gdemetThe 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 Drupal.org. The advantage of the latter approach is that it would always point to the definitive version of the CoC.
Comment #18
impalash CreditAttribution: impalash commentedAdded for 8.6.x
Comment #19
borisson_#18 looks like it includes a lot of things that are not related to this issue.
Comment #20
impalash CreditAttribution: impalash commentedFixed.
Comment #21
impalash CreditAttribution: impalash commentedissue fixed properly
@borisson_ please review.
Comment #22
impalash CreditAttribution: impalash commentedComment #23
borisson_There is a stray space here. Otherwise this looks solid.
Comment #24
impalash CreditAttribution: impalash at Google Summer of Code commentedStray space removed.
Comment #25
borisson_Looks solid.
Comment #26
David_Rothstein CreditAttribution: David_Rothstein as a volunteer commentedThis looks like the exact same patch as before, so none of the questions regarding licensing/etc. from above have been addressed.
Comment #27
xjmRemoving the novice tag since this is a governance issue. Probably this should also live in a different queue as it is not a core issue at present?
Comment #29
Amber Himes MatzWhich queue should this be moved to? What is the preferred method for moving an issue to another queue?
Comment #30
Amber Himes MatzIt looks like Drupal's CoC (https://www.drupal.org/dcoc) may have been based on v1 of Ubuntu's CoC. Ubuntu now has v2, which includes the text from v1, plus quite a bit more. Link: https://www.ubuntu.com/community/code-of-conduct. Version 2 is licensed under Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) - https://creativecommons.org/licenses/by-sa/3.0/.
So, to resolve the licensing question, could we add the CC license to CODE_OF_CONDUCT.txt, state how ours was modified, and clarify credit to Ubuntu as v2 of their CoC?
Comment #31
rachel_norfolkI believe the CWG intend to lead an initiative updating the Drupal Community Code of Conduct. It makes sense to me to then include it in our code.
If you are looking for a place to move this, maybe into their project, https://www.drupal.org/project/issues/drupal_cwg ?
Comment #32
gdemetI've gone ahead and moved this into the CWG queue; in the meantime, we'd suggest the patch just include the intro text and a link to the current CoC as discussed in #15 above. If this is not workable for any reason, let's discuss!