Amarok Promo Team is looking for help

[Valorie Zimmerman]

On Tue, Jan 12, 2010 at 4:54 AM, Myriam Schweingruber
<myriam.schweingruber at gmail.com> wrote:
> Hi Valorie,
>
> On Mon, Jan 11, 2010 at 12:08, Valorie Zimmerman
> <valorie.zimmerman at gmail.com> wrote:
>> On Mon, Jan 11, 2010 at 1:52 AM, Eelko Berkenpies <fedora at berkenpies.nl> wrote:
>>>
>>> On Sun, 10 Jan 2010 01:04:50 -0800, Valorie Zimmerman
>>> <valorie.zimmerman at gmail.com> wrote:
> ...
>> As you are scrolling though Bugzilla, how about noticing what comes up
>> over and over again? And what sort of answer is the most effective?
>> Make notes, and send those to the Promo list or here, when you feel
>> like it.
>
> I don't think we should put bugs in a handbook. I triage all Amarok
> bugs when they come in and I don't understand why this would be
> relevant for the handbook at all, sorry. Could you elaborate why this
> has anything to do with the writing on how to use Amarok?
>
>
> Regards, Myriam.

Hi Myriam -- great point! No, we certainly do not want to put bugs in
the Handbook! But bugs that don't get solved are a measure of how our
users are getting confused or frustrated. Not that we want to change
Amarok in deference to their confused wishes, but sometimes looking at
the complaints who like Amarok enough to file a bug, even though it
can't be solved, will give us a clue as to how to explain things
clearly enough to answer future questions before our users get so
confused and frustrated.

I had never thought of using bugs as a source of information for
documentation until I saw them listed over at
http://writingopensource.com/ . As a triager, you might be the best
person to point out bugs we should read as cautionary tales, as we
organize and write. We will be using them as raw materials only, to
get us thinking; not part of the finished product.

Valorie

-- 
New! http://genealogy-uki.linkpendium.com/
Facebook, Twitter, Identi.ca, LinkedIn, Delicious: valoriez .
All my pages: http://valorie.zimmerman.googlepages.com