Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Gazz]

And Skuggaping smorgasbrod does what?

[teloft]

And Skuggaping smorgasbrod does what?

Some elements of it do rating/voting for Suggestion, and other make it easy to follow up on and group similar suggestions.

As you noted, it is a smorgasbrod so there is a lot of stuff on it that is not related to voting..

[zagibu]

There are many external tools, which could be useful, but all I've seen so far lack SM forum integration.

[Footkerchief]

There are many external tools, which could be useful, but all I've seen so far lack SM forum integration.

Does it really need that much integration, though?  Does ESV's current level of integration go any farther than pulling the user ID out of the session?

[zagibu]

No, you are right, I guess it doesn't do much more than that. I think it also checks for admin, mod or guest rights somewhere, but this could also be checked by looking it up in the db.

[dorf]

I kind of like Rainseeker's approach to voting, so I'll try to translate it here:
We nominate/gather some suggestions from the community.
We vote for our favorite ones.
We don't reveal the results until the voting ends.

Pros:

• We get rid of redundant suggestions and the "human herd instinct".
• Suggestions can be easily transferred to the next voting round

Cons:

• For this to be effective, we'd have to limit the nomination and voting time period from eternal to a month or so.
• Once the nominations are final, the voting starts and no more suggestions can be added.
• The votes would be cleared before each voting round.
• We'd probably have to limit the amount of suggestions and/or the summary.

I think this would work great, if we didn't already have 200+ suggestions.
But since I came this far, I'll just click the "Post" button and wait for comments.

[zagibu]

Periodic re-voting could be interesting. How long would you design a period? A month? And what happens with monthly winners? Might be a bit boring if the same top10 suggestions win every month. Maybe remove them and have an end-year voting of all top suggestions?

[Mephansteras]

Seems like it would depend mostly on what's most useful for Toady. I know he's planning on shorter release cycles from here on out, so maybe once a release (whatever that ends up being?)

[dorf]

How long would you design a period? A month?

We'd tailor the time periods to Toady's needs.

And what happens with monthly winners?

The results will be forwarded to Toady.

Might be a bit boring if the same top10 suggestions win every month. Maybe remove them and have an end-year voting of all top suggestions?

Yeah, you pointed out a good issue. Toady will probably implement 0 - 2 suggestions, depending on difficulty, priority, workload, schedule and so on.

Perhaps we could remove the suggestions that received most of the votes (sure winners) and recycle the others.
End-year voting doesn't seem necessary, except Toady would explicitly want that. I see the winners as suggestions that the people REALLY want in, sooner or later. And so, they would be permanently added to Toady's TODO list, if he would agree to this.

I feel the nomination phase is also important here.
Do we exclude the suggestions that fared poorly in the previous voting rounds?
Do we set up some rules for nominating a suggestion (i.e. the suggestions MUST be well defined, not be too broad, not overlap with others, have a descriptive title and a concise summary...)?
Assuming we'll impose a limit... how do we decide which suggestions to put in, once the amount of suggestions exceeds the limit?

[BlckKnght]

Periodic re-voting could be interesting. How long would you design a period? A month? And what happens with monthly winners? Might be a bit boring if the same top10 suggestions win every month. Maybe remove them and have an end-year voting of all top suggestions?

Um, this seems like we're going backwards.  Isn't periodic voting on suggestions exactly what the eternal voting system was created to replace? Why would we want to go back to the old way?

[Footkerchief]

Yeah, I personally would like to preserve the "Eternal" aspect of ESV.

[dorf]

Ah, I was not aware of that.

[zagibu]

Periodic re-voting could be interesting. How long would you design a period? A month? And what happens with monthly winners? Might be a bit boring if the same top10 suggestions win every month. Maybe remove them and have an end-year voting of all top suggestions?

Um, this seems like we're going backwards.  Isn't periodic voting on suggestions exactly what the eternal voting system was created to replace? Why would we want to go back to the old way?

The script was created to reduce the amount of manual labor involved in these suggestion gathering endeavours. The problem the current system has is that nobody knows how many "dead" votes hang in there. A periodic reboot (maybe longer periods than months) would reduce this problem a bit.

[bluea]

Timestamp the vote and weight it with 'weeks since vote'.

"I voted this week" = full credit.
"I voted last week" = 95%
"This month" = 90
"This season" = 70
"Last six months" = 50

(Or pick a faster depreciation, whatever.) If you're hyper-partisan, you can revote all you like for the same thing and always have your vote count 100%. But even just once a month or so gets you -most- of the way there. And you vote still counts for something even if you're infrequent.

Things like:

Code: [Select]

12. (176)  [Resolved] Designate Safe Area
Would automatically be migrating lower and lower. (People re-voting would see "Resolved" and the additional notes. The 176 votes that are still there are many months old at this point.)
--
On a separate note:
Would it be possible to for the user-facing form to have a checkbox (or something) that allows some sort of feedback on whether an item should be [Resolved]? With the possibility of submitting URLs?

Like item #20: Rope Ladders. No, they aren't going to be in this release. But the major game impact is the ability to build down - and that is going to be in (IIRC). An automated note such as:

Code: [Select]

27 people claim that a significant fraction of this development item should be considered RESOLVED,
and this URL has been provided as reference.

That isn't a "Revote now!" instruction so much as "Rethink the importance of this entry after reading this."

[Draco18s]

Things like:

Code: [Select]

12. (176)  [Resolved] Designate Safe Area
Would automatically be migrating lower and lower. (People re-voting would see "Resolved" and the additional notes. The 176 votes that are still there are many months old at this point.)

FYI, I own that one, and any other I've marked as "resolved" will be deleted and re-added as "completed" (thus clearing the votes) once the new version comes out.  It doesn't stop people from voting for it even then, but would indicate to people that it was recently dealt with and likely will not be getting attention in the near future.

I would also PM the voters--if I knew who they were--asking them to re-cast their votes.