Timeline for Help us identify new roles for community members
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2022 at 23:06 | comment | added | Bergi | Details that the help center doesn't mention are collected in the [faq] already | |
| Dec 2, 2022 at 21:40 | comment | added | Kevin B | That wouldn't fix the reason they're not useful. | |
| Dec 2, 2022 at 21:36 | comment | added | Sep Roland | @KevinB That's why they have to be very short and focussed. | |
| Dec 2, 2022 at 21:30 | comment | added | Kevin B | polls on meta would be no more useful than upvotes and downvotes on meta at determining a meaningful consensus. | |
| Dec 2, 2022 at 21:27 | history | edited | Sep Roland | CC BY-SA 4.0 |
added 132 characters in body
|
| Dec 2, 2022 at 21:16 | comment | added | Sep Roland | @starball The voting on Meta posts to me pretty much says nothing about agreement or disagreement with the post's content. For that, we should at least introduce the concept of a 'poll' where a vote can be cast based on a short one-line proposal (ignoring all remaining text). I don't think the poll-vote should replace the post-vote but rather complement it. The Help Officer could be at the heart of setting up these polls. | |
| Dec 2, 2022 at 20:47 | comment | added | starball | Can't we all just be passive help officers? I was under the impression that the current way of doing things is to make feature-requests and let the community voice their agreement or disagreement by voting, and then mods can escalate the request to staff by tagging status-review. I think that communal vote and discussion part is important. If we create a "Help Officer" role, are you suggesting that that that communal vote and discussion be removed from the process? And what do you think is insufficient about the status-review tagging process? | |
| Dec 2, 2022 at 20:39 | history | answered | Sep Roland | CC BY-SA 4.0 |