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.
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.
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.
1 answer
The title was weird. That's why I came to this post. Then, saw something :laugh:.
Additional Information :
- You can use GitHub issues always for filling a bug report or feature-request.
- If you think that your feature-request needs a discussion to public (not all features are helpful. And, Codidact is open-source. We build everything for user's better performance), then you should ask it in Codidact Meta.
- If you have faced an issue. And, it's have been a long day you are facing that, then you have to post it in Codidact Meta.
- If you have faced a "tiny" issue, then leave a message in Discord. So, developers can solve the problem as soon as possible.
0 comment threads
1 comment thread