[Kde-pim] [kde-promo] KDE PIM marketing

[Shaheed Haque]

I'd add one. I want to know how to back up my data and/or config
(whatever is required) in order to (a) move to another
machine/partition/whatever or (b) for archival.

I know the archival process might be as simple as "right click the
folder, and select archive", but users still want to be able to save
their precious data before "risking" it on an upgrade etc.

On 20 February 2012 16:04, Anne Wilson <annew at kde.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 19/02/12 21:31, Jos Poortvliet wrote:
>> Heya all,
>>
>> I don't think I am subscribed to the KDE PIMsters list so I hope
>> Cornelius is willing to forward this to them so they know what's
>> going on... :D
>>
>>
>> --
>>
>> As you might have read in the dot story, the KDE PIM team has
>> discussed marketing at the Osnabrück meeting.
>>
>> A few of the results are relevant for -promo so I promised to mail
>>  you ;-)
>>
>> Please see http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_10
>>  under the marketing header.
>>
>> In short, KDE PIM 4.7 was the first real release of the 'new' KDE
>> PIM since the KDE 3 times. It took a long time to get it out,
>> indeed longer than expected. The stop-gap measures were not
>> exactly great and resulted in many complaints. Meanwhile, the
>> marketing team tried to keep the spirit up - being a tad too
>> positive, perhaps... The result was that the 4.7 release, which
>> would have needed some patience and understanding, instead resulted
>> in many people giving up on KDE PIM.
>>
>> That is sad, as in the 6 months after that release, a HUGE number
>> of issues has been fixed. The KDE PIM team now actually needs
>> quality bug reports - but is unfortunately flooded with lots of
>> complaints. What needs to happen is that we need our KDE Community
>> to start using and testing KDE PIM again; AND we need help bug
>> triaging.
>>
>> Last but not least, we need to change our communication, make clear
>> that 4.7 was our FIRST release and the hurt of the huge
>> re-factoring is behind us: it's upwards from now on.
>>
>> The plan is: 1. We should stop pushing technical terms like
>> "Akonadi" and "Nepomuk" to users. Work has already been put in to
>> eradicate those terms from the UI but we need to do the same in our
>> communication. These terms have not only gotten a very bad rep but
>> are confusing too. Lets keep it simple: we have the KDE PIM UI's
>> like Kontact Mail and Kontact Address book and the KDE PIM
>> backend.
>>
>> 2. We need to communicate that KDE PIM has finally started fresh
>> and is ready for testing; and needs help bug triaging!
>>
>> 3. And we need to tell the big story, the how and what of what we
>> did. For that, see the graphic here:
>> http://dl.dropbox.com/u/29347181/KDE%20PIM.svg
>> http://dl.dropbox.com/u/29347181/KDE%20PIM%20big.png
>> http://dl.dropbox.com/u/29347181/KDE%20PIM_small.png
>>
>> (They are in the "history of KDE PIM" in the wiki, atm, and
>> can/should be used in future stories)
>>
>> The plan is: 1. Change the wiki pages to reflect 1 (done) 2. Let
>> you guys & girls know (hereby done) 3. find a good time to do a
>> big 'call for help' for 2 and do it 4. write articles to address
>> myths around KDE PIM (eg about memory usage, speed, stability, mail
>> loss etc)
>>
>> I have started working on 3 but help is needed with 4. That needs
>> benchmarking and the like...
>>
> As you probably know, for years I did user support for Kontact, which
> was my No.1 favourite application.  Like many users, I gave up the
> struggle when it overwhelmed me.  I'd be more than happy to try it
> again, and help it move still further along the line, and I know that
> other old-time-users still care and would like to, too, but there are
> some steps that really need to be taken before you get the quality bug
> reports and other useful feedback that you need.
>
> Someone absolutely must write about how to move important mail into a
> folder somewhere, in order for it to be imported once the system is
> set up.
>
> Next, a clear instruction on how to remove all traces of the old
> installation, so that the new one really does start clean.  Follow
> that up with instructions on how to import those important messages
> saved elsewhere.  There needs to be clear and easily followed
> explanations of steps that are peculiar to POP3 accounts and those
> peculiar to IMAP accounts.
>
> Then, make available a debug package that doesn't involve 3.4 GB (last
> time I had to remove them) of disk space given up to debug packages.
> *Please* give us a package that fulfils this particular need, not one
> that tries to do everything for every package.
>
> Do remember that your list of complaints in (4) is not a list of
> myths, as you suggest, but real pain that we suffered.  We want to
> help, but pretending that we didn't suffer is not going to help
> anyone.  Instead, tell us that the problems have been recognised and
> addressed.
>
> Help us get a healthy community together again, so that we can help
> the team.
>
> Anne
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk9CbwUACgkQj93fyh4cnBfh7QCfeuXTnecC65edY9jeFVryvcPC
> TFkAnAxPSmzpBBNXyFkPBJxhRfUXol8B
> =izXV
> -----END PGP SIGNATURE-----
> _______________________________________________
> KDE PIM mailing list kde-pim at kde.org
> https://mail.kde.org/mailman/listinfo/kde-pim
> KDE PIM home page at http://pim.kde.org/
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/