faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: KDE-PIM meeting and akonadi
by KDErocker on Saturday 02/Feb/2008, @11:05
|
Hehe. KDE is acting like a real company now.
The guy from the marketing working group is promising exciting new 4.1 features to the press.
And the developers are blogging that the timeline is not realistic. And the feature has to postponed to 4.2
Funny :-) |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: KDE-PIM meeting and akonadi
by anon on Saturday 02/Feb/2008, @12:40
|
Same for Decibel, it is listed on techbase as a 4.1 feature even if the project is totally unmaintained and has been so for many months already. It would be great if KDE could stop acting like a coorp and not make promises it can't keep.
|
[
Reply To This | View ]
|
Re: KDE-PIM meeting and akonadi
by Anon on Saturday 02/Feb/2008, @12:54
|
Looks like work on Decibel is *just* beginning to resume after a very long lapse:
http://cia.vc/stats/project/kde/decibel
So things are looking a bit more promising, on the Decibel front - thankyou, Tobias :)
|
[
Reply To This | View ]
|
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 ...
|
[
Reply To This | View ]
|
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 ]
|
Re: KDE-PIM meeting and akonadi
by Tobias on Monday 04/Feb/2008, @04:17
|
Hey, nobody had any requests for me to update decibel, so I did not do it:-) Porting KCall to it was pretty straight forward, so I am mostly happy with what I got (at least for the few use cases we are supporting so far).
I recently had some patches coming in (which got commited ASAP) and now that KDE4 integration is looming up ahead I really do need to fix the KDE integration issues that is still open. Apart from that I am waiting for feedback on what needs improvements and which features should get added (I am sure there still is much to do!). One of the design goals is to keep the decibel daemon (which is a network-accessible service after all) as simple and compact as possible. So just adding functionality that might be needed is not the way forward.
My other decibel related tasks are:
* Updating telepathy-qt to the newest telepathy spec. Unfortunately that is basically a rewrite. We need to come up with a better way to keep telepathy-qt up to date!
* Add profile support to tapioca-qt. Once that is done it should be visible in Decibel automatically.
* Write some more KCM modules.
* Blog about the kwallet support added by George Goldberg. I hate blogging.
* Update the decibel web site. I hate that even more than blogging.
PS: Help and patches are very welcome.
Best Regards,
Tobias
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|