The license possibilities that have been discussed so far are GPL to remain consistent with the KOffice applications, LGPL to encourage add-on development, and a mention not to discount a BSD style license.
The two most popular suggestions for language of development are Java and C++.
Java has been suggested for its platform independence and built in networking abilities.
C++ has been suggested for its compatibility with the core KDE development.
Whether the initial version of the application should use an embedded database or an external database has been the subject of much debate on <kplato@kde.org>. An embedded database would give the advantage of ease of setup, while an external database would give KPlato access to the functions provided by the enterprise level databases available in Linux.
One thing that has been agreed upon is that the database API should be sufficiently abstracted that it can be generalized to use a database of the users choice as the application matures.
The following applications have been noted as ones that the KPlato team should investigate close integration with:
Kproject
KOrganizer
KOffice
Kugar
A Requirements Management Tool
A document browser tree