It may make sense to provide much more weight to the latest N reviews, and a lot less to older, but still to add them into the mix. So your past will weight as well but you can correct your problems and get a better average review.
I like this idea. Software changes over time, so I always have to double-check the date when reading other people's reviews. Especially if the software is developed at a very fast rate, such as Redis.
Another option would be to provide a history of average star ratings, similar to the 52-week activity graph. Then people would be able to see, for example, that most reviews have turned positive since the v2.5 release, etc. Tie reviews to versions and/or commits, and allow people to post another review after X weeks, so that the same person can post different reviews of different versions of the same program.
Comments
It may make sense to provide much more weight to the latest N reviews, and a lot less to older, but still to add them into the mix. So your past will weight as well but you can correct your problems and get a better average review.
I like this idea. Software changes over time, so I always have to double-check the date when reading other people's reviews. Especially if the software is developed at a very fast rate, such as Redis.
Another option would be to provide a history of average star ratings, similar to the 52-week activity graph. Then people would be able to see, for example, that most reviews have turned positive since the v2.5 release, etc. Tie reviews to versions and/or commits, and allow people to post another review after X weeks, so that the same person can post different reviews of different versions of the same program.