There seem to be a couple of things unclear.

- Koffice contains some packages which all use and depent on koffice-libs. 
These libs are opensource and creating parts which use them will require 
these to be open source as well.

- Koffice developers communicate through a couple of means:
  - IRC
  - personal email
  - the koffice-devel list (which is limited to active koffice developers)
  - personal contact (as far as possible)
My experience is that this is done a lot and works fine.

- Last week there has been a meeting (5 days of hacking) in Erlangen/Germany.
Design stuff was discussed there, some time ago a new mailing list for that
has been started which the developers have been using to discuss the 
koffice stuff. This kept the serious discussions away from this list.

- We are in a feature freeze, you don't need to discuss design problems when
you are fixing stuff.

OK, enough of the discussions thing. If you want to start a discussion simply 
post your proposal (keep it short please) and if you don't get a reply (within
a reasonale timeframe) noone objects.


- theKompany.com employees have been communicating with the koffice team.
- If you are interested in a project that has a seperate mailing-list; 
  subscribe!

- I wish that all development with the koffice-libs was in one place because
that would make it much easier to incorporate changes to all the dependent
applications. This would effectively mean that the projects theKompany is 
working on would have to be in kde-CVS. (This is just my personal opinion)

- KWord has been neglected for a _long_ time. I picked it up some time ago
and have been getting it up to date in my spare time (I have a full-time job
that keeps me occupied with other stuff). I think kword has been getting better
at a good pace thanx to other people on this list!

Keep up the good work!
-- 
Thomas Zander                                            zander@earthling.net
The only thing worse than failure is the fear of trying something new