Proposal: KDE CVS Commit Policy

[Neil Stevens]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday March 31, 2003 02:05, Dirk Mueller wrote:
> On Son, 30 M=C3=A4r 2003, Neil Stevens wrote:
> > 14. Lack of openness about conflicts of interest.  People abuse
> > various positions of trust to favor particular vendors at the expense
> > of the greater community.
>
> I don't know what you mean. Care to make an example?

Being unable to read minds, I cannot point to any one example decision and=
=20
prove that it was altered by a conflict, but here are some kinds of=20
potential conflicts KDE sees all the time:

The desires of certain vendors to merge KDE and GNOME possibly leading to=20
undiscussed and at times large changes to KDE services.

The desires of certain vendors to have binary packages possibly leading to=
=20
undiscussed and even undisclosed delays in KDE releases.

The desires of certain vendors to have advance notice of security problems=
=20
possibly leading to covered-up bugs.

The desires of certain vendors to have KDE make certain use of certain=20
libraries possibly leading to breakages of compatibility.

> Also, why do your 2 points belong into a CVS commit policy ?

It doesn't, any more than your point on "direction" does.  That point I=20
read as you saying developers should *take* more direction, and this was=20
my rebuttal of that.

=2D --=20
Neil Stevens - neil@qualityassistant.com
"The shepherd drives the wolf from the sheep's throat, for which the
sheep thanks the shepherd as a liberator, while the wolf denounces him
for the same act as the destroyer of liberty." -- Abraham Lincoln
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+iDrXf7mnligQOmERAlA3AJ4nj5cDulZJzl3rnZnNefCts8FQsgCeOTu0
WvYEFAEd5WGUjhq5RqqTYQU=3D
=3DW4+8
=2D----END PGP SIGNATURE-----