Thread: Maemo 5 design decision: call lists (was: Wired Magazine - hands on with the n900)
View Single Post
TheLongshot is offline TheLongshot
2009-10-28 , 16:59
Posts: 234 | Thanked: 160 times | Joined on Oct 2009
#87
Originally Posted by GeneralAntilles View Post
Unfortunately this is a self-fulfilling prophecy. People get irritated because Nokians generally refuses to interact with us, so more Nokians will refuse to interact with us, so people get more irritated, etc.

Once again, broken process. Broken process. Broken process.

It's not our fault if the way management has set things up puts you in between a rock and a hard place. Obviously that needs to be fixed, but you can't blame the current situation on us. Nokia has a pretty clear track record of not getting how to handle an open source community (see the Bugzilla Fiasco that's been ongoing since 2005) and the irritation you see here is simply a side-effect of that. Treat people with respect and you get respect in return. It's a two-way street.
As a software engineer by trade, I can understand having a level of indirection between the developers and the customer. Fact is, customer requests CAN get in the way of a developer doing his job, depending on how combative the customer is. There aren't usually problems if the customer is well behaved, but when they are not, it can turn into a mess. That's why I find the request for 'transparency' being something that isn't all that attractive to the developers. The indirection allows them to get the work that they need to get done, done without outside interference. It is up to management to interface with the bug list and set priorities of items on the list based on difficulty and overall usefulness of any fix to the general community.

You might not agree with the priority list, but in the end you are just one stakeholder out of many and the team may have bigger fish to fry that affect more users than just yourself.