<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote
cite="mid:mailman.13.1461931204.10626.kde-community@kde.org"
type="cite">
<pre wrap="">Date: Thu, 28 Apr 2016 22:43:02 +0200
From: Alexander Neundorf <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:neundorf@kde.org"><neundorf@kde.org></a>
To: informing about and discussing non-technical community topics
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:kde-community@kde.org"><kde-community@kde.org></a>
Subject: Re: [kde-community] KDE Mission - let's do this!
Message-ID: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:2628160.NaUb4Nz2oe@tuxedo.neundorf.net"><2628160.NaUb4Nz2oe@tuxedo.neundorf.net></a>
Content-Type: text/plain; charset="us-ascii"
Hi,
On Thursday, April 28, 2016 12:21:28 Thomas Pfeiffer wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>Hi everyone,
<span class="moz-txt-citetags">> </span>as we've found during the vision creation process that having a concrete
<span class="moz-txt-citetags">> </span>draft to work from can streamline the discussion, I tried to come up with
<span class="moz-txt-citetags">> </span>one. It goes quite into detail, but I think this is necessary in order to
<span class="moz-txt-citetags">> </span>be useful as practical guidance.
</pre>
</blockquote>
<br>
<span class="moz-txt-citetags"></span>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>To provide control, freedom and privacy, KDE's products
<span class="moz-txt-citetags">> </span>- allow users to "tinker" with them
</pre>
</blockquote>
<pre wrap="">As Aleix said, what do you mean exactly with that ?
I could interpret it as
- sources are available
- it is easy to build
- it's highly configurable
- data is stored in easily accessible formats (text, or documented binary, or
binary with low level tools, etc) ?
</pre>
</blockquote>
I think the 2 first are normal for FOSS. What we should emphasis on
is more the 3rd and 4th point. 3rd for users to have more power, 4th
for them to be sure that if one day KDE dies (not soon hopefully
:D), their data are not lost.I like your draft.
<blockquote
cite="mid:mailman.13.1461931204.10626.kde-community@kde.org"
type="cite">
<pre wrap="">It does not mention providing libraries explicitely, but focuses only on
applications (if I didn't miss it).
Is that something which should be added ?
</pre>
</blockquote>
<br>
I like this draft and everything you answered. I think one should
emphasis on the libraries as well in order to show that our target
users are not only end-users but developers as well.<br>
I would really like that someone who uses Qt is able to say "Oh the
KDE Frameworks are great, let's reuse that instead of rewritting
from scratch!" Like people use V-PLay or what not based on Qt.<br>
<br>
Something else: I'm not sure it should be part of the mission: the
way to achieve all this? Having common user interface design (work
with the VDG), same type of configuration windows (use Frameworks
libraries), having webpresence (up to date websites, documentation
online,...).<br>
<br>
I write this last part (webpresence) because I think it's somewhere
we are not so good at, and being part of the mission could put some
incentive on it. We really need that to get more users IMOH.<br>
<br>
Olivier<br>
</body>
</html>