Drafting a policy? [was: Re: Qt 3.2 requirement]

Bernhard Reiter bernhard at intevation.de
Wed Jul 30 14:57:55 BST 2003

A coordination overhead cannot be avoided if the effort
itself gets bigger or more important. 

And the problems this thread has grown out of
do exist on a technical level in practice.
It is clear from the discussion that a solution
can only be found on the non-technical level.

On Wednesday 30 July 2003 09:09, Ralf Nolden wrote:
> On Mittwoch, 30. Juli 2003 07:39, Martin Konold wrote:
> > Am Mittwoch, 30. Juli 2003 03:57 schrieb Neil Stevens:

> > > We can either set up KDE policies that respect all contributors, or we
> > > can have informal policies that favor a few developers over the greater
> > > group. I think the formal ones would be more fair in the long run.
> >
> > KDE was never about fairness (speak politics/bureaucracy) but primarily
> > about getting the work done. Bureaucracy is actually a serious thread to
> > KDE.
> >
> > So instead of drafting a policy and doing philosophical considerations it
> > is more benefitial for KDE to try to find an efficient technical solution
> > to real problems.
> cvs co qt-copy; cd qt-copy; ./configure <add your desires here>; make.
> It's always amazing how easy it is to solve really hard problems in KDE/Qt
> :-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2145 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20030730/b966ec58/attachment.bin>

More information about the kde-core-devel mailing list