Re: Re: [Telepathy] Telepathy Status
Mikael Hallendal <[email protected]> Wed, 11 Oct 2006 14:41:37 +0200
| Newsgroups | gmane.comp.gnome.gossip.devel |
|---|---|
| Message-ID | <[email protected]> |
Xavier Claessens wrote: > Le mercredi 11 octobre 2006 à 14:13 +0200, David Nielsen a écrit : >> ons, 11 10 2006 kl. 13:59 +0200, skrev Xavier Claessens: >>> Le mercredi 11 octobre 2006 à 12:26 +0100, Dafydd Harries a écrit : >>>> Ar 09/10/2006 am 21:23, ysgrifennodd Eitan Isaacson: >>>>> * We are right now building a vertical solution in the sense that we are >>>>> managing accounts, connections, contacts, and incoming channels all in >>>>> the same process. If we are truly subscribing to the telepathy way of >>>>> life we need to redefine the goals of gossip. Telepathy dictates that >>>>> there should be something called mission control[3] that will do all the >>>>> background handling of connections and account settings and delegate >>>>> actual communications to separate channel handlers, so these are some >>>>> options I see: >>>>> 1. separate gossip in to two processes, mission control, and everything >>>>> else. >>>>> 2. stay monolithic, and delegate unhandled channels to external >>>>> handlers. >>>>> 3. size down to a roster and IM interface. >>>>> 4. combination of 2 and 3, be a self sustaining process with an option >>>>> of cooperating with an MC. >>>>> Just thought I would throw that out there and hopefully flare up some >>>>> discussion :) >>>> One way forward would be for Gossip to implement the MC API, and for MC to be >>>> split into a separate component later on. >>>> >>>> There was a lot of enthusiasm at Boston for the Telepathy port of Gossip, and >>>> it was suggested that we propose it for inclusion in Gnome 2.18. If we want to >>>> do this, we should do it right now -- I think the deadline for proposals is >>>> the 13th. I personally feel this is a good idea: getting Gossip with Telepathy >>>> support into Gnome would be a major boon to both Telepathy and Gnome. If >>>> inclusion is rejected, we can always re-propose it for 2.20. Either way, not >>>> having MC as a separate component should not block Gossip's adoption by Gnome. >> As a user I'd love to see the functionality Gossip offers in my GNOME >> desktop and I know many others who feel the same way thus I'd be all for >> proposing Gossip for inclusion in 2.18. >> >> - David Nielsen > > Personally I doubt gossip-telepathy would be ready for 2.18, but I'm all > for consider it for 2.20 :-) > > There is not only gossip which isn't ready, telepathy-[gabble, > butterfly,...] aren't feature-full at all, and I don't even speak about > stability. Agreed, this doesn't sound very feasible from a number of perspectives: * Feature/UI stability of Gossip, we are constantly changing the UI of Gossip and having it as part of GNOME would mean a lot of extra work load and restrictions to this. (This goes for both branches of Gossip but even more so for the Telepathy branch). * Feature completion of Telepathy, my understanding is that there are a bunch of things lacking in order to make Gossip/Telepathy have all the features of current Gossip. * Untested/Experimental stack, Telepathy, Telepathy Jabber implementation and Gossip/Telepathy involves a lot of new and largely untested code. * Time frame/resources, there aren't enough resources in the Gossip project for this kind of commitment. Best Regards, Mikael Hallendal -- Imendio AB, http://www.imendio.com/