{"push_id":2567980139,"size":3,"distinct_size":3,"ref":"refs/heads/coc-enforcement-reporting","head":"03be613ad34b1c016cff4aabd9c17cdb92f81f59","before":"3d9921178590a0c00158a81611a8a97870d1e5bf","commits":[{"sha":"25e26c4b503a815dfc406cc39bd04bf3b276cf12","author":{"name":"Sasha Romijn","email":"64b2b6d12bfe4baae7dad3d018f8cbf6b0e7a044@mxsasha.eu"},"message":"Removed requirement for actions to be taken by CoC committee chair.\n\nIn practice, the CoC committee has a rotating role for who should\nsend messages or take other actions. This has proven to be effective,\nhelps distribute the workload, and distributes experience.","distinct":true,"url":"https://api.github.com/repos/mxsasha/djangoproject.com/commits/25e26c4b503a815dfc406cc39bd04bf3b276cf12"},{"sha":"88b25efdbbfe62cc3aeaa03869ce3beed56a1205","author":{"name":"Sasha Romijn","email":"64b2b6d12bfe4baae7dad3d018f8cbf6b0e7a044@mxsasha.eu"},"message":"Adjusted CoC committee reporting requirements.\n\nI see no purpose in reporting to the Django core team, and in fact\nno team by that name currently even exist in the community.\n\nFor reporting to the board, this change adds an exception for cases\nwhere the CoC incident involved a member of the board.","distinct":true,"url":"https://api.github.com/repos/mxsasha/djangoproject.com/commits/88b25efdbbfe62cc3aeaa03869ce3beed56a1205"},{"sha":"03be613ad34b1c016cff4aabd9c17cdb92f81f59","author":{"name":"Sasha Romijn","email":"64b2b6d12bfe4baae7dad3d018f8cbf6b0e7a044@mxsasha.eu"},"message":"Changed working group to committee in CoC enforcement manual.\n\nThere is actually no working group, the group is a committee,\nso this language was slightly confusing.","distinct":true,"url":"https://api.github.com/repos/mxsasha/djangoproject.com/commits/03be613ad34b1c016cff4aabd9c17cdb92f81f59"}]}
{"actor":{"display_login":"mxsasha"}}