Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Monday, February 08, 2016 22:41:08 Sebastian Kügler wrote: > On Monday, February 08, 2016 21:42:58 Alexander Neundorf wrote: > > > I understand that you're saying it doesn't have a place in KDE. > > > > Sebas, you may have missed that I explicitely mentioned eigen in the mail > > you replied

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Thursday, February 04, 2016 08:49:55 PM Alexander Neundorf wrote: > Still we don't see linear algebra libraries or build tools as the main goal > KDE is trying to achieve (...says the guy who maintained the KDE > buildsystem for more than 7 years). Next counter-example: The Eigen library, a

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Thursday, February 4, 2016 9:16:41 PM CET Alexander Neundorf wrote: > Hi, > > On Thursday, February 04, 2016 07:53:06 Martin Graesslin wrote: > > On Wednesday, February 3, 2016 11:44:35 PM CET Alexander Dymo wrote: > > > I reread both drafts and realized that people who have not > > >

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Monday, February 08, 2016 10:56:01 Sebastian Kügler wrote: > On Thursday, February 04, 2016 08:49:55 PM Alexander Neundorf wrote: > > Still we don't see linear algebra libraries or build tools as the main > > goal > > KDE is trying to achieve (...says the guy who maintained the KDE > >

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Friday, February 05, 2016 08:40:21 AM Alexander Dymo wrote: > You > can satisfy all the requirements in the manifesto, but still be a bad > candidate for a KDE project. As the extreme example, one could fork > Plasma and want to join KDE. There are less extreme cases. I wonder why you say that

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

Ingo, you may be right here. If we extract the vision statement from the proposal, it would be something like: "An end user will have free software apps and shells/launchers on any device they use". Note, this is what I came up just now when writing this reply. This needs more thought, but the

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Thursday, February 04, 2016 08:53:57 AM Alexander Dymo wrote: > Let's say it wants to join KDE. Under the > "inclusive" proposal such a project will be welcomed. Under "focused" > - no. The vision document will never be a metric to accept or refuse a project. The manifesto is the only

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

As Lydia put it, it will be a clear frame of reference to make choices in. On Fri, Feb 5, 2016 at 4:13 AM, Riccardo Iaconelli wrote: > On Thursday, February 04, 2016 08:53:57 AM Alexander Dymo wrote: >> Let's say it wants to join KDE. Under the >> "inclusive" proposal such a

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Friday, February 05, 2016 08:01:49 AM Alexander Dymo wrote: > As Lydia put it, it will be a clear frame of reference to make > choices in. No way. Quoting Ben Cooksley: This criteria has already been laid out by the KDE Community, in a document called the Manifesto. It lays out fairly

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

Answering the first part of your email: Vision and mission would help us determine whether the project that wants to join KDE shares the same goals and follows the same path. You can satisfy all the requirements in the manifesto, but still be a bad candidate for a KDE project. As the extreme

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

Hi, At this point, I need to butt in. On 4 February 2016 at 20:23, Alexander Dymo wrote: > Let's consider another example. This time it will be the imaginary > free Github replacement. This time the tech is too far away from > user-end apps and shells. Let's say it wants to

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

Let's take one of your examples: some imaginary sensory tech that follows your mind. It's going to be a competitive advantage to both Plasma and applications, for sure. Can it be a KDE project? Yes, because it clearly brings KDE closer to its goal. And actually, both visions/missions would support

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Thursday, February 4, 2016 7:52:34 AM CET Alexander Dymo wrote: > Focused does not mean exclusive. Every technology (and not only > technology) that gets us to the point where all users use KDE shells > and apps (because of their superiority) is welcome. IMHO, of course. sorry, but I cannot

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

Focused does not mean exclusive. Every technology (and not only technology) that gets us to the point where all users use KDE shells and apps (because of their superiority) is welcome. IMHO, of course. Another point is that not everything needs to be built in house. When I started free software

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Thursday, February 4, 2016 8:53:57 AM CET Alexander Dymo wrote: > Let's take one of your examples: some imaginary sensory tech that > follows your mind. It's going to be a competitive advantage to both > Plasma and applications, for sure. Can it be a KDE project? Yes, > because it clearly

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

And here is where I, perhaps surprisingly to you, agree with you. Like, 100% agree. I wrote "Plasma and applications", but should have written "applications and Plasma". It's the KDE apps that shine these days. Krita, Digikam, Kdenlive, K3B, Kate, Okular, and many and many others. In my opinion

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On 4 February 2016 at 20:49, Alexander Neundorf wrote: > On Thursday, February 04, 2016 20:38:52 Boudhayan Gupta wrote: > ... >> Under the "focused" proposal, such a software would have no place in >> the KDE Project. In fact, a software, developed within KDE to address >> KDE's

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Wednesday, February 3, 2016 11:44:35 PM CET Alexander Dymo wrote: > I reread both drafts and realized that people who have not > participated in the development of these proposals might miss the > important difference between them. > > The Lydia & Co see KDE providing users free software to

[kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

I reread both drafts and realized that people who have not participated in the development of these proposals might miss the important difference between them. The Lydia & Co see KDE providing users free software to manage any aspect of their digital life: GUI environments, applications (GUI and