[kde-community] Fwd: KDE Vision – towards “wholesame” solutions

[Martin Graesslin]

On Monday, February 15, 2016 9:06:48 AM CET Jaroslaw Staniek wrote:
> On 15 February 2016 at 07:54, Martin Graesslin <mgraesslin at kde.org> wrote:
> > On Sunday, February 14, 2016 11:57:56 PM CET Alexander Neundorf wrote:
> >> > I agree that integration within our projects is important. And I
> >> > believe it has suffered lately as the cohesion inside KDE became less.
> >> > My gut feeling is that this should go in the mission.
> >> > 
> >> > > I would suggest a sentence like the following:
> >> > > “KDE aims to offer complete, well-integrated solutions – while
> >> > > connecting
> >> > > different platforms, devices and online services.”
> >> > 
> >> > That sounds good to me.
> >> 
> >> To me too, but I still miss the reference that it is about software with
> >> graphical user interfaces (GUI's can also have gesture or voice input
> >> etc.), which Olaf seems to imply too.
> > 
> > I can only repeat my advice: please don't close doors for KDE by focusing
> > on GUI. There is a world beyond GUI and KDE partially already entered it.
> > Don't close it.
> 
> Maybe GUI -> UI would solve that. Or "primary focus is the UI".

Would be much better. It at least doesn't exclude things like speech 
recognition.

Nevertheless I would still suggest that we elaborate where KDE might be going 
and whether that fits under UI. Especially under consideration what we already 
do.

Using a simple example: today I created a GSoC project idea which is a docker 
container for KWin to be useable as a Plasma mobile emulator and also cloud. 
Is that UI? I don't know. It would render somwhere, but is that enough to 
consider it as a UI? Or is in that case KWin just a piece of server software 
without any UI (e.g. access through VNC/rdesktop/html5 with no direct 
interaction in KWin)?

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20160215/2abc74b7/attachment.sig>