glib in kdesupport: yes or no?

Stefan Westerfeld stefan at space.twc.de
Mon Mar 10 06:20:29 GMT 2003


   Hi!

On Mon, Mar 10, 2003 at 12:50:02AM -0500, Havoc Pennington wrote:
> Keep in mind a couple of things, 1) D-BUS is maybe 30% done if that
> and still open to large changes 2) there were more KDE developers
> initially involved than GNOME developers, quite a few people (a
> dozen-ish I think?).  The whole thing was more or less Matthias
> Ettrich's idea as I understand it, though he hasn't had a lot of time
> to work on it.

Stop with that useless piece of thinking seperation. Read this:

Keep in mind a couple of things, 1) D-BUS is maybe 30% done if that
and still open to large changes 2) there were more GNOME developers initially
involved than GNOME developers, quite a few people people. The whole thing
was more or less Matthias Ettrichs idea, as I understand it (hereby labelling
Matthias Ettrich implicitely as GNOME developer), though he hasn't had a
lot of time to work on it.

> I've been relying on the KDE developers involved to tell KDE about
> D-BUS, rather than doing it myself; I have my hands full selling it to
> GNOME as some may have noticed if you lurk on our flamewars. ;-) But
> I'd be happy to do a 'briefing' for this list.

I've been relying on the GNOME developers involved to tell GNOME about
D-BUS, rather than doing it mysself; I have my hands full selling it to
GNOME as some may have noticed if you lurk on our flamewars. ;-). But
I'd be happy to do a 'briefing' for this list.

> We'd still be eager to make *any* changes that will
> be desired for KDE adoption.

We'd still be eager to make *any* changes that will be desired for GNOME
adoption.

> An important question for KDE is.
An important question for GNOME is, ...

Do you see why you're making no sense here? You're implicitely projecting
a "we" "they" split on the world in every word you say and every thought
you have. This can not help. If you want KDE and GNOME to interoperate
really well, consider them as the same thing, and put your workforce in
doing things that are ideal for both projects, not only for one of this.

Give up your identity as GNOME developer (where as GNOME is somewhat
implicitely defined by "a desktop that has been written to avoid KDE due to
licensing issues"), and become a KDE developer as well. Ultimately consider
these two things the same thing. Then you will work as person who benefits
both projects, and will gain the reputation that you need to really guarantee
interoperability.

If you win support in GNOME but not in the KDE, nothing will happen. If you
win support in KDE, but not in GNOME, nothing will happen. You can forget
working on interoperability without support and reputation. So work equally
concentrated on attaing this within KDE as you work on attaining this in
GNOME. 

But this is just a hint, and my understanding may be limited ;).

   Cu... Stefan
-- 
  -* Stefan Westerfeld, stefan at space.twc.de (PGP!), Hamburg/Germany
     KDE Developer, project infos at http://space.twc.de/~stefan/kde *-         




More information about the kde-core-devel mailing list