Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
How does Codidact avoid repeating SE's mistakes?
I received an important question in private email, and I'm bringing it here so we can improve on the answer I sent. This won't be the last time we get this question; let's develop a clear, effective response.
The question, slightly paraphrased, was:
How will you prevent Codidact from repeating the problems that got SE into its current state? What, in your opinion, caused SE's problems, and how are you avoiding them?
To elaborate a bit, those problems include:
SE management neglecting, ignoring, and then changing things out from under the communities they host and the volunteers who support them (e.g. license changes, policy changes), apparently for financial reasons
Lack of transparency and accountability in company actions that affect communities
Community turmoil caused by company actions that seem mysterious and harmful, and community fragmentation and decline as some leave, others stay, some change their behavior, and so on