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 »
Q&A

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

75%
+4 −0
Q&A How can we poll a community?

In my effort of giving structure to EE.CD tags pages, I find myself in the need of asking the community for consensus about some debatable choices. Of course the place for this is EE Meta, but I'd...

2 answers  ·  posted 1y ago by Lorenzo Donati‭  ·  edited 5mo ago by trichoplax‭

#2: Post edited by user avatar trichoplax‭ · 2024-08-07T12:29:54Z (5 months ago)
Improve styling, layout, and reading flow by adding a summary tag
  • In my effort of giving structure to EE.CD tags pages, I find myself in the need of asking the community for consensus about some debatable choices.
  • Of course the place for this is EE Meta, but I'd like to know in general if there is a standard practice to poll the community.
  • In other words, suppose I want to ask the community if it is OK to do something out of a list of actions (multiple choice of actions), how to do that in an effective way?
  • If I list all the choices in the question it is impossible to know why the question was upvoted or downvoted. I could read comments and possible answers, but this has proven to be messy and lengthy for a simple multiple choice which doesn't need too much discussion.
  • I thought about the following process:
  • 1. Post the issue in a question, with general premises.
  • 2. Post an answer for each choice, telling the community in the question to upvote/downvote one (or more) of the answers to "vote" on the choice to undertake.
  • 3. Wait some time before taking action. The "expiry date" of the poll should be advertised in the question.
  • Crude example:
  • <details>
  • ### Question
  • I think the tag `cruncher` is too ambiguous. I have three choices for the community. How should I proceed?
  • The three choices are spelled out in the answers below. Please express your vote by upvoting/downvoting those answers. The poll expires in 4 days. I will take steps to enact the community decision after that date.
  • ### Answer 1
  • Ask the devs to delete the tag and add it to a blacklist.
  • ### Answer 2
  • Create two new tags `potato-cruncher` and `cookie-cruncher`,
  • add `cruncher` as a synonym to `potato-cruncher`.
  • ### Answer 3
  • Create two new tags `potato-cruncher` and `cookie-cruncher`,
  • add `cruncher` as a synonym to `cookie-cruncher`.
  • </details>
  • Is this a sensible approach? Any alternative?
  • In my effort of giving structure to EE.CD tags pages, I find myself in the need of asking the community for consensus about some debatable choices.
  • Of course the place for this is EE Meta, but I'd like to know in general if there is a standard practice to poll the community.
  • In other words, suppose I want to ask the community if it is OK to do something out of a list of actions (multiple choice of actions), how to do that in an effective way?
  • If I list all the choices in the question it is impossible to know why the question was upvoted or downvoted. I could read comments and possible answers, but this has proven to be messy and lengthy for a simple multiple choice which doesn't need too much discussion.
  • I thought about the following process:
  • 1. Post the issue in a question, with general premises.
  • 2. Post an answer for each choice, telling the community in the question to upvote/downvote one (or more) of the answers to "vote" on the choice to undertake.
  • 3. Wait some time before taking action. The "expiry date" of the poll should be advertised in the question.
  • <details>
  • <summary>Crude example</summary>
  • ### Question
  • I think the tag `cruncher` is too ambiguous. I have three choices for the community. How should I proceed?
  • The three choices are spelled out in the answers below. Please express your vote by upvoting/downvoting those answers. The poll expires in 4 days. I will take steps to enact the community decision after that date.
  • ### Answer 1
  • Ask the devs to delete the tag and add it to a blacklist.
  • ### Answer 2
  • Create two new tags `potato-cruncher` and `cookie-cruncher`,
  • add `cruncher` as a synonym to `potato-cruncher`.
  • ### Answer 3
  • Create two new tags `potato-cruncher` and `cookie-cruncher`,
  • add `cruncher` as a synonym to `cookie-cruncher`.
  • </details>
  • Is this a sensible approach? Any alternative?
#1: Initial revision by user avatar Lorenzo Donati‭ · 2023-08-20T08:33:30Z (over 1 year ago)
How can we poll a community?
In my effort of giving structure to EE.CD tags pages, I find myself in the need of asking the community for consensus about some debatable choices.

Of course the place for this is EE Meta, but I'd like to know in general if there is a standard practice to poll the community.

In other words, suppose I want to ask the community if it is OK to do something out of a list of actions (multiple choice of actions), how to do that in an effective way?

If I list all the choices in the question it is impossible to know why the question was upvoted or downvoted. I could read comments and possible answers, but this has proven to be messy and lengthy for a simple multiple choice which doesn't need too much discussion.

I thought about the following process:


1. Post the issue in a question, with general premises. 
2. Post an answer for each choice, telling the community in the question to upvote/downvote one (or more) of the answers to "vote" on the choice to undertake.
3. Wait some time before taking action. The "expiry date" of the poll should be advertised in the question.

Crude example:

<details>


### Question

I think the tag `cruncher` is too ambiguous. I have three choices for the community. How should I proceed?

The three choices are spelled out in the answers below. Please express your vote by upvoting/downvoting those answers. The poll expires in 4 days. I will take steps to enact the community decision after that date.

### Answer 1

Ask the devs to delete the tag and add it to a blacklist.

### Answer 2

Create two new tags `potato-cruncher` and `cookie-cruncher`,
add `cruncher` as a synonym to `potato-cruncher`.

### Answer 3

Create two new tags `potato-cruncher` and `cookie-cruncher`,
add `cruncher` as a synonym to `cookie-cruncher`.

</details>

Is this a sensible approach? Any alternative?