[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-promo
Subject: Re: [kde-promo] Article about Baloo
From: Jos Poortvliet <jos () opensuse ! org>
Date: 2014-02-19 6:11:48
Message-ID: CAABAGrWdktd35OQup+YG5EMiuDC0QmjijqOu-E1hNYMfu=0CRg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I really like this. A lot.
On Feb 19, 2014 2:28 AM, "Aaron J. Seigo" <aseigo@kde.org> wrote:
> On Monday, February 17, 2014 15:43:29 Jos Poortvliet wrote:
> > It would be great if the draft on https://notes.kde.org/p/BalooArticlecould
>
> from the article, i get the following key points:
>
> * stability
> * performance
> * ease of use
> * bright future
>
> Those are great points, and the article starts off strongly. The content in
> general is great imho. The only thing that leaped out at me was that the
> flow
> meanders from design to developers to users to developers to migration to
> developers ...
>
> What would you think about simplifying the flow a bit so that it goes sth
> like:
>
> Introduction
> Using Baloo ("Baloo for users")
> Developing with Baloo (second half of "about baloo")
> The design behind Baloo (first half of "about baloo")
> Migrating to Baloo (4.13, migration tool, KF5...)
>
> That way people get told what it does for them / how it makes their life
> better before getting into the details of the design.
>
> Separating "using" from "developing" more clearly may also help the
> readability a bit; e.g. in "baloo for users" right now there is this
> sentence:
>
> "The simplicity of the design will not only reduce failures, but will also
> make it easier for current and new contributors to add and improve
> functionality."
>
> While true, it's not really relevant to usage right now that it can be more
> easily added to in future ...
>
> I suggest dropping the entire "Why change Nepomuk" section (regardless of
> what
> happens with naming): it's technical, dry and negative. I don't know how
> many
> people in the target audience will care about RDF and how it works, for
> instance. The "Making Nepomuk Usable" sub-section could be re-purposed as
> an
> introduction to a "design behind baloo" section. I would entirely avoid
> criticizing the outcome of the research project.
>
> Perhaps something along the lines of:
>
> Since its inception, Nepomuk developers received and digested a lot of
> feedback. Application developers requested and received easier to use APIs
> (Application Programming Interfaces, glue for integration) and widgets
> (like
> the star rating or a tagging dialog). Users clearly requested increased
> stability and performance. Much work was put into improving the speed of
> indexing, keeping it out of the way of users and making Nepomuk more
> reliable.
>
> Even after all this work, paint points remained. In particular, the storage
> system used in Nepomuk continued to present performance challenges that
> were
> unresolvable on desktop and mobile systems.
>
> To address this, the developers took a step back to look at how Nepomuk was
> being used in practice. The major use-cases they found are:
>
> <...etc...>
>
>
> This is a lot less negative about Nepomuk, skips a lot of technical detail
> tat
> probably isn't necessary to understand the message and turns it all into a
> nice story of "the Nepomuk developers listened and worked hard to meet the
> needs being communicated to them."
>
> --
> Aaron J. Seigo
>
> _______________________________________________
> This message is from the kde-promo mailing list.
>
> Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set
> digest on or temporarily stop your subscription.
[Attachment #5 (text/html)]
<p dir="ltr">I really like this. A lot.</p>
<div class="gmail_quote">On Feb 19, 2014 2:28 AM, "Aaron J. Seigo" <<a \
href="mailto:aseigo@kde.org">aseigo@kde.org</a>> wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> On Monday, February 17, 2014 \
15:43:29 Jos Poortvliet wrote:<br> > It would be great if the draft on <a \
href="https://notes.kde.org/p/BalooArticle" \
target="_blank">https://notes.kde.org/p/BalooArticle</a> could<br> <br>
from the article, i get the following key points:<br>
<br>
* stability<br>
* performance<br>
* ease of use<br>
* bright future<br>
<br>
Those are great points, and the article starts off strongly. The content in<br>
general is great imho. The only thing that leaped out at me was that the flow<br>
meanders from design to developers to users to developers to migration to<br>
developers ...<br>
<br>
What would you think about simplifying the flow a bit so that it goes sth like:<br>
<br>
Introduction<br>
Using Baloo ("Baloo for users")<br>
Developing with Baloo (second half of "about baloo")<br>
The design behind Baloo (first half of "about baloo")<br>
Migrating to Baloo (4.13, migration tool, KF5...)<br>
<br>
That way people get told what it does for them / how it makes their life<br>
better before getting into the details of the design.<br>
<br>
Separating "using" from "developing" more clearly may also help the<br>
readability a bit; e.g. in "baloo for users" right now there is this sentence:<br>
<br>
"The simplicity of the design will not only reduce failures, but will also<br>
make it easier for current and new contributors to add and improve<br>
functionality."<br>
<br>
While true, it's not really relevant to usage right now that it can be more<br>
easily added to in future ...<br>
<br>
I suggest dropping the entire "Why change Nepomuk" section (regardless of what<br>
happens with naming): it's technical, dry and negative. I don't know how many<br>
people in the target audience will care about RDF and how it works, for<br>
instance. The "Making Nepomuk Usable" sub-section could be re-purposed as an<br>
introduction to a "design behind baloo" section. I would entirely avoid<br>
criticizing the outcome of the research project.<br>
<br>
Perhaps something along the lines of:<br>
<br>
Since its inception, Nepomuk developers received and digested a lot of<br>
feedback. Application developers requested and received easier to use APIs<br>
(Application Programming Interfaces, glue for integration) and widgets (like<br>
the star rating or a tagging dialog). Users clearly requested increased<br>
stability and performance. Much work was put into improving the speed of<br>
indexing, keeping it out of the way of users and making Nepomuk more reliable.<br>
<br>
Even after all this work, paint points remained. In particular, the storage<br>
system used in Nepomuk continued to present performance challenges that were<br>
unresolvable on desktop and mobile systems.<br>
<br>
To address this, the developers took a step back to look at how Nepomuk was<br>
being used in practice. The major use-cases they found are:<br>
<br>
<...etc...><br>
<br>
<br>
This is a lot less negative about Nepomuk, skips a lot of technical detail tat<br>
probably isn't necessary to understand the message and turns it all into a<br>
nice story of "the Nepomuk developers listened and worked hard to meet the<br>
needs being communicated to them."<br>
<br>
--<br>
Aaron J. Seigo<br>
<br>
_______________________________________________<br>
This message is from the kde-promo mailing list.<br>
<br>
Visit <a href="https://mail.kde.org/mailman/listinfo/kde-promo" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-promo</a> to unsubscribe, \
set digest on or temporarily stop your subscription.</blockquote></div>
_______________________________________________
This message is from the kde-promo mailing list.
Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on \
or temporarily stop your subscription.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic