Fwd: Hayes

Rob Kaper kde-policies@mail.kde.org
Tue, 28 Jan 2003 01:15:05 +0100


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

On Tuesday January 28 2003 1:00 am, Charles Samuels wrote:
> > 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?
>
> And also, how does a kdeaddons module differ from its application's actual
> module?

Well, the name suggests it is an add-on and not part of the original 
application. You don't object to the Hayes stand-alone releases, so I can't 
see why you'd object to it being in kdeaddons.

Question: why must the playlist save meta file properties? To me, the playlist 
plugin is only responsible for maintaining a collection of files, the 
"playlist". What to do with those files should be solely up to Noatun.

(shit, how are we supposed to form policies without technical discussion and 
arguments included?)

Rob
- -- 
Rob Kaper      | From the mountains, to the prairies         ***** =========
capzilla.net   | To the oceans, white with foam              ***** =========
unixcode.org   | GOD BLESS AMERICA                           ===============
the-amazing.us | My home sweet home                          ===============
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+NcuJtppIl2G1SjcRAiTiAKCqxPqZyF9zzC7BVR6q/CTut9vYYgCgsY23
q1sjdlAm8m+0flVDrTvp7cU=
=jsu5
-----END PGP SIGNATURE-----