Re: KDE-PIM meeting and akonadi

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: KDE-PIM meeting and akonadi
by Aaron Seigo on Saturday 02/Feb/2008, @16:09

It would be great if people would actually be realistic about things when making such comments.

It's not easy to keep all communication 100% up everywhere as long as we remain a distributed, open project. So being like a corp would actually *fix* that.

It's also pretty cool that developers are still in charge and make decisions like "akonadi after 4.1" if that's what makes sense. Again, not very corp like letting the engineers writing the code to set the pace of things so freely.

Instead of trying to see all that as a bad thing, perhaps you might consider seeing it as the result of an open devel process that gets better (not to mention Free) technology to your doorstep.

Cheers ...

Related Links

·   Articles on KDE in the News
·   Also by Aaron Seigo
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: KDE-PIM meeting and akonadi
by Chris Samuel on Saturday 02/Feb/2008, @20:20

I find your faith in corporate communications disturbing.. :-)

[ Reply To This | View ]

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.

[ Reply To This | View ]

Re: KDE-PIM meeting and akonadi
by Birger on Monday 04/Feb/2008, @04:32

:-)

It's refreshing to see such great enthusiasm for the corporate model Aaron. But from my own experience in rather huge development groups, it's far worse than the communication within KDE.

cu / ....

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"You would know that after informal research, KDE developers prefer tea!" -- Roberto Alsina
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.