Re: [Ekiga-list] [GUADEC 2013 Proposal]

[Jim Diamond <Jim Diamond acadiau ca>]

On Wed, May 15, 2013 at 18:51 (+0200), Víctor M. Jáquez L. wrote:

> On Wed, May 15, 2013 at 06:32:27PM +0200, Genghis Khan wrote:
> > Hello,

> > On Wed, 15 May 2013 14:07:45 +0200
> > Víctor M. Jáquez L. <vjaquez igalia com> wrote:

> > > On Wed, May 15, 2013 at 01:55:45PM +0200, Damien Sandras wrote:
> > > > Bad news.
> > > >
> > > > That probably means GNOME has now less or no interest in Ekiga
> > > > anymore.

> > > Yes, though, it is a fact that we are not keeping the pace of gnome,
> > > with it's library dependencies and user interface design.

> > What exactly is missing or wrong in Ekiga?

> There's nothing missing or wrong in Ekiga per se. 

> But if we want to think in Ekiga as a component of GNOME (3.x) we shall admit
> that Ekiga doesn't follow the UI design and the migration to GTK+ 3.x,
> GSettings, GStreamer, etc., is a bit lagged behind.

Speaking as a voice on the side... why do we/you/... want ekiga to be
a gnome component?  Why not a generic program which is independent of
any desktop environment?

(I'm not bad-mouthing gnome 2 or gnome 3; I do prefer gnome 2 to kde.
However, as a non-gnome desktop environment user (Slackware dropped
gnome many years ago), the "gnome" aspects of (first gnomemeeting and
then) ekiga have caused me considerable amounts of grief over the
years.  In particular, gconfd has caused lots of problems, and it is
unclear to me what the benefits are, in particular for people who
don't use gnome as their DE.)

As an(other?) example, I am having no luck when behind a NAT router.
I see no gui option to set up STUN.  I search the web a bit and find
out I need to use gconf-editor.  Too bad that it doesn't exist on
slackware, since (presumably) there is no gnome.  Ho hum.

                                Jim