Creation of kdevplatform module
winter at kde.org
Thu May 3 04:40:48 CEST 2007
On Wednesday 02 May 2007 10:26:14 pm Alexander Neundorf wrote:
> On Wednesday 02 May 2007 11:33, Matt Rogers wrote:
> > On May 2, 2007, at 8:05 AM, Allen Winter wrote:
> > > IF we were to do this.. then
> > > + The new module should be in place by 8 May.
> > > + The libs code should follow typical kdelibs coding policies and
> > > licensing
> > > requirements by the first beta release (25 June). And kdevelop
> > > and quanta
> > > should be using it.
> > Is following kdelibs coding policies a requirement? KDevelop has its
> > own coding style. Why can't we just follow that? What happens if it
> > won't be ready for KDE 4.0 (which it won't be)?
> IMO kdevelop is a project with releases independent from KDE (as koffice) and
> as such can have its own policies, in coding style, release management and
Sorry, I wasn't clear.
I'm talking about the policies dealing with a public API. i.e, dpointers, inline
methods, apidox, .. stuff like that. I didn't mean coding style. The licensing
must be LGPL, BSD, or X11 (same as kdelibs).
And i still think kdedevlibs would be a more appropriate module name.
Or maybe kdesdklibs.
Release management of this new module should be put under the KDE umbrella.
Else, why did you post this request to the release-team ML?
More information about the release-team