[kde-community] finding a clear vision for KDE - first draft for discussion

[Alexander Neundorf]

On Thursday, February 11, 2016 10:06:57 Sebastian Kügler wrote:
> On Wednesday, February 10, 2016 10:08:19 PM Alexander Neundorf wrote:
> > On Tuesday, February 09, 2016 23:03:47 Sebastian Kügler wrote:
> > > On Tuesday, February 09, 2016 23:15:21 Alexander Neundorf wrote:
> > > > I'll also start a new sub-thread.
> > > > Since this vision draft is very broad: what kind of projects do you
> > > > consider  to be covered by this vision draft ?
> > > > Or, the other way round, are there projects, or types of projects
> > > > which
> > > > you see as not part of this vision ?
> 
> I don't know what exactly you mean with "being covered by" or "see as part
> of the vision", but let's assume "projects that identify with the goals
> described in our vision.
> 
> > > Sure. Projects that use open source licenses for purely economical
> > > reasons, or those that don't care about the user, or her privacy.
> > > 
> > > A lot of it is about priorities, and the reason why people work on these
> > > project, their goals.
> > 
> > Let's get a bit more concrete.
> > So I guess most GNU projects would fit ? Bash, gcc, emacs ?
> 
> GCC and Emacs (I couldn't find info about bash) require copyright assigment
> through a mandatory contributor license agreements *1. That would be against
> KDE's manifesto. It makes sense to work together, but we disagree about the
> how to do it.

so do I understand correctly that in general you would consider projects like 
a shell, a compiler and a text-mode editor as potential KDE projects ?

What's your opinion on one of the original goals of KDE to provide a set of 
software with a consistent look & feel and usability, stuff like common 
printing dialogs, file dialog, help systems, dialog layouts, etc, etc. ?


> > What about non-software projects like Project Gutenberg (free books),
> > Jamendo  (free indie music), SubSurfWiki.org (free knowledge) ?
> > Paraview (empowering students and scientists) ?
> 
> The draft states clear that we do Free software.

There's also a thin line here.
Most web sites require some programming. Some more, some less. E.g. a 
knowledge site could have some special code for presenting/visualizing data, a 
music site could have custom solutions for streaming, etc.
Where do you draw the line ?

Alex