faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: KDE-PIM meeting and akonadi
by Breco Pol on Sunday 03/Feb/2008, @04:25
|
Dear Aaron,
you really do not want to experience corporation communication, I'm afraid. It will definitely not result in 100% communication, unless you mean just babbling without reasoning. Trust me, I have first-hand experience on such things in a large corporation.
For instance, marketing thinks about this and that, writing system requirements which try to even control which technology should be used instead of focusing on functionality. Marketing also requires conflicting and unresolvable goals to be realized simultaneously and has no problems in communicating this to 100%. Architecture and development then have to see how to make the best out of this. They are communicating back to marketing all the time but the goals set within marketing lead to completely ignoring feedback. Next, development ignores requirements, doing what they think could be great. No more communication then. And so on.
I'm not saying that only one of the groups involved is wrong; there are mistakes in all fields and on all levels. But that is exactly what is corporation communication. And it would be sad if KDE would just end up with this kind of corporation communication. My hope is still that the incentives within the KDE development are differently enough from the usual corporation incentives that the development model including marketing, product management, architecture, development, and system test actually works better than in the ordinary companies. |
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
