|
| 1 | +--- |
| 2 | +layout: home |
| 3 | +title: "#include ＜C++＞ Update on CppCon" |
| 4 | +toc: true |
| 5 | +--- |
| 6 | + |
| 7 | +## Overview |
| 8 | + |
| 9 | +CppCon has recently published a post with new, expanded, and continuing [diversity and inclusion initiatives for CppCon 2022](https://cppcon.org/diversity-2022/). We believe this is a good time to review how much progress CppCon has made on the eight meaningful changes that we asked for in our [#include <C++> position on CppCon safety](https://www.includecpp.org/posts/communication-cppcon/) document. |
| 10 | + |
| 11 | + |
| 12 | +## Transparency and public accountability from CppCon and the Standard C++ Foundation. |
| 13 | + |
| 14 | +### 1. A full, public transparency report from the Standard C++ Foundation on this incident. |
| 15 | + |
| 16 | +CppCon has published a transparency report on this incident [here](https://cppcon.org/announcing-cppcon-safety-policy/) (together with the announcement of a new CppCon Safety Policy), with a follow-post answering additional questions [here](https://cppcon.org/answering-your-questions-about-our-case-transparency-report-and-safety-policy/). These posts contain a considerable amount of information on the incident and its aftermath, however notably they do not mention the precise nature of the conviction, describing it only as a "serious felony". Further, they make no mention of the private meeting the Foundation board held with X. Understanding why such a meeting was held and the purpose of it, as well as the outcome, is part of the transparency that is still missing. |
| 17 | + |
| 18 | +### 2. Public annual CppCon Code of Conduct transparency reports. |
| 19 | + |
| 20 | +CppCon published a Code of Conduct transparency report for the 2021 conference [here](https://cppcon.org/cppcon-2021-transparency-report/) and have committed to continue to do so annually. |
| 21 | + |
| 22 | +### 3. Public minutes for the Standard C++ Foundation board meetings (following the example of the Python Software Foundation). |
| 23 | + |
| 24 | +The Standard C++ Foundation has started to [publish minutes](https://isocpp.org/about/board-meeting-minutes) of their board meetings. |
| 25 | + |
| 26 | +### 4. Public annual reports on the activities and decisions of the Standard C++ Foundation Board (following the example of the Python Software Foundation). |
| 27 | + |
| 28 | +The Standard C++ Foundation has published an [annual report for the 2021 fiscal year](https://isocpp.org/blog/2022/03/standard-cpp-foundation-annual-report-for-fiscal-year-2021), and [publicly committed](https://isocpp.org/about/annual-reports) to continue to publish these reports annually. |
| 29 | + |
| 30 | +## Changes to the governance of CppCon. |
| 31 | + |
| 32 | +### 5. Establishment of a transparent and diverse CppCon Steering Committee that has authority over CppCon. CppCon Attendees should elect the Steering Committee, and have short term limits. |
| 33 | + |
| 34 | +No changes to the governance of CppCon have been announced to date other than appointing Daisy Hollman as Program Chair. While we are confident Daisy will be a great Program Chair, the issues with leadership that led to the #include <C++> statement were not with the Program Chair position (in fact, the previous incumbent, Bryce Adelstein Lelbach, quit over the way this situation was handled). We therefore do not consider this to be a meaningful leadership or governance change. |
| 35 | + |
| 36 | +### 6. Changes to the composition of the Standard C++ Foundation board. |
| 37 | + |
| 38 | +No changes to the composition of the Standard C++ Foundation board have been announced to date. |
| 39 | + |
| 40 | +## Empowerment of the CppCon Code of Conduct team. |
| 41 | + |
| 42 | +### 7. Extension of the mandate of the team to all questions of attendee safety. |
| 43 | + |
| 44 | +CppCon has announced a [Safety Policy](https://cppcon.org/safetypolicy/) and has publicly announced that they have placed the implementation of that policy fully in the hands of the Code of Conduct team. As far as we can tell, this is being followed in practice: a recent security-related question that was raised with the CppCon leadership was immediately forwarded to the Code of Conduct team, along with a confirmation that the decision on this question lies with the Code of Conduct team. |
| 45 | + |
| 46 | +### 8. Possibility for the team to take binding decisions on the conference leadership. |
| 47 | + |
| 48 | +CppCon has confirmed that the Code of Conduct team's mandate to enforce the Code of Conduct extends to anyone at CppCon, including the conference leadership, and added wording to the published [CppCon Code of Conduct](https://github.com/CppCon/CppConCodeOfConduct/blob/master/code_of_conduct.md) explicitly stating this ("The code of conduct team is empowered to, amongst other things: eject any participant from the conference (including speakers and organisers); cancel a presentation in progress or scheduled; close down any online presentation chat forum"). |
| 49 | + |
| 50 | +## Summary Table |
| 51 | + |
| 52 | +| Change or Action | Current Status | |
| 53 | +|------------------------------------|-------------------------------| |
| 54 | +| 1. Incident Transparency Report | :heavy_check_mark: Incomplete | |
| 55 | +| 2. CppCon Transparency Reports | :white_check_mark: | |
| 56 | +| 3. Foundation Board Minutes | :white_check_mark: | |
| 57 | +| 4. Foundation Board Annual Reports | :white_check_mark: | |
| 58 | +| 5. Steering Committee | :question: | |
| 59 | +| 6. Foundation Board | :question: | |
| 60 | +| 7. CoC Team Mandate | :white_check_mark: | |
| 61 | +| 8. CoC Binds Leadership | :white_check_mark: | |
0 commit comments