The DrupalCon Code of Conduct was updated over Winter 2017/2018 using a series of Google Docs but this is not a sustainable process moving forward and does not allow for attribution of the work does by many members offer Community.
This issue will update this project with a markdown version of the DrupalCon CoC as it is now published and allow for all those that took part in the updates to log their work on this issue, so can be given commit credit.
Please add a comment saying that you worked on the Google Doc version of the DrupalCon Code of Conduct for 2018 and I will commit this change to 7.x-2.0 at the end of DrupalCon Nashville during the Friday Sprints on 13th April. Note that this is for attribution only - no changes to the text will be accepted on this issue.
Thank you for all your hard work!
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | drupalcon-coc-2018-2957525-2.patch | 12.81 KB | rachel_norfolk |
Comments
Comment #2
rachel_norfolkAdding the patch from 2017 CoC. This is simply the difference between the old CoC and the new one that can be found at https://events.drupal.org/code-conduct (minus an odd headings level thing we do on the site!)
Comment #3
hussainwebI am happy to have been of some help in this effort. Thanks for creating this issue to track and credit all the contributors.
Comment #4
justafish👋
Comment #5
ifrikThanks for keeping working on this in a participatory manner. Happy to given my comments on it.
Comment #6
manjit.singhGood to see the efforts by all the community members. I would love to add comments in future if needed.
Comment #7
timmillwoodCan we keep this somewhere?
Comment #8
rachel_norfolkCan you create a new issue for it, please Tim? This issue will only implement the CoC already updated - it’s here simply to recognise the work of those who helped on the current iteration over the Winter.
As it happens, I fully support adding that particular wording back in - I hadn’t noticed it was removed (and this is why this type of thing should be done in git, not google docs!!!)
Comment #9
timmillwoodFiled a "bug" report; #2958396: Come for the software, stay for the community.
Comment #11
rachel_norfolkComment #12
rachel_norfolkComment #13
justafishComment #16
gdemetAre the members of the CWG credited here? If not, they should be.
Comment #17
rachel_norfolkHi George. I did email everyone (except the lawyer because they would charge!) inviting them to add a comment on here and that I would credit them when I committed the change on Friday in Nashville.
I will *try* adding you now - *if * that works, we can ask others if they want to be added.