On Fri, Jan 13, 2017 at 1:38 PM, Valorie Zimmerman
wrote:
> I've just finished preparing the new Ideas page for 2017:
> https://community.kde.org/GSoC/2017/Ideas
>
> It is basically the same as every other year, and has no previous
> ideas on it. If you or your project plan to present a former ide
On Mon, Dec 19, 2016 at 10:01 AM, Harald Sitter wrote:
> On Thu, Dec 15, 2016 at 10:18 PM, Albert Astals Cid wrote:
>> In the old days it had kdelibs development discussion but not that that has
>> moved over to kde-frameworks-devel, waht's kde-core-devel for?
>
> *cough*
> http://markmail.org/th
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129810/#review102109
---
Isn't this KCM already available in "Configure Konqueror" ?
Hi devs,
this month, a heated exchange on kde-core-devel about a dep
change breaking CI has moved us to draft a new policy to better
handle situations like this in the future.
While not "law", the policy _strongly_ suggests some guidelines
forming a quid-pro-pro protocol between developers and s
On 01/19/2017 04:55 PM, Ben Cooksley wrote:
> It's already been fixed - by having the CI build libxkbcommon. It was
> also required to build an updated version of xorg-macros upon which
> that depended.
> Libraries that depend on KWindowSystem will have the self-built
> libxkbcommon made availabl
On 01/19/2017 03:59 AM, Friedrich W. H. Kossebau wrote:
> Given this is a policy affecting all of the KDE projects, please first
> propose
> it officially in a separate own thread, with a proper subject. Perhaps even
> on
> kde-community, as kde-core-devel might not be read by many, given it u
