[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] status pim.kde.org
From:       Cornelius Schumacher <schumacher () kde ! org>
Date:       2001-10-10 7:53:19
[Download RAW message or body]

On Tuesday 09 October 2001 21:46, Nick Papadonis wrote:
> Adriaan de Groot <adridg@sci.kun.nl> writes:
> > On Monday 08 October 2001 21:37, Klaus Staerk wrote:
> > > I just looked for Changelogs of pim-apps in webcvs - and it seems that
> >>
> >> except KPilot-Changelog the changelogs aren't very up to date.
> >
> > relating to design decisions, people I work with, etc. etc. etc. I think
> > it's neat to have something of a history of the project, (you can tell,
> > for example, that Nick Papadonis was pretty active in testing and fell by
> > the wayside when I didn't fix anything -- foolish me, I hope he'll come
> > back now things are working better again).
>
> I'm here still. :)
>
> I would really like to help development, but I still think we lack
> some well defined information on the website.

What exactly are you missing?

> In many open source situations this information isn't needed.  KDE PIM is
> such a large project with so many pieces, we must establish requirements
> for each and at least specifications for interoperability.  Object and data
> flow diagrams would help even more.

You mean UML diagrams for all the applications? Or what specific applications 
or parts of applications do you have in mind? We already have some developer 
information and lots of documentation is in the source code and can be 
extracted e.g. with Doxygen.

> This will elimate uneeded work and code duplication.

One goal of the roadmap I posted soem time ago, was exactly this, to avoid 
duplicate efforts. If we can extend this to a more detailed list, augmented 
with diagrams and other developer documentation, this would be definitely 
helpful.

> Does anyone have any experience creating these?  If not I can point
> you to the tutorials.  I can also assist in defining these development
> documents. ;)

Great. I would be interested in the pointers and if you would help with the 
development documents, this would be a very valuable contribution. It's a 
hard task to create these and an even harder task to keep them up to date, 
but I think it's important to have it, especially for developers new to the 
kdepim project.

-- 
Cornelius Schumacher <schumacher@kde.org>
_______________________________________________
Kde-pim mailing list
Kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim

[prev in list] [next in list] [prev in thread] [next in thread]