Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate rating aside popularity #32

Open
AntoineTurmel opened this issue Nov 19, 2012 · 6 comments
Open

Integrate rating aside popularity #32

AntoineTurmel opened this issue Nov 19, 2012 · 6 comments

Comments

@AntoineTurmel
Copy link
Contributor

It would be cool for user to be able to rate plugin. It could be done either by modification of pluginrepo or installing rater plugin

@selfthinker
Copy link
Collaborator

Generally a good idea. In order to prevent misuse only logged-in users should be able to rate. And they should only be able to give 1 rating, but re-rating (and removing the former rating) should also be allowed.

But I am against using any additional plugins, as the pluginrepo plugin should work on its own and we shouldn't use any third-party plugins on dokuwiki.org unless it's from a trusted source and/or its code has been checked. (I'm not saying you cannot trust the rater plugin, I'm just saying we don't know that yet.)

@AntoineTurmel
Copy link
Contributor Author

Agree, which type of vote should we keep ? I like the 5 ⭐

@splitbrain
Copy link
Collaborator

I'm not convinced that rating is a good idea. I'd assume a majority of our users would not be able to differentiate a bad plugin from a good one. All they can see is if it work or not. And that feedback is already collected by popularity.

@selfthinker
Copy link
Collaborator

I used to agree with @splitbrain, but now I don't. It's because there simply is no fair way of evaluating the value of a plugin. The number of installations (aka "popularity") is not entirely fair either (i.e. it will also not be able to tell you which plugins are good or bad). Yes, a rating system will not be entirely fair as well. But at least the combination of those two makes it more realistic.

Additionally to that, I would like to have "recommended" flags, which are only editable by the core team. Not sure how that can work, though? The way the plugin works right now, I don't think something like that would be easy to implement.

Maybe we should just try out a rating system and see how it works out? We can still remove it again if they turn out to be too similar to the popularity data.

@splitbrain
Copy link
Collaborator

Yeah maybe. I'm not convinced but I'm fine with trying it out. However I think #25 is way more important than all the other changes (though I guess @GeekShadow's priorities may differ here).

@AntoineTurmel
Copy link
Contributor Author

@selfthinker
+1 for recommended flag, maybe it can be saved in the configuration just like "bundled" plugins ?

@splitbrain
Table view redesign would be good too, I have to give a shot when I got time ;)
Again, I'm filling issues for things that would be nice for the pluginrepo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants