Note that the docs from #include <C++> weren't finalized.
This is my personal and individual perspective and experience.
1/
This is not about an individual (do *not* name names here).
It really is not.
This is about working to keep the C++ community safe, inclusive, and welcoming.
And it is about doing so with transparency and integrity.
2/
I was on the Standard C++ Foundation board until 2021-09-22 and helped found CppCon.
I tried to help handle this, but ultimately failed, made mistakes, and for that I'm sorry:
- I suggested that the CoC group should handle this (my only good idea).
...
3/
...
- Tried to help the board handle it instead.
- Helped form the initial (flawed I now think) restrictions.
- Couldn't make a short-notice meeting, it lifted some restrictions w/o me.
- Objected to being excluded.
- Asked "At what point have I resigned?" ... & found out.
4/
I then tried to support the leaders in #include <C++> engaging w/ the Foundation. I have huge respect for their efforts. I think they did a better job than I did.
The result followed a sad pattern: not upholding CppCon's CoC with integrity or operating with transparency.
5/
This is a pattern that lost my trust in both CppCon and the Foundation's leadership.
Trust can't be repaired easily or quickly. It takes actions & time. But the community doesn't deserve to wait - they need trusted leadership now.
6/
- Doesn't address the process failings, and the lack of transparency.
- Vague, which doesn't build trust or show transparency.
- Misleading about the Sept 17 vote, which doesn't build trust or show integrity.
7/
It will be hard for leadership to step back, admit the breach of trust, and let the community heal away from them.
But this isn't about an individual, any individual. That includes the leadership of CppCon and the Foundation.
This is about the community and what it needs.
8/
It is important that this is public and the community is aware.
I hope the community will align around a published response from #include <C++> - they are one of the largest, most trusted, and most inclusive part of the C++ community and can IMO best show the path forward.
9/9
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Was actually in the process of renaming a `master` branch. Wrote up rationale:
- even if I think it's "not that bad", make others welcome
- lazy me has simpler rule -> never type `master`
- use a name w/ meaning, yay!
I wish I were even surprised that the whole rationale for why "this isn't bad and you shouldn't be offended" is actually....
*COMPLETELY MADE UP NONSENSE* being used to post-hoc justify the garbage of racists people who haven't dealt w/ their underlying biases.
When I saw this oh-so-convenient line of reasoning, of course sandwiched by vitriol at the "SJW" and "PC" attack on "simple" (captain subtext says "racist") phrases, I tried to research and find where the racist history lurked...
So I wrote up (with a *huge* amount of help from colleagues both at G and elsewhere) what I think the goals and priorities for C++ should be: wg21.link/p2137
Finally published. I'm not sure the committee agrees, but it is definitely what I and my users need.
Highlights:
1) Performance-critical software
*THE* distinguishing feature of C++ is prioritizing performance.
However, paper points out some surprising aspects: control & predictability are often neglected aspects here.
2) Both software and language evolution
"Change is the essential progress of all existence." -- Spock.
Wait, you're still debating? ;]
Seriously, things which do not change are replaced. C++ must enable both software and itself to change and grow.