AUR web interface

Tasklist

FS#3007 - autovote on own packages

Attached to Project: AUR web interface
Opened by Hugo (Citral) - Friday, 29 July 2005, 23:05 GMT
Last edited by Callan Barrett (wizzomafizzo) - Thursday, 27 March 2008, 09:13 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To Paul Mattal (paul)
Architecture All
Severity Low
Priority Normal
Reported Version 1.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

As I issued this thought in this thread:
http://bbs.archlinux.org/viewtopic.php?p=104718&sid=510e081b1d9ff2e27a7f46a14f44a498#104718
I decided to make the bug report too.

I don't know how your (you the AUR admins) view is on this.

But I'll just copy my opinion from the thread:

It just doesn't feel right that some packages get voted by their maintainers, while most packages are not (because the maintainer can't be bothered).

IMO when you add a package, you should automatically get your own vote on it. Or disable voting on your own packages.

I mean, would you ever add a package, and explicitly not want to vote for it? You can "unvote", if you really want to.
Also when I use an App from AUR that I like, and I see it has 0 votes, I'm like, why should I bother voting for the package if the maintainer himself hasn't even bothered?
Some people are too humble to vote on their own packages, and most are just too lazy.
This task depends upon

Closed by  Callan Barrett (wizzomafizzo)
Thursday, 27 March 2008, 09:13 GMT
Reason for closing:  Won't implement
Comment by Simo Leone (neotuli) - Friday, 12 August 2005, 04:51 GMT
If it was an auto vote, then every package will have at least one vote. Which is stupid. I'd rather make it so that the submitter/maintainer CANT vote for their own package, that'd effectivly do the same thing as implementing an auto vote.
Comment by Hugo (Citral) - Friday, 12 August 2005, 15:06 GMT
As I said, I'm happy with that too, and I agree that it's the best way to go.

Some people on the forum thread uttered the concern that they sometimes don't want to vote for their own packages/don't believe it's community-repo worthy. But if it's really a that big issue for them, they can simply ask in the package comments for people not to vote on it.
Comment by Paul Mattal (paul) - Thursday, 18 August 2005, 15:19 GMT
I, too, like this solution. It seems more appropriate.
Comment by Simo Leone (neotuli) - Sunday, 25 September 2005, 17:05 GMT
Notes/checklist to person that may implement this (maybe myself):
-Don't allow a vote for own (maintained) packages
-Have to manually go through and destroy all existing ones
-Check for vote on package at adoption, if user has voted on package and they want to adopt, delete vote. (avoid "submit, disown, vote, adopt" scenario to get around limitation)
Comment by Eric Belanger (Snowman) - Friday, 09 March 2007, 21:57 GMT
I know this is an old bug report but I think it is unecessary complication. The package maintainer's single vote will not make any difference wether the package goes in community or not because the "25 votes = community" is just a guideline. If a TU wants to add a package in community, he will do it wether the package has 24, 25 or even 20 votes.

Loading...