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
Community Proposals
Community Proposals
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 »
Users Search
Help Dashboard Sign In Sign Up
Q&A Blog
Q&A
Posts Tags Edits
Ask Question

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

88%
+14 −0
Q&A What, another meta? What's this site for?

Codidact Meta is for questions about the instance that we will host. You can also request changes and report bugs in the software platform that runs it, though you're also welcome to use GitHub. ...

1 answer  ·  posted 5y ago by Monica Cellio‭  ·  last activity 3y ago by Kevin M. Mansour‭

Question discussion announcement
#7: Post edited by user avatar Monica Cellio‭ · 2020-12-20T17:25:51Z (about 4 years ago)
this didn't age all that well...
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
  • Codidact Meta is for questions about the instance that we will host. You can also request changes and report bugs in the software platform that runs it, though you're also welcome to use [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself. If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
discussion announcement
discussion announcement
#6: Post edited by user avatar pnuts‭ · 2020-12-20T12:15:00Z (about 4 years ago)
Update. 
What, another meta?  What's this site for?
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use the [forum](https://forum.codidact.org/) and [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
  • Finally, I see that Codidact Meta has a meta site. That's built into QPixel. We should probably, um, ignore that.
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
discussion announcement
discussion announcement
#5: Post edited by user avatar pnuts‭ · 2020-07-19T02:34:03Z (over 4 years ago)
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use the [forum](https://forum.codidact.org/) and [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
  • Finally, I see that Codidact Meta has a meta site. That's built into QPixel. We should probably, um, ignore that.
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
#4: Post edited by user avatar pnuts‭ · 2020-07-18T08:27:14Z (over 4 years ago)
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use the [forum](https://forum.codidact.org/) and [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
  • Finally, I see that Codidact Meta has a meta site. That's built into QPixel. We should probably, um, ignore that.
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
#3: Post edited by user avatar pnuts‭ · 2020-07-18T00:21:09Z (over 4 years ago)
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use the [forum](https://forum.codidact.org/) and [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
  • Finally, I see that Codidact Meta has a meta site. That's built into QPixel. We should probably, um, ignore that.
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
#2: Post edited by user avatar pnuts‭ · 2020-07-18T00:20:57Z (over 4 years ago)
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use the [forum](https://forum.codidact.org/) and [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
  • Finally, I see that Codidact Meta has a meta site. That's built into QPixel. We should probably, um, ignore that.
  • Codidact Meta is for questions about the instance that we will host. It is not about the platform itself; for that, please continue to use [GitHub](https://github.com/codidact).
  • But what does that leave, you ask? Use this meta site for questions about:
  • - instance-level policies and governance
  • - new communities that would (or might) like to join us and how to help them
  • - setup/configuration of our instance (URLs, services, integrations, etc)
  • - emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)
  • It's also fine to ask questions about using the software itself (currently QPixel, later Codidact). If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions. Those are fine.
#1: Initial revision by user avatar Monica Cellio‭ · 2020-02-12T02:45:30Z (almost 5 years ago) 
Codidact Meta is for questions about the instance that we will host.  It is not about the platform itself; for that, please continue to use the [forum](https://forum.codidact.org/) and [GitHub](https://github.com/codidact).

But what does that leave, you ask?  Use this meta site for questions about:

- instance-level policies and governance
- new communities that would (or might) like to join us and how to help them
- setup/configuration of our instance (URLs, services, integrations, etc)
- emergent patterns on our communities that might need to be fed back to the platform developers (community X has this need and is currently kludging it by doing Y; what would help them? etc)

It's also fine to ask questions about using the software itself (currently QPixel, later Codidact).  If it turns out to be a bug someone can file a report on GitHub so it doesn't get lost, but I assume there will be "how do I do X?" and "why did this do that?" questions.  Those are fine.

Finally, I see that Codidact Meta has a meta site.  That's built into QPixel.  We should probably, um, ignore that.