From kde-community  Thu Jan 16 13:27:43 2014
From: Kevin Ottens <ervin () kde ! org>
Date: Thu, 16 Jan 2014 13:27:43 +0000
To: kde-community
Subject: Re: [kde-community] Non Api-stable libraries/frameworks - Re: Applications in KDE Generation 5
Message-Id: <1629628.0CTQq7hVcA () wintermute>
X-MARC-Message: https://marc.info/?l=kde-community&m=138987887711906
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============9061286022621255623=="


--===============9061286022621255623==
Content-Type: multipart/signed; boundary="nextPart3063543.WndWfjU4jl"; micalg="pgp-sha1"; protocol="application/pgp-signature"


--nextPart3063543.WndWfjU4jl
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

On Thursday 16 January 2014 12:16:48 Sebastian K=FCgler wrote:
> On Thursday, January 16, 2014 12:00:36 Kevin Krammer wrote:
> > On Thursday, 2014-01-16, 01:33:34, Albert Astals Cid wrote:
> > > El Dimecres, 15 de gener de 2014, a les 21:47:17, John Layt va es=
criure:
> > > > * Application domain-specific libraries such as libkipi or libk=
cddb
> > > > may now be better organised under Frameworks rather than their
> > > > modules, where they could gain a wider user base and a clearer
> > > > maintenance viability.  Can we have a Frameworks category for n=
on-api
> > > > stable libraries?
> > >=20
> > > I am not sure I would call it "Frameworks", but yes, that makes t=
otal
> > > sense, for example at the moment our mobipocket library just uses=
 QtCore
> > > and QtGui but since it's using all the KDE cmake stuff it's not t=
hat
> > > easy
> > > to re-use "from the outside".
> >=20
> > I also think it is important to not call those "Frameworks", becaus=
e it
> > dilutes the assumption we want developers to make about Frameworks,=
 e.g.
> > stable, maintained, scheduled releases, etc.
>=20
> This is a very important point. We've had some discussions during the=
 Plasma
> sprint (which I'm currently attending), and "make it a Framework" was=

> offered as a solution to scope some libraries. While I think that sho=
uld in
> principle be possible, separate libraries do not automatically become=

> frameworks.
>=20
> The fact that they're split and less interdependent makes it easier t=
o have
> a bigger set of libraries, but it's really important that we only shi=
p
> libraries that satisfy a certain set of qualities, such as API and AB=
I
> stability, complete documentation, unit-testing, etc. Otherwise, our =
newly
> created "Frameworks brand" will quickly lose its meaning and value, a=
nd
> worse, devalue other, high-quality libraries' reputations. Strong
> requirements are a good thing here.

That's what this page is for:
http://community.kde.org/Frameworks/Policies

Still incomplete, but I expect the quality threshold to raise with time=
.

Cheers.
=2D-=20
K=E9vin Ottens, http://ervin.ipsquad.net

KDAB - proud supporter of KDE, http://www.kdab.com


--nextPart3063543.WndWfjU4jl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEABECAAYFAlLX3k8ACgkQB0u7y43syeIAogCfYfVrumqzLizVpftUoJzNCTPA
/6gAniUEzoEqjpNjqBIWll/DnZpsqa+H
=QwJJ
-----END PGP SIGNATURE-----

--nextPart3063543.WndWfjU4jl--


--===============9061286022621255623==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
--===============9061286022621255623==--