Review for library code

[Aaron J. Seigo]

On June 21, 2010, Kevin Krammer wrote:
> Hi Stefan,
> 
> On Monday, 2010-06-21, Stefan Majewsky wrote:
> > I want to add new classes to libkdegames, but cannot find any policy on
> > Techbase describing how the review process is supposed to work.
> 
> I don't think there is a policy like that, especially not for "private"
> module libraries.
> 
> My guess is that most module teams just let all of their established
> members make additions (or even changes if dependencies are changed as
> well) without any special review, unless requested so by the committer
> (e.g. because it is not clear whether this is a proper way to do it).

pretty much; we do have this for kdelibs, however:

	http://techbase.kde.org/Policies/New_KDE_Library_API_Policy

and i think it would be very good if other KDE projects adopted this approach 
for their major libraries (such as libkdegames). it is also a living document, 
so if it doesn't fit the needs of a specific project (e.g. kdegames) let's 
talk about why, revamp the policy page and work into a shape that can be more 
widely adopted.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20100621/f6a7e5cc/attachment.sig>