Redmine

Great!

Yuuki NARA wrote:

[...]

What do you think?

I think this and the other extended lists are an awesome source for finding the interest of the community. As such they are, I think, a very valuable contribution. Thanks for creating and sharing them.

Note: I'll set this topic to be sticky so it becomes easier to find.

Mischa, thanks for your comment and setting sticky.

I will post other lists , in a few days.

I hope everyone will be useful.

Released the remaining list.

Redmine.org incomplete tickets vote count lists as of 2017/1/7
Lists were split because there are many cases(over 900)

I hope this list will be useful

Yuuki NARA, thanks for creating these lists and for sharing them with the community. I'm wondering if it's easy for you to update these lists? I'm asking because Redmine 3.4.0 closed some of the most voted tickets.

Hi, Marius.

Thanks for your comment.

How about with the following correspondence?

I will delete items completed in 3.4 from vote count list.

I will not delete items completed in 4.0 .
Because it can not be used yet.

After Redmine 4.0 is released, i will Update the whole list.

Thanks.

Sounds good for me. I thought that you use a script or something like that to generate the reports, but if is only manual work, don't bother too much.

Hi, Marius.

I deleted items completed in 3.4 from vote count list.

I left only #10485.
Because it is schduled for treatment at Ver4.0

Most of the work is scripted.
But,it took me an hour to download 4700 issue XML files. (^^;

How about using number of watchers to correlate interest?

See Feature #17288 Use Watcher Count as a poor man's Voting system on redmine.org for a description of a simple implementation.

This woukd make it transparent, and avoid the +1 spam.

@ go2null A voting plugin is available, too and the original issue #1011 will have its 10th anniversary in April this year. It seems, there aren't many dwarfs left in the halls of Moria to hear your suggestion. Perhaps you would have more luck in the #IRC channel.

I updated vote count list.
This list is 2018 New Year version.

I will update this list,when Redmine4.0 released.

I separated one thing with +1 more than five and 1-4 things.
1-4 cases were sorted by category first, sorted by number of votes and update date and time.

Reason for division
· There are many proponents who have more than 5 cases, and it seems necessary to judge the contents on a case by case basis.
· It is easier to correlate in categories than one difference.

I discussed with Go.MAEDA and created note count list too.
RedmineOrg-IssueNotesCountList-20180708.xlsx

The number of issue comments express the lively activity of the discussion.
It is considered to be an index of interest concerning the contents of the issue.

I hope this will help.

Recently I started working on plugin that allows to vote on issues by sending crypto tokens. This way people can not only show interest in resolution of particular issue, but also incentivise it.

At this point plugin has very basic functionality. There is yet a lot to be done to use it in real life. But you can take a look at it: https://www.redmine.org/plugins/token-voting

I would be happy to work on it further if there is interest.

I created a prototype site of the ticket voting function of the Redmine.org site.

I will let it run during November.
Please try operation.（vote,comment,, available)
I am waiting for your comments.

The contents I carried out are as follows.

Copied the redmineorg ticket.
Gathered plus 1 of the existing ticket.
Ticket vote function added.
(For each ticket, one vote is possible for each login ID)

For the Vote function, we used the following plug-in.
https://github.com/ojde/redmine-vote_on_issues-plugin

The site URL are as follows. (Operating in 2019/12/22
http://demo1.unofficial-redmine.org/redmine/projects/redmineorg-copy/issues

URL as of 2018/12
http://150.95.132.208/redmine/projects/redminet15-orgcopy/issues

Yuuki NARA wrote:

(For each ticket, one vote is possible for each login ID)

One downside of such solution is that people can be motivated to create multiple accounts to upvote tickets of their interest/downvote others.

crypto gopher wrote:

One downside of such solution is that people can be motivated to create multiple accounts to upvote tickets of their interest/downvote others.

That's right.

However, it is still possible to increase the number of Votes by using multiple IDs, even now.

This method can be easily executed, and fairness among tickets can be secured.

Please tell me if there is any other good way.

Yuuki NARA wrote:

Please tell me if there is any other good way.

I'm not saying that this method is inappropriate for Redmine. It may work depending on community culture.

I think that robust voting system should rely on some scarce resource to provide reliable results. Voter identity ('account') is to some degree scarce - as it requires time (which is strongly limited) to create additional identities. Still the relatively short time needed to create identities may set this price on too low level.

Best idea that I can think of at this point is to vote with crypto tokens (given that they are limited or have any economic value). I posted it here in #29758. I also wrote a proof of concept plugin https://www.redmine.org/plugins/token-voting. You may want to have a look if you didn't see it before.

Nice post thanks for this.

crypto gopher wrote:

Best idea that I can think of at this point is to vote with crypto tokens (given that they are limited or have any economic value). I posted it here in #29758. I also wrote a proof of concept plugin https://www.redmine.org/plugins/token-voting. You may want to have a look if you didn't see it before.

It's cool idea, however, it turns a voting system into something more sophisticated than it has to be while also making people deal with bitcoins, which seems sketchy for sure.
I believe the identity duplicate protection should not be implemented in the voting system itself, it should be implemented on the level of registration process, which should consist of following layers:
1. Easy integration of own reCaptcha via Google to filter bots.
2. Easy integration of own 2FA via Google or MS in the core Redmine, and then to fill phone number and confirm it at least once would need to be required during registration. Then obviously it would then not allow another user with the same phone number.

I think keeping it simple as Yuuki NARA suggested in the prototype would be the best.

This message is Redmine.org incomplete tickets vote count lists as of 2019/12/22
Redmine 4.1 release anniversary and Happy New Year 2020 edition. :-)

...
If it is longer than this, it will be treated as SPAM and registration will fail, so I registered on another site.
Please refer to the following.

https://redmine.tokyo/issues/1069

I think that robust voting system should rely on some scarce resource to provide reliable results. Voter identity ('account') is to some degree scarce - as it requires time (which is strongly limited) to create additional identities. Still the relatively short time needed to create identities may set this price on too low level.