Add a mention to the Contributor Covenant document to the README.txt file.

Contributor Covenant - http://contributor-covenant.org

CommentFileSizeAuthor
#10 metatag-n2613598-10.patch2.51 KBDamienMcKenna
#3 metatag-n2613598-3.patch2.48 KBDamienMcKenna
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

DamienMcKenna created an issue. See original summary.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Issue summary: View changes
DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Status: Active » Needs review
FileSize
metatag-n2613598-3.patch2.48 KB

This should suffice. FYI I wrapped the file at char 80 to match the d.o coding standards.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Status: Needs review » Fixed

Committed.

  • DamienMcKenna committed 18e4e96 on 7.x-1.x 
    Issue #2613598 by DamienMcKenna: Added a copy of the Contributor...
DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented

Note: this actually adds the code of conduct file to the repository, rather than just a mention in the readme.txt file.

kreynen’s picture

kreynen CreditAttribution: kreynen at University of Colorado Boulder commented

Did you run this by anyone before adding it to the project? I'm not sure which working group this falls under, but I'm going to open an issue in https://www.drupal.org/project/issues/drupal_lwg initially to discuss. Drupal already has https://www.drupal.org/dcoc and https://www.drupal.org/node/1001544 which govern the behavior on Drupal.org and Drupal events as well what users agree to when they are given access to commit code. While I personally don't object to anything in http://cgit.drupalcode.org/metatag/tree/CODE_OF_CONDUCT.txt, this is a slippery slope.

I don't think it's a great idea to allow every project on Drupal.org to create their own codes of conduct that are anything other than the DCoC. If we allow anything that is more or less restrictive or even a different process for resolving issues, we are really opening ourselves up to a lot of headaches.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett at Acquia commented

See #2681277-11: Stance on projects that require a CLA (Contributor License Agreement). This file makes promises that are not enforceable by the maintainer.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Status: Closed (fixed) » Needs review
FileSize
metatag-n2613598-10.patch2.51 KB

I guess I jumped the gun a bit.

Dave Reid’s picture

Dave Reid
he/him
Primary language English
Location Nebraska USA
CreditAttribution: Dave Reid as a volunteer commented
Status: Needs review » Reviewed & tested by the community

Yeah, I'm not really ok with any Drupal.org project using the contributor covenant. I'd rather rely on our existing code of conduct and improve it where needed.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Status: Reviewed & tested by the community » Fixed

Committed.

  • DamienMcKenna committed 6a7ce62 on 7.x-1.x 
    Issue #2613598 by DamienMcKenna: Removed the Contributor Covenant,...
tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett at Acquia commented

For the record, I am very pro-CoC. Just wanted to be clear about which one we use, and be sure it remains actionable.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.