[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Creation of kdevplatform module
From:       "Alexander Dymo" <adymo () kdevelop ! org>
Date:       2007-05-03 15:14:30
Message-ID: a178f7b00705030814t7851e4fbq897a1ecc8aafc025 () mail ! gmail ! com
[Download RAW message or body]

On 5/3/07, Allen Winter <winter@kde.org> wrote:
> I'm talking about the policies dealing with a public API. i.e, dpointers, inline
> methods, apidox, .. stuff like that.

Basically we either adhere to kdelibs policies here or strive to.


>  I didn't mean coding style.   The licensing
> must be LGPL, BSD, or X11 (same as kdelibs).

The license of the libraries in the module is LGPL, the license of the
plugins in the module is LGPL or GPL depending on the plugin.
We do have the requirement for libraries to be LGPL-ed, but I don't
think this requirement fits the plugins.


> And i still think kdedevlibs would be a more appropriate module name.
> Or maybe kdesdklibs.

Please take a look at this thread
http://lists.kde.org/?l=kdevelop-devel&m=117068584829906&w=2
and to the voting results:
http://lists.kde.org/?l=kdevelop-devel&m=117087973005829&w=2

The name "kdeveloplib" was proposed but didn't get many votes.


> Release management of this new module should be put under the KDE umbrella.

We'd like kdevplatform to be the part of KDE releases of course, just
like kdevelop and kdewebdev. We won't be ready for 4.0, but there's a
chance for 4.1 or later versions.
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]