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
Historical note: When this post was written, we planned to use the QPixel software as a stopgap while building a new Codidact platform from scratch. That's not what we ended up doing. Since early ...
#6: Post edited
by
Monica Cellio
·
2023-08-14T20:49:23Z (8 months ago)
- QPixel is not Codidact, yet, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?
- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- ----
- ## For communities that want to know more
- Thank you for your interest! The site you're viewing is built on QPixel, a project that started as more of an SE clone. It doesn't have all of SE's features, but it has the basics, enough to start building out your site either with imported content or from scratch.
- **We are modifying QPixel to become Codidact in the future.** Codidact will have some important differences from SE, because we've learned a lot in a decade+ of using SE about where communities have encountered friction. Some types of content don't fit SE's Q&A format as-is -- for sandboxes, code-golfing, critiques, canonical posts, and others, communities have had to twist things to make them work. And for some communities, baked-in SE features like specific close reasons or comment-handling pose challenges. Codidact is building a richer toolbox so each community can build the site it needs. You'll see these features appear gradually on your sites here, as we implement them.
- **Some things will change as we move this platform toward the Codidact vision.** Privileges will be tied to your activity rather than basing everything off a single reputation number. Answer scoring will be a little different, designed to favor consensus over controversy. Meta will work a little differently. **We think these changes are for the better, we don't expect them to be alarming, and Codidact team members will assist with the transition and be on hand to answer questions.** We'll keep working toward the [Codidact Vision](https://github.com/codidact/docs/wiki/The-Codidact-Vision).
- Please use QPixel to build your site with confidence that you'll be able to make a smooth transition to Codidact when it's ready. In the unlikely event that you decide you prefer QPixel to Codidact, no problem -- QPixel is open-source so you can take it and your data, and we'll help you set up your own server. We think you're going to prefer Codidact, though.
- Please use this Meta site if you have questions or concerns. Or if you want to get more involved in building Codidact, visit [codidact.org](https://www.codidact.org).
- **Historical note:** When this post was written, we planned to use the QPixel software as a stopgap while building a new Codidact platform from scratch. That's not what we ended up doing. Since early in 2020 we have instead been evolving the original QPixel code. Discussion in this post about migrating from QPixel to Codidact is obsolete now.
- --
- QPixel is not Codidact, yet, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?
- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- ----
- ## For communities that want to know more
- Thank you for your interest! The site you're viewing is built on QPixel, a project that started as more of an SE clone. It doesn't have all of SE's features, but it has the basics, enough to start building out your site either with imported content or from scratch.
- **We are modifying QPixel to become Codidact in the future.** Codidact will have some important differences from SE, because we've learned a lot in a decade+ of using SE about where communities have encountered friction. Some types of content don't fit SE's Q&A format as-is -- for sandboxes, code-golfing, critiques, canonical posts, and others, communities have had to twist things to make them work. And for some communities, baked-in SE features like specific close reasons or comment-handling pose challenges. Codidact is building a richer toolbox so each community can build the site it needs. You'll see these features appear gradually on your sites here, as we implement them.
- **Some things will change as we move this platform toward the Codidact vision.** Privileges will be tied to your activity rather than basing everything off a single reputation number. Answer scoring will be a little different, designed to favor consensus over controversy. Meta will work a little differently. **We think these changes are for the better, we don't expect them to be alarming, and Codidact team members will assist with the transition and be on hand to answer questions.** We'll keep working toward the [Codidact Vision](https://github.com/codidact/docs/wiki/The-Codidact-Vision).
- Please use QPixel to build your site with confidence that you'll be able to make a smooth transition to Codidact when it's ready. In the unlikely event that you decide you prefer QPixel to Codidact, no problem -- QPixel is open-source so you can take it and your data, and we'll help you set up your own server. We think you're going to prefer Codidact, though.
- Please use this Meta site if you have questions or concerns. Or if you want to get more involved in building Codidact, visit [codidact.org](https://www.codidact.org).
#5: Post edited
by
Monica Cellio
·
2020-04-07T01:54:43Z (about 4 years ago)
- QPixel is not Codidact, yet, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?
- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- ----
- ## For communities that want to know more
- Thank you for your interest! The site you're viewing is built on QPixel, a project that started as more of an SE clone. It doesn't have all of SE's features, but it has the basics, enough to start building out your site either with imported content or from scratch.
- **We are modifying QPixel to become Codidact in the future.** Codidact will have some important differences from SE, because we've learned a lot in a decade+ of using SE about where communities have encountered friction. Some types of content don't fit SE's Q&A format as-is -- for sandboxes, code-golfing, critiques, canonical posts, and others, communities have had to twist things to make them work. And for some communities, baked-in SE features like specific close reasons or comment-handling pose challenges. Codidact is building a richer toolbox so each community can build the site it needs. You'll see these features appear gradually on your sites here, as we implement them.
**Some things will change as we move this platform toward the Codidact vision.** Privileges will be tied to your activity rather than basing everything off a single reputation number. Answer scoring will be a little different, designed to favor consensus over controversy. Meta will work a little differently. **We think these changes are for the better, we don't expect them to be alarming, and Codidact team members will assist with the transition and be on hand to answer questions.**- Please use QPixel to build your site with confidence that you'll be able to make a smooth transition to Codidact when it's ready. In the unlikely event that you decide you prefer QPixel to Codidact, no problem -- QPixel is open-source so you can take it and your data, and we'll help you set up your own server. We think you're going to prefer Codidact, though.
- Please use this Meta site if you have questions or concerns. Or if you want to get more involved in building Codidact, visit [codidact.org](https://www.codidact.org).
- QPixel is not Codidact, yet, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?
- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- ----
- ## For communities that want to know more
- Thank you for your interest! The site you're viewing is built on QPixel, a project that started as more of an SE clone. It doesn't have all of SE's features, but it has the basics, enough to start building out your site either with imported content or from scratch.
- **We are modifying QPixel to become Codidact in the future.** Codidact will have some important differences from SE, because we've learned a lot in a decade+ of using SE about where communities have encountered friction. Some types of content don't fit SE's Q&A format as-is -- for sandboxes, code-golfing, critiques, canonical posts, and others, communities have had to twist things to make them work. And for some communities, baked-in SE features like specific close reasons or comment-handling pose challenges. Codidact is building a richer toolbox so each community can build the site it needs. You'll see these features appear gradually on your sites here, as we implement them.
- **Some things will change as we move this platform toward the Codidact vision.** Privileges will be tied to your activity rather than basing everything off a single reputation number. Answer scoring will be a little different, designed to favor consensus over controversy. Meta will work a little differently. **We think these changes are for the better, we don't expect them to be alarming, and Codidact team members will assist with the transition and be on hand to answer questions.** We'll keep working toward the [Codidact Vision](https://github.com/codidact/docs/wiki/The-Codidact-Vision).
- Please use QPixel to build your site with confidence that you'll be able to make a smooth transition to Codidact when it's ready. In the unlikely event that you decide you prefer QPixel to Codidact, no problem -- QPixel is open-source so you can take it and your data, and we'll help you set up your own server. We think you're going to prefer Codidact, though.
- Please use this Meta site if you have questions or concerns. Or if you want to get more involved in building Codidact, visit [codidact.org](https://www.codidact.org).
#4: Post edited
by
Monica Cellio
·
2020-04-07T00:21:50Z (about 4 years ago)
Now that we're evolving QPixel toward Codidact instead of doing a full cut-over to a new platform, updated explanation for communities.
QPixel is not Codidact, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- ----
- ## For communities that want to know more
Thank you for your interest! The site you're viewing is built on QPixel, a project that is more of an SE clone. It doesn't have all of SE's features, but it has the basics, enough to start building out your site either with imported content or from scratch. We'll keep it running until Codidact is ready.**The eventual goal is to move communities from QPixel to Codidact.** Codidact will have some important differences from SE, because we've learned a lot in a decade+ of using SE about where communities have encountered friction. Some types of content don't fit SE's Q&A format as-is -- for sandboxes, code-golfing, critiques, canonical posts, and others, communities have had to twist things to make them work. And for some communities, baked-in SE features like specific close reasons or comment-handling pose challenges. Codidact is building a richer toolbox so each community can build the site it needs.**Some things will change when your community moves from QPixel to Codidact.** Privileges will be tied to your activity rather than basing everything off a single reputation number. Answer scoring will be a little different, designed to favor consensus over controversy. Meta will work a little differently. **We think these changes are for the better, we don't expect them to be alarming, and Codidact team members will assist with the transition and be on hand to answer questions.**- Please use QPixel to build your site with confidence that you'll be able to make a smooth transition to Codidact when it's ready. In the unlikely event that you decide you prefer QPixel to Codidact, no problem -- QPixel is open-source so you can take it and your data, and we'll help you set up your own server. We think you're going to prefer Codidact, though.
- Please use this Meta site if you have questions or concerns. Or if you want to get more involved in building Codidact, visit [codidact.org](https://www.codidact.org).
- QPixel is not Codidact, yet, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?
- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- ----
- ## For communities that want to know more
- Thank you for your interest! The site you're viewing is built on QPixel, a project that started as more of an SE clone. It doesn't have all of SE's features, but it has the basics, enough to start building out your site either with imported content or from scratch.
- **We are modifying QPixel to become Codidact in the future.** Codidact will have some important differences from SE, because we've learned a lot in a decade+ of using SE about where communities have encountered friction. Some types of content don't fit SE's Q&A format as-is -- for sandboxes, code-golfing, critiques, canonical posts, and others, communities have had to twist things to make them work. And for some communities, baked-in SE features like specific close reasons or comment-handling pose challenges. Codidact is building a richer toolbox so each community can build the site it needs. You'll see these features appear gradually on your sites here, as we implement them.
- **Some things will change as we move this platform toward the Codidact vision.** Privileges will be tied to your activity rather than basing everything off a single reputation number. Answer scoring will be a little different, designed to favor consensus over controversy. Meta will work a little differently. **We think these changes are for the better, we don't expect them to be alarming, and Codidact team members will assist with the transition and be on hand to answer questions.**
- Please use QPixel to build your site with confidence that you'll be able to make a smooth transition to Codidact when it's ready. In the unlikely event that you decide you prefer QPixel to Codidact, no problem -- QPixel is open-source so you can take it and your data, and we'll help you set up your own server. We think you're going to prefer Codidact, though.
- Please use this Meta site if you have questions or concerns. Or if you want to get more involved in building Codidact, visit [codidact.org](https://www.codidact.org).
#3: Post edited
by
ArtOfCode
·
2020-02-17T22:58:15Z (about 4 years ago)
setup support is a thing we should do
- QPixel is not Codidact, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?
- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- ----
- ## For communities that want to know more
- Thank you for your interest! The site you're viewing is built on QPixel, a project that is more of an SE clone. It doesn't have all of SE's features, but it has the basics, enough to start building out your site either with imported content or from scratch. We'll keep it running until Codidact is ready.
- **The eventual goal is to move communities from QPixel to Codidact.** Codidact will have some important differences from SE, because we've learned a lot in a decade+ of using SE about where communities have encountered friction. Some types of content don't fit SE's Q&A format as-is -- for sandboxes, code-golfing, critiques, canonical posts, and others, communities have had to twist things to make them work. And for some communities, baked-in SE features like specific close reasons or comment-handling pose challenges. Codidact is building a richer toolbox so each community can build the site it needs.
- **Some things will change when your community moves from QPixel to Codidact.** Privileges will be tied to your activity rather than basing everything off a single reputation number. Answer scoring will be a little different, designed to favor consensus over controversy. Meta will work a little differently. **We think these changes are for the better, we don't expect them to be alarming, and Codidact team members will assist with the transition and be on hand to answer questions.**
Please use QPixel to build your site with confidence that you'll be able to make a smooth transition to Codidact when it's ready. In the unlikely event that you decide you prefer QPixel to Codidact, no problem -- QPixel is open-source so you can take it and your data and run your own server. We think you're going to prefer Codidact, though.- Please use this Meta site if you have questions or concerns. Or if you want to get more involved in building Codidact, visit [codidact.org](https://www.codidact.org).
- QPixel is not Codidact, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?
- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- ----
- ## For communities that want to know more
- Thank you for your interest! The site you're viewing is built on QPixel, a project that is more of an SE clone. It doesn't have all of SE's features, but it has the basics, enough to start building out your site either with imported content or from scratch. We'll keep it running until Codidact is ready.
- **The eventual goal is to move communities from QPixel to Codidact.** Codidact will have some important differences from SE, because we've learned a lot in a decade+ of using SE about where communities have encountered friction. Some types of content don't fit SE's Q&A format as-is -- for sandboxes, code-golfing, critiques, canonical posts, and others, communities have had to twist things to make them work. And for some communities, baked-in SE features like specific close reasons or comment-handling pose challenges. Codidact is building a richer toolbox so each community can build the site it needs.
- **Some things will change when your community moves from QPixel to Codidact.** Privileges will be tied to your activity rather than basing everything off a single reputation number. Answer scoring will be a little different, designed to favor consensus over controversy. Meta will work a little differently. **We think these changes are for the better, we don't expect them to be alarming, and Codidact team members will assist with the transition and be on hand to answer questions.**
- Please use QPixel to build your site with confidence that you'll be able to make a smooth transition to Codidact when it's ready. In the unlikely event that you decide you prefer QPixel to Codidact, no problem -- QPixel is open-source so you can take it and your data, and we'll help you set up your own server. We think you're going to prefer Codidact, though.
- Please use this Meta site if you have questions or concerns. Or if you want to get more involved in building Codidact, visit [codidact.org](https://www.codidact.org).
#2: Post edited
by
Monica Cellio
·
2020-02-17T04:28:56Z (about 4 years ago)
added a section to address people who are checking us out, too
- QPixel is not Codidact, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?
- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- QPixel is not Codidact, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving?
- Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)
- ----
- ## For communities that want to know more
- Thank you for your interest! The site you're viewing is built on QPixel, a project that is more of an SE clone. It doesn't have all of SE's features, but it has the basics, enough to start building out your site either with imported content or from scratch. We'll keep it running until Codidact is ready.
- **The eventual goal is to move communities from QPixel to Codidact.** Codidact will have some important differences from SE, because we've learned a lot in a decade+ of using SE about where communities have encountered friction. Some types of content don't fit SE's Q&A format as-is -- for sandboxes, code-golfing, critiques, canonical posts, and others, communities have had to twist things to make them work. And for some communities, baked-in SE features like specific close reasons or comment-handling pose challenges. Codidact is building a richer toolbox so each community can build the site it needs.
- **Some things will change when your community moves from QPixel to Codidact.** Privileges will be tied to your activity rather than basing everything off a single reputation number. Answer scoring will be a little different, designed to favor consensus over controversy. Meta will work a little differently. **We think these changes are for the better, we don't expect them to be alarming, and Codidact team members will assist with the transition and be on hand to answer questions.**
- Please use QPixel to build your site with confidence that you'll be able to make a smooth transition to Codidact when it's ready. In the unlikely event that you decide you prefer QPixel to Codidact, no problem -- QPixel is open-source so you can take it and your data and run your own server. We think you're going to prefer Codidact, though.
- Please use this Meta site if you have questions or concerns. Or if you want to get more involved in building Codidact, visit [codidact.org](https://www.codidact.org).
#1: Initial revision
by
Monica Cellio
·
2020-02-12T03:20:20Z (about 4 years ago)
QPixel is not Codidact, and so we're not yet trying to "build all the things" (communities). But some communities on SE seem eager to move even to a temporary site, and [one already has](https://writing.codidact.com/). Which communities are looking to move, and what do we know about them? Are there particular users we should talk with? Meta posts where they've discussed moving? Please use this question to record what we know about candidate communities, so we can collectively figure out logistics, timing, etc. (It's probably better to add communities one at a time, for instance.)