# Changing PEP 13 to remove the CoC responsibility from the SC

**URL:** <https://discuss.python.org/t/changing-pep-13-to-remove-the-coc-responsibility-from-the-sc/71885>\
**Category:** Committers\
**Created:** [November 21, 2024, 1:56pm UTC](https://discuss.python.org/t/changing-pep-13-to-remove-the-coc-responsibility-from-the-sc/71885 "2024-11-21T13:56:24Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)\
**Post date:** [November 21, 2024, 7:17pm UTC](https://discuss.python.org/t/changing-pep-13-to-remove-the-coc-responsibility-from-the-sc/71885/15 "2024-11-21T19:17:32Z")

</div>

> [@tim.one](#):
>
> Right now is at least the third time over the years I’ll suggest the minimal level of “CoC transparency report” produced for PyCons would already be a huge improvement for the CoC WG and SC to produce.

I strongly agree with that. I will put this on the COC WG agenda for the next meeting.

---

_[View the full topic](https://discuss.python.org/t/changing-pep-13-to-remove-the-coc-responsibility-from-the-sc/71885)._