examples

[Aaron J. Seigo]

hi ..

according to this:

http://community.kde.org/Frameworks/Policies#Framework_directory_structure

source code examples are to live in an examples/ directory within the given 
framework git module. to put it simple: i object :)

kdeexamples exists as a way to bring together example code for all sorts of 
frameworks and infrastructure using KDE library and software. it provides a 
"one stop shop" for example code and prevents developers, who usually work 
with pre-packaged binaries and not the upstream sources, from having to fetch 
each and every framework tarball just to see examples for it. it has been well 
received as a result by users and developers alike.

since it's inception it has had 799 commits and over 95 examples.

so those are the "pro"s.

the cons that i can think of are:

* if examples are in the framework repo, people working on the frameworks 
might be more inclined to add examples (though this has not be borne out by 
the kdeexamples experiment at all)

* if examples are not in the same repo as the framework, they are perhaps less 
likely to be maintained. this might mean they are more likely to break if/when 
the framework in question changes (though given source and binary compat 
requirements, this shouldn't be so much of an issue), or will slowly fall out 
of date (though this happened before kdeexamples as well)

in spite of the cons and given the pros, i propose we keep kdexamples as is, 
and not move examples into individual frameworks repositories.

-- 
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-frameworks-devel/attachments/20111205/fce49419/attachment-0001.sig>