[kde-community] Closing the kde-core-devel mailing list

[Aaron J. Seigo]

On Tuesday, August 26, 2014 13.39:46 Kevin Krammer wrote:
> Only if it involves a (potential) framework.
> In this this is incidentally true.
> 
> If the scope of the BoF would just be gathering best pratices, I would have

At risk of repeating myself in this thread: the definition of "frameworks" is 
being used in a fashion that is too narrow to be useful.

If the scripting BoF never results in a physical git repository that joins KDE 
Framework, but "only" results in a best practice to be adopted by the 
Frameworks audience, then it ought to be on-topic for the frameworks devel 
list. It should, after all, be reflected in KDE Frameworks as well as the 
applications above it.

.. and what of the applications? At least one person from each KDE development 
team which uses frameworks ought to be on the frameworks devel mailing list, 
if only to keep frameworks devel on track for the needs of the wider audience 
of application developers.

If that assumption is wrong, then KDE is going to have some serious problems 
on its hands in short order; but I suspect it is not at all off the mark and 
you ought to be able to announce your BoF on a k-c-d that is dedicated 
primarily to frameworks-as-a-product and reach your intended audience.

-- 
Aaron J. Seigo
-------------- 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-community/attachments/20140826/b0aea4b2/attachment.sig>