MrSinatra;695845 Wrote: > > you say votes and forums etc are no good for the devs to take cues > from... so just how then do you propose they do it? u make some valid > points but you seem to have a defeatist attitude. i don't mean that in > a personal way, but when you say "you've given up" etc it seems that > way. they used to ENCOURAGE VOTING, like Chris Owens, logitech > employee, remember him??? now thats no good? > I think votes is a good way for people to tell Logitech what they wish to be implemented, so people should vote and Logitech does include votes as one factor when they consider if something should be implemented.
But I don't think you can trust votes strictly as long as it's as hard as it currently is to vote, you need to register a separate account and you need to find the bug among the thousands of bugs available in bugzilla. The reason some bugs have more votes than others are often that they have been promoted by someone in the forum to make people realize the bug exist and is possible to vote on. Also, I would suspect that it's probably less than 5% of the Squeezebox owners that spend time on this forum on weekly basis and of those 5% only a small sub set is registered in bugzilla so they can vote on bug reports and enhancement requests. It's easy to think that all Squeezebox owners read this forum every week because most of the experienced community members do, but in reality this isn't the case. Also there are probably a lot of users that doesn't even have a forum account but still reads the forum without being registered on it. MrSinatra;695845 Wrote: > > i haven't given up in the sense that i do think a reasonable, > non-personal argument can be made that the devs, who btw WORK FOR > LOGITECH, (i don't accept this deflection argument of good guys vs bad > guys, which is insane in a corporate environment, you all are one > entity imo), should takes cues to the roadmap from votes for bug > tracker. how is that not reasonable? michael says they do, but when u > have a bug like 142 sit DEAD for as long as it does, how can anyone > believe that? > 142 is not a bug, it's an enhancement request. It's pretty obvious that Logitech and Slim Devices have decided to stay away from smart playlists and this also makes ratings completely uninteresting as their primary usage is together with smart playlists. In my mind, both 142 and 380 needs to be implemented to get something that's useful, else they will still have a dependency to third party solutions. I've probably caused this scenario partly myself since the need become less obvious when there was a working third party solution through TrackStat/SQLPlaylist in 2006. Maybe it would have gotten higher priority if I hadn't released TrackStat/SQL Playlist, I don't know, but the main reason I released them was because I wanted to show the potential and I wanted the functionality myself and didn't want to wait for Slim Devices to realize it was important. MrSinatra;695845 Wrote: > > frankly, it seems to me it is completely reasonable to suggest that > they could implement ONE top ten voted bug per official release. > Reasonable, yes, but you won't get any commitment, in same way as you won't get any commitment from Apple, Microsoft, Sonos, Google or any other serious company regarding new features. What you will get is what Michael already has said, they will consider the votes when deciding what to include. The reason enhancements like 142 hasn't been implemented is strategically, it's not because they don't care about votes, the same thing is also the reason for the top most voted feature regarding Grooveshark (which is related to legal issues). I would guess that most of the bugs/features on the top 10 list have a reason why they haven't been implemented, either it's not in line with Logitech strategies or they have negative side effects for some user category or they require a large development effort but won't generate enough revenue. Personally I would prefer that Logitech just closed enhancements they don't plan to fix with a "Won't fix" resolution, because that would make it clear for everyone what the strategy is, but in reality I understand why they don't want to do that because it will make some people upset when someone says that their favorite bug/enhancement won't be fixed, it causes less critique if they just ignore it. Target Milestone = "Future" or "New Schema" does in reality mean the same thing as "Won't fix" in most cases, at least in my mind. As a side note, the Spotify enhancement request got exactly 100 votes and that one got implemented, so did a number of other bugs which also have a lot of votes: http://bugs.slimdevices.com/buglist.cgi?query_format=advanced;votes=10;bug_status=RESOLVED;bug_status=VERIFIED;bug_status=CLOSED;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc;resolution=FIXED So I guess this could be an indication that they do care about votes. -- erland Erland Isaksson ('My homepage' (http://erland.isaksson.info)) (Developer of 'many plugins/applets (both free and commercial)' (http://wiki.slimdevices.com/index.php/User:Erland). If you like to encourage future presence on this forum and/or third party plugin/applet development, 'consider purchasing some plugins' (http://license.isaksson.info)) Interested in music discovery ? See 'Social Music Discovery (SMD)' (http://forums.slimdevices.com/showthread.php?p=656713) project. ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=94109 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
