Re: Fwd: Hayes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday January 27, 2003 12:55, Rob Kaper wrote:
> Neil wrote Hayes without implementing a part of the API completely,
> properties, because he's he claims he  doesn't like the concept of
> properties.  Properties are like X-atoms.  Any plugin should be able to
> set a key-value pair, like "copyright"->"Virgin Schallplatten GmbH". 
> Neil decided that he doesn't like this, so basically, setting a property
> results in nothing happening.

This is only half-true.  Previously, in an attempt to compromise, I 
implemented these dictionaries so that they would be saved for the life of 
the application.  They just wouldn't be saved after the app quit.

Charles disabled Hayes from release even after this.

> So then, I finally get Neil to make property support optional, and he
> implements another feature, which allows you to add a file to Hayes
> right from a Konqueror context menu (indeed a nice feature!).  It
> communicates to Hayes via its own DCOP interface, rather than using
> Noatun's own dcop interface function "addFile".  Mind you this item
> appears on the Konqueror context menu even if Hayes isn't loaded. Ok,
> very well, I'll just ask Neil to change it to use the noatun function. 
> Turns out he didn't implement the noatun function, because he didn't
> like the *name* of the function addFile. Not only this, but he wrote
> hayes before we released 3.0 (and hence before I started keeping Binary
> Compat), so he had ample time to tell me he didn't like the name
> "addFile" and to suggest an alternative.

Adding a file and playing a file are two completely different things.  
That's why I "didn't like the name."

But here's the issue Charles seems to have forgotten to bring up:  Hayes 
was created and developed in CVS, in kdemultimedia.  But Charles, as 
Noatun maintainer, decided it was unfit for release.  So we moved it to 
kdeaddons.  But Charles also claims that as Noatun maintainer, he decides 
what goes there and what doesn't.  So I cvs removed the app, because after 
three people enabling the app (me, Rob Kaper, Kevin Puetz) it was clear 
that Charles was decided on the matter.  And with the option of separate 
releases available, it wasn't worth it to me to fight.

So, then comes Hayes 1.2, which included some very nice optimizations by 
Carsten Pfeiffer.  Carsten has asked me to return Hayes to CVS, giving me 
his opinion that Charles doesn't have control over kdeaddons.  Not knowing 
what people think, I asked kde-multimedia for opinions.

So now here we are in kde-policies, with a simple question:  Does the 
maintainer of a plugin-based application have veto power over what plugins 
get included in the release?  And does that veto power carry over to the 
kdeaddons package of extra plugins, too?

- -- 
Neil Stevens - [email protected]
"Distinctions by race are so evil, so arbitrary and insidious that a
state bound to defend the equal protection of the laws must not allow
them in any public sphere." -- Thurgood Marshall
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+Nb3Lf7mnligQOmERAm9JAJ986NFtrfPXhDsQbz0fdujf/fM21gCffstP
WMxcYqiy7bJDnaolqVCH5Fw=
=xvrQ
-----END PGP SIGNATURE-----