Re: Proposed module: empathy

[Xavier Claessens <xclaesse gmail com>]

Le lundi 24 décembre 2007 à 12:48 +0000, Gustavo J. A. M. Carneiro a
écrit :
> I would just like to say that I am concerned about telepathy storing
> unencrypted passwords in GConf instead of GnomeKeyring.  GNOME modules
> should be taking security more seriously, IMHO.

It is not empathy's responsibility to store account parameters,
MissionControl does that job but unfortunately it does not uses gnome
keyring :(

> On Thu, 2007-12-20 at 04:52 +0100, Vincent Untz wrote:
> > Homepage: http://live.gnome.org/Empathy
> > svn/git/bzr/...: http://svn.gnome.org/viewcvs/empathy/
> > Proposal on d-d-l: http://mail.gnome.org/archives/desktop-devel-list/2007-September/msg00301.html
> > 
> > Short description:
> > ==================
> > Empathy consists of a rich set of reusable instant messaging widgets,
> > and a GNOME client using those widgets. It uses Telepathy and Nokia's
> > Mission Control, and reuses Gossip's UI. The main goal is to permit
> > desktop integration by providing libempathy and libempathy-gtk
> > libraries. libempathy-gtk is a set of powerful widgets that can be
> > embeded into any GNOME application.
> > 
> > Requires new external dependencies:
> > ===================================
> > libtelepathy, telepathy-glib, libmissioncontrol
> > (libtelepathy will go away at some point in the future)
> > 
> > Summary so far:
> > ===============
> >  + a few -1 from people thinking it's useless duplication of
> >    pidgin/ekiga/etc. work or not wanting to use telepathy
> >  + some +1 from people thinking it's going the right way
> >  + questions about stability
> >  + questions about feature set that might not be complete yet
> >  + API documentation needed to be written (I don't know the
> >    current status)
> >  + no API stability guarantee yet
> >  + current license of the libraries is GPL
> >    [context: if the libraries are proposed for the platform later, they
> >    will need to be LGPL]
> > 
> > Xavier can probably send an update about the feature set, the API doc
> > status, and the license.
> > 
> > Vincent
> >