Freebie reports: Builders who put something to ... #3070
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3070
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Freebie reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
That would definitely be good. The requirement of 20 votes beeing cast and zero feedback on how many players voted already requires players to annoy others by advertising for the vote constantly.
I even wrote a book some time ago and sent it to alias with suggestions on how the problem might be solved.
It's obvious that it'd be a problem if too few (one, or two with one beeing the one asking for the vote) people voted - because then the lone vote would no longer be a secret. This can be solved by Amanda only sending out detailled reports if at least 5 people voted.
I agree on what was said.
One argument against this was, that then people could figure out who voted and for what But most of the time when some of my buildings was up for vote I knew almost everytime who were the people that voted, because usually you are around when they are voting, you invite them and show them around. So I would argue that having a count of how many players voted would actually increase the anonymity because you wouldn't always have to be around and count for yourself how many people counted (that's usually what I do) because you'd then know how many votes are left just from the counter.
The qualitative quorum, i.e. who votes how, must remain protected. The quantitative quorum, however, has a different function. It is intended to ensure that sufficient attention is paid to the vote.
The number of 20 voters as a quantitative quorum is arbitrarily fixed. It is unclear how it relates to the total number of users or the total number of active players at voting time. However, from experience, 20 voters should be an achievable number.
Builders worried about their concerns can even achieve the opposite of what is desired by constantly asking questions and begging for a vote. Reserved builders, on the other hand, may not reach enough people willing to vote.
Sufficient attention is perhaps already given with a sufficiently high number of visitors in the voting period. Not every visitor will vote, but the majority are expected to vote.
Everyone would be helped if, around the halfway point of the vote, the number of voters or visitors were announced. Amanda could do it.