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
The best place to raise concerns about any specific actions -- whether by mods or by the community -- is the per-community Meta category. Differences of opinion about closing questions might reall...
Answer
#2: Post edited
by
Monica Cellio
·
2024-07-09T22:27:38Z (5 months ago)
https://github.com/codidact/qpixel/issues/1354
- The best place to raise concerns about any specific actions -- whether by mods or by the community -- is the per-community Meta category. Differences of opinion about closing questions might really be differences of opinion about scope or policy, or they might be rooted in differing knowledge. A constructive community discussion about these issues is a good first step in resolving them. Moderators are not infallible and are not necessarily experts in all aspects of a community's scope. They are trusted caretakers, ideally chosen by the community (but I know we don't have formal elections here yet).
One problem this post and its comments have pointed out is that currently there's no way to ask for a closed question to be reopened except through a custom moderator-only flag. Users with the Curate ability can close and reopen (and take some other actions), and they can see the standard flags, but they can't see the custom moderator flags so you've got no way to systematically communicate with them about reopening. That's a gap, and I've written up a [change request](https://github.com/codidact/qpixel/issues/1354) to add a flag type for communicating with curators. I *think* this is not too hard, and I hope to take a try at implementing this soon.I recognize that abilities are still too hard to get (we've had Meta discussions about that and don't yet have a clear path forward), but it's a start. Remember that moderators can explicitly grant abilities, so while we work on that, communities can appoint curators if they'd like to.
- The best place to raise concerns about any specific actions -- whether by mods or by the community -- is the per-community Meta category. Differences of opinion about closing questions might really be differences of opinion about scope or policy, or they might be rooted in differing knowledge. A constructive community discussion about these issues is a good first step in resolving them. Moderators are not infallible and are not necessarily experts in all aspects of a community's scope. They are trusted caretakers, ideally chosen by the community (but I know we don't have formal elections here yet).
- One problem this post and its comments have pointed out is that until now there was no way to ask for a closed question to be reopened except through a custom moderator-only flag. Users with the Curate ability can close and reopen (and take some other actions), and they can see the standard flags, but they can't see the custom moderator flags so you've got no way to systematically communicate with them about reopening. We've now fixed this by adding a new flag type, "change post status", to request close/reopen, lock/unlock, or delete/undelete. When raising this flag you must add a message about what you want. As part of this change, we renamed "other" to "moderator attention" and clarified that the latter, unlike other flags, goes only to moderators.
- I recognize that abilities are still too hard to get (we've had Meta discussions about that and don't yet have a clear path forward), but flagging for curators is a start. Remember that moderators can explicitly grant abilities, so while we work on that, communities can appoint curators if they'd like to.
#1: Initial revision
by
Monica Cellio
·
2024-06-26T15:37:49Z (5 months ago)
The best place to raise concerns about any specific actions -- whether by mods or by the community -- is the per-community Meta category. Differences of opinion about closing questions might really be differences of opinion about scope or policy, or they might be rooted in differing knowledge. A constructive community discussion about these issues is a good first step in resolving them. Moderators are not infallible and are not necessarily experts in all aspects of a community's scope. They are trusted caretakers, ideally chosen by the community (but I know we don't have formal elections here yet). One problem this post and its comments have pointed out is that currently there's no way to ask for a closed question to be reopened except through a custom moderator-only flag. Users with the Curate ability can close and reopen (and take some other actions), and they can see the standard flags, but they can't see the custom moderator flags so you've got no way to systematically communicate with them about reopening. That's a gap, and I've written up a [change request](https://github.com/codidact/qpixel/issues/1354) to add a flag type for communicating with curators. I *think* this is not too hard, and I hope to take a try at implementing this soon. I recognize that abilities are still too hard to get (we've had Meta discussions about that and don't yet have a clear path forward), but it's a start. Remember that moderators can explicitly grant abilities, so while we work on that, communities can appoint curators if they'd like to.