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

[Aaron J. Seigo]

On Tuesday, August 26, 2014 13.28:56 Kevin Krammer wrote:
> On Tuesday, 2014-08-26, 12:02:27, Aaron J. Seigo wrote:
> > On Tuesday, August 12, 2014 21.23:54 Kevin Ottens wrote:
> > > For instance, Kevin Krammer's example of having a mean of
> > > contacting largely for gauging the need of a scripting BoF is spot on. I
> > > hope it won't get to that point, but k-c-d would still have value if it
> > > was
> > > the only kind of traffic on it.
> > 
> > How is a pan-KDE scripting BoF not a frameworks topic?
> 
> It is mostly an application development topic, it becomes a frameworks topic
> if there is a need to create a framework for sharing stuff.

"Stuff" means more than "code". A best practice is shared "stuff"; a 
community-wide policy is shared "stuff". The difference between having an 
agreed upon best practice or policy and a code repository is academic; it 
requires the same people to buy into it and provide input.

-- 
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/bd326b54/attachment.sig>