Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Post History

94%
+30 −0
Q&A How does Codidact avoid repeating Stack Exchange'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, effecti...

3 answers  ·  posted 3y ago by Monica Cellio‭  ·  last activity 2y ago by Monica Cellio‭

Question discussion policies
#4: Post edited by user avatar Monica Cellio‭ · 2020-10-22T12:59:23Z (over 2 years ago)
expanded abbreviation for clarity
  • How does Codidact avoid repeating SE's mistakes?
  • How does Codidact avoid repeating Stack Exchange'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
  • 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 Stack Exchange (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
#3: Post edited by user avatar Monica Cellio‭ · 2020-10-22T12:59:13Z (over 2 years ago)
expanded abbreviation for clarity
  • How does Codidact avoid repeating SE's mistakes?
  • How does Codidact avoid repeating Stack Exchange'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
  • 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 Stack Exchange (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
#2: Post edited by user avatar Monica Cellio‭ · 2020-03-31T02:51:32Z (almost 3 years ago)
attempting to flesh out in response to a comment
  • 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?
  • 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
#1: Initial revision by user avatar Monica Cellio‭ · 2020-02-13T03:13:34Z (almost 3 years ago)
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?