[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Open question to all developers.
From: "=?ISO-8859-1?Q?Elio_Cuevas_G=F3mez?=" <elcugo () gmail ! com>
Date: 2008-06-26 19:59:38
Message-ID: a29e06b20806261259q3f5bab6bje0971d77d2fc18ac () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi! I have a sugestion that could reduce some of the latest flaming.
http://elcugo.deviantart.com/art/Klippy-89868684
Thanks. Elio.
2008/6/25 FiNeX <finex@finex.org>:
> Hi all!
>
>
> Lately KDE is having some troubles with the communication between
> developers,
> kde enthusiast and common users.
>
>
> It seems that the current tools used for communicate are not efficient
> enough:
> wikis, ML, planetKDE, b.k.o... the informations are all present, but
> informations are too much and sometimes not well organized. This cause
> problems like what we've seen this days. People which doesn't help the
> development process, but which slow it down, bad words, and bad feelings,
> all
> things that I don't like to see on a project made by the passion!
>
>
> My idea is to improve the organization of informations. How?
>
>
> One big problem is that users want features. Tom, our example user,
> probably
> have read something about feature X, somewhere on the web, Tom maybe want X
> and Y. He try a 0.x version, probably X and Y aren't there, maybe X is in
> trunk and Y planned for 4.2... who knows this info? Some knows developers,
> some infos are on the commit log, some else are on the wiki, some is in
> b.k.o
> and maybe on some blog entries in Planet.
> At this point Tom try to ask it on b.k.o (Tom is not a skilled user, it is
> more easy that he doesn't use the ML).
> Tom is a common user which doesn't like to read, moreover on bugzilla there
> are a lot of reports, so Tom doesn't look if X and Y are already there; Tom
> will ask again about X and Y, he want it and he doesn't understand that it
> has been planned, he is an user and (sorry for being rude) he doesn't like
> to
> reason out. At this point Tom expect X and Y, but developers are exausted
> to
> repeat all the same things, they doesn't know what to do more than they
> already did.
> So Tom could think that KDE is a failure because his needs are not
> satisfied
> and the communication were not good.
>
>
> If the development process could be transparent to users, with public,
> complete and updated infos about planned version and features, probably a
> big
> problem could be solved: Tom will find the informations he needs in only
> one
> centralized place.
>
> Another problem will be solved: developers will not have to loose time to
> say
> $MAXINT times the same things :-)
>
> I want to ask this to you, KDE developers, do you agree on this
> argumentation?
>
> What do you think if I propose to adopt a centralized tool for managing the
> development processes like development plans, feature planning and so on?
>
> Do you think it is feasibile?
>
> This could be part of a new way for improving communication between you
> (develpers) and users.
>
>
> Thanks for your attention.
>
> Regards.
>
>
> P.S: sorry for the cross-post
>
> --
> by FiNeX
> http://www.finex.org
> finex (@) finex (.) org
> Linux Registered User #306523
>
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>
>
[Attachment #5 (text/html)]
Hi! I have a sugestion that could reduce some of the latest flaming.<br><br><a \
href="http://elcugo.deviantart.com/art/Klippy-89868684">http://elcugo.deviantart.com/art/Klippy-89868684</a><br><br>Thanks. \
Elio.<br><br><div class="gmail_quote"> 2008/6/25 FiNeX <<a \
href="mailto:finex@finex.org">finex@finex.org</a>>:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;">Hi all!<br>
<br>
<br>
Lately KDE is having some troubles with the communication between developers,<br>
kde enthusiast and common users.<br>
<br>
<br>
It seems that the current tools used for communicate are not efficient enough:<br>
wikis, ML, planetKDE, b.k.o... the informations are all present, but<br>
informations are too much and sometimes not well organized. This cause<br>
problems like what we've seen this days. People which doesn't help the<br>
development process, but which slow it down, bad words, and bad feelings, all<br>
things that I don't like to see on a project made by the passion!<br>
<br>
<br>
My idea is to improve the organization of informations. How?<br>
<br>
<br>
One big problem is that users want features. Tom, our example user, probably<br>
have read something about feature X, somewhere on the web, Tom maybe want X<br>
and Y. He try a 0.x version, probably X and Y aren't there, maybe X is in<br>
trunk and Y planned for 4.2... who knows this info? Some knows developers,<br>
some infos are on the commit log, some else are on the wiki, some is in b.k.o<br>
and maybe on some blog entries in Planet.<br>
At this point Tom try to ask it on b.k.o (Tom is not a skilled user, it is<br>
more easy that he doesn't use the ML).<br>
Tom is a common user which doesn't like to read, moreover on bugzilla there<br>
are a lot of reports, so Tom doesn't look if X and Y are already there; Tom<br>
will ask again about X and Y, he want it and he doesn't understand that it<br>
has been planned, he is an user and (sorry for being rude) he doesn't like to<br>
reason out. At this point Tom expect X and Y, but developers are exausted to<br>
repeat all the same things, they doesn't know what to do more than they<br>
already did.<br>
So Tom could think that KDE is a failure because his needs are not satisfied<br>
and the communication were not good.<br>
<br>
<br>
If the development process could be transparent to users, with public,<br>
complete and updated infos about planned version and features, probably a big<br>
problem could be solved: Tom will find the informations he needs in only one<br>
centralized place.<br>
<br>
Another problem will be solved: developers will not have to loose time to say<br>
$MAXINT times the same things :-)<br>
<br>
I want to ask this to you, KDE developers, do you agree on this argumentation?<br>
<br>
What do you think if I propose to adopt a centralized tool for managing the<br>
development processes like development plans, feature planning and so on?<br>
<br>
Do you think it is feasibile?<br>
<br>
This could be part of a new way for improving communication between you<br>
(develpers) and users.<br>
<br>
<br>
Thanks for your attention.<br>
<br>
Regards.<br>
<br>
<br>
P.S: sorry for the cross-post<br>
<font color="#888888"><br>
--<br>
by FiNeX<br>
<a href="http://www.finex.org" target="_blank">http://www.finex.org</a><br>
finex (@) finex (.) org<br>
Linux Registered User #306523<br>
</font><br><br>
>> Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe <<<br> <br></blockquote></div><br>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic