[kde-quality] KDE PIM docs

[Carlos Leonhard Woelz]

I forgot to add kde-doc-english.

Also, the screenshots in almost all modules need update. It seems like a very 
good job for a begginner: fast and gratifying.

On Tuesday 24 February 2004 15:16, Carlos Leonhard Woelz wrote:
> Hi,
>
> I am checking the status of the kde-pim docs. I intend to maintain this
> list to help orienting the newcomers. When it is ready, I will make a page
> in the wiki with updated status for the kdepim module. I guess the per
> application page was not such a good idea, since it is too much work, and
> too many people work in more than one application per module. So I will try
> to maintain and update the page for the whole kde-pim, and specially make
> it ready for the launch of the kde quality team (monday).
>
> Using KDE CVS data, I made a (crude) analysis, please correct me if I am
> wrong.
>
> KMail: relatively well maintained, dnaber is currently updating it.
>
> KOrganizer: needs work, last update 14 months ago.
>
> KAdressbook: updated 5 months ago by tokoe, and got fixes from binner.
>
> Kontact: cshumac added it two months ago, seems reasonably up to date.
>
> KNotes: laurie updated and simplified it 5 months ago. Dunno if it changed
> much since.
>
> KAlarm: got an update from David Jarvie two months ago.
>
> KNode: last update ages ago
>
> KPilot and Kandy: I don't have the hardware to test this apps, but lets go:
>
> KPilot: last update 7 months ago by adridg with the comment "it is still a
> mess"
>
> Kandy: very old docs! I think Kandy holds the record of oldest non-fix
> commit.
>
> KonsoleKalendar: Allan Winter seems to be taking care of it.
>
> The worse situations seem to be KOrganizer, KPilot, KNode and  Kandy.
>
> Yes, I know that the update priority is a not only a function of the lag in
> time of the last update, but also of the current quality of the documents
> and the rhythm of the changes in the application. That is why I want your
> comments on this list.
>
> With the exception of KMail, I don't use much of the other KDE PIM
> applications currently, so I am pretty neutral on which app to attack
> first. KOrganizer seems a good target, and I am willing to set up a testing
> environment for testing the groupware features if necessary.
>
> Do you recommend setting up a Kolab (or other supported groupware) server
> only for that, or is this a overkill?
>
> Cheers,
>
> Carlos Woelz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: signature
Url : http://mail.kde.org/pipermail/kde-quality/attachments/20040224/a4a77d2b/attachment.pgp