From kde-core-devel  Wed Jul 30 07:08:04 2003
From: Ralf Nolden <nolden () kde ! org>
Date: Wed, 30 Jul 2003 07:08:04 +0000
To: kde-core-devel
Subject: Re: Drafting a policy? [was: Re: Qt 3.2 requirement]
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=105954894407849
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-02=_U72J/2L5jatcryA"


--Boundary-02=_U72J/2L5jatcryA
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Mittwoch, 30. Juli 2003 02:25, Cornelius Schumacher wrote:
> On Wednesday 30 July 2003 02:06, Daniel Molkentin wrote:
> > Hi Guillaume, thread-participants,
> >
> > On Wednesday 30 July 2003 00:04, Guillaume Laurent wrote:
> > >No. Ask a user which one he prefers :
> > >
> > >- get a better, more stable desktop in a shorter time, at the
> > > expense of upgrading some basic libs
> > >
> > >- get a buggier, less stable desktop in a longer time, but you won't
> > > have to update some basic libs.
> >
> > Nice set of questions ;) Why do you ask them if you choose them in a
> > way they are bogus to ask? Sounds like you missed a carrier as a
> > politican...
> >
> > This all sounds like somebody (or some group) should sit down and
> > think about how such a thing could be realistically turned into
> > practice for KDE. Next step would be to post the results to
> > kde-policies where they should be discussed. If the result finds a
> > consensus, we should try to deploy it. We don't really have anything
> > to loose at that point, except for maybe some time. But I think we
> > can afford that. We should test it a bit in the 3.x phase and - if it
> > is useful - deploy it for 4.0. This is not meant as a policy that
> > should demotivate developers. It's in contrary something that should
> > enable the developers to employ certain techniques that help with the
> > issue. People were able to learn about and adapt d-pointers and other
> > BC- keeping measures, why not this?
>
> If Guillaume has missed a career as politician, you have missed a career
> as bureaucrat ;-)
He, he can still become one, just become a Debian developer and you're on t=
he=20
best way :-))

> Setting up policies for KDE doesn't work. Never. The only thing that
> works is to put that what is already common sense among KDE
> contributors into a policy. In this case I would consider it hopeless
> to even try it.
And it would be wasted time anyway.

BTW: why do we have a release coordinator to decide about such things ?=20
Stephan ? :-)

Ralf

=2D-=20
We're not a company, we just produce better code at less costs.
=2D-------------------------------------------------------------------
Ralf Nolden
nolden@kde.org

The K Desktop Environment       The KDevelop Project
http://www.kde.org              http://www.kdevelop.org

--Boundary-02=_U72J/2L5jatcryA
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA/J27Uu0nKi+w1Ky8RAvNMAJ9blppdFp03QLYJb/hpyPcFwk/MRQCeL0Ui
p7mY2hFSFH0BHcQBeI4SbX0=
=qNs2
-----END PGP SIGNATURE-----

--Boundary-02=_U72J/2L5jatcryA--