Am Mittwoch, 27. August 2014, 07.24:04 schrieb Thiago Macieira:
Morning Thiago
[snip]
I'm not asking we encourage that. But I am saying that:
* we need a place for discussion to happen if it happens (it will)
Yes, absolutely. Why not kde-devel. What else than the 15+ history speaks
On 27.08.2014 07:11, Aaron J. Seigo wrote:
The way I've seen the goal for years is something like this:
* applications should run great everywhere they can
* applications deliver an even *better* experience when paired with Plasma
You know, a little both/and :)
+1, yeah :)
Cheers,
Eike
On Wednesday 27 August 2014 07:51:54 Laszlo Papp wrote:
My suggestion: use qt-inter...@qt-project.org for supporting people who
want to just use KF5, without developing it.
I would understand that suggestion if the kde frameworks became
official Qt 5 add-ons, although even then one could
On Tuesday, August 12, 2014 17.31:11 Kevin Krammer wrote:
On Tuesday, 2014-08-12, 16:40:36, Aaron J. Seigo wrote:
On Tuesday, August 5, 2014 21.28:14 Kevin Krammer wrote:
k-c-d is the list to for things that happen in development, like
kde-review
requests, inter-module coordination,
On Tue, Aug 26, 2014 at 11:34 AM, Aaron J. Seigo ase...@kde.org wrote:
Sure, but asking questions about how to use frameworks will end up on the
frameworks list, because that's the most obvious name for people looking
for
help on frameworks.
agreed; my suggestion is that we already have
Am Dienstag, 26. August 2014, 12.34:35 schrieb Martin Klapetek:
Morning Martin
We can have the perfectly named mailing list (whatever that means) but
that
is not going to get people using frameworks, which is at the core of your
contention. To achieve the goal of more people using KDE
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
On Tuesday, 2014-08-26, 11:34:20, Aaron J. Seigo wrote:
On Tuesday, August 12, 2014 17.31:11 Kevin Krammer wrote:
On Tuesday, 2014-08-12, 16:40:36, Aaron J. Seigo wrote:
On Tuesday, August 5, 2014 21.28:14 Kevin Krammer wrote:
review requests probably should be going elsewhere; they make
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
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
On Tuesday, 2014-08-26, 16:15:56, Aaron J. Seigo wrote:
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
On Tuesday 26 August 2014 15:28:09 Aaron J. Seigo wrote:
Simple frameworks
support list for random people who are not involved with KDE in any way
and
don't care about development (of any kind) inside of the community, but
are
just looking for support and possibly willing to offer
On Tuesday 26 August 2014 17:17:43 Kevin Krammer wrote:
On Tuesday, 2014-08-26, 16:15:56, Aaron J. Seigo wrote:
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
On Tuesday 26 August 2014 09:29:02 Thiago Macieira wrote:
On Tuesday 26 August 2014 15:28:09 Aaron J. Seigo wrote:
Simple frameworks
support list for random people who are not involved with KDE in any way
and
don't care about development (of any kind) inside of the community, but
On 26.08.2014 22:05, Milian Wolff wrote:
That would leave kde-devel for what it's been used for the past 15 years:
discussing development of applications that are tightly integrated with
KDE's desktop environment (i.e., Plasma desktop).
I like that suggestion!
My 2 cents: KDE is a the name
On Tuesday, August 26, 2014 22.24:24 Eike Hein wrote:
So yeah, let's please not make a write apps for Plasma
mailing list. It doesn't fit what KDE is today - and
that's a good thing, because our ambitions have become
grander and our means to accomplish them have, too.
I generally agree; that
On Tuesday 26 August 2014 22:24:24 Eike Hein wrote:
My 2 cents: KDE is a the name of a community that makes a
whole bunch of things, chiefly among them right now:
* A set of libraries/frameworks that complement Qt and help
with building applications and workspaces that run nicely
on a
On Tuesday, August 05, 2014 21:28:14 Kevin Krammer wrote:
On Tuesday, 2014-08-05, 20:29:05, Albert Astals Cid wrote:
El Dilluns, 4 d'agost de 2014, a les 20:36:44, Vishesh Handa va escriure:
Random Idea: How about we close the k-c-d mailing list? It's main
purpose
used to be to
On Tuesday, August 5, 2014 21.28:14 Kevin Krammer wrote:
k-c-d is the list to for things that happen in development, like kde-review
requests, inter-module coordination, etc.
It is more like a kde-community-technical list.
review requests probably should be going elsewhere; they make following
On Tue, Aug 12, 2014 at 3:40 PM, Aaron J. Seigo ase...@kde.org wrote:
perhaps it would make more sense to recall the purpose of each list, adapt
to
how the community is using reviewboard, and simplify rather than redefine
and
move around long-extant infrastructure?
+1
On Tuesday, 2014-08-12, 16:40:36, Aaron J. Seigo wrote:
On Tuesday, August 5, 2014 21.28:14 Kevin Krammer wrote:
k-c-d is the list to for things that happen in development, like
kde-review
requests, inter-module coordination, etc.
It is more like a kde-community-technical list.
review
On Monday 04 August 2014, Vishesh Handa wrote:
Hello people
Random Idea: How about we close the k-c-d mailing list? It's main purpose
used to be to discuss kdelibs changes, but now since we have
kde-frameworks, the mailing list seems less useful. We already have
kde-devel for other generic
On Monday 04 August 2014 20:36:44 Vishesh Handa wrote:
Hello people
Random Idea: How about we close the k-c-d mailing list? It's main purpose
used to be to discuss kdelibs changes, but now since we have
kde-frameworks, the mailing list seems less useful. We already have
kde-devel for other
How about the opposite? Close the frameworks list and move that discussion
back here, where it belongs.
+1
For me, the frameworks list was useful for the work on splitting. Now, it is
(kinda) business as usual, so we can all just return back to k-c-d.
--
Cheerio,
Ivan
KDE, ivan.cukic
Hello,
On Monday 04 August 2014 20:36:44 Vishesh Handa wrote:
Random Idea:
Heh, someone with too much time at hand? :-)
Note that I generally find that fiddling with lists is generally generating
quite some boring work across the board.
How about we close the k-c-d mailing list?
I think
On Monday, August 4, 2014 20.36:44 Vishesh Handa wrote:
Random Idea: How about we close the k-c-d mailing list? It's main purpose
used to be to discuss kdelibs changes, but now since we have
kde-frameworks, the mailing list seems less useful. We already have
kde-devel for other generic kde
El Dilluns, 4 d'agost de 2014, a les 20:36:44, Vishesh Handa va escriure:
Hello people
Random Idea: How about we close the k-c-d mailing list? It's main purpose
used to be to discuss kdelibs changes, but now since we have
kde-frameworks, the mailing list seems less useful. We already have
On Tuesday, 2014-08-05, 20:29:05, Albert Astals Cid wrote:
El Dilluns, 4 d'agost de 2014, a les 20:36:44, Vishesh Handa va escriure:
Hello people
Random Idea: How about we close the k-c-d mailing list? It's main purpose
used to be to discuss kdelibs changes, but now since we have
Hello people
Random Idea: How about we close the k-c-d mailing list? It's main purpose used
to be to discuss kdelibs changes, but now since we have kde-frameworks, the
mailing list seems less useful. We already have kde-devel for other generic
kde stuff.
--
Vishesh Handa
On Monday 04 August 2014 20:36:44 Vishesh Handa wrote:
Hello people
Random Idea: How about we close the k-c-d mailing list? It's main purpose
used to be to discuss kdelibs changes, but now since we have
kde-frameworks, the mailing list seems less useful. We already have
kde-devel for other
30 matches
Mail list logo
